If you only need documentation, stop at Docs MCP. The Console endpoint is not a general connection path for arbitrary MCP clients. If you have a pre-registered pilot client, continue below.
{consoleOrigin} means the origin shown on the signed-in 86d Console Agent access page. Copy the URL from that page for your environment.
Unauthenticated path: Docs MCP
Point any MCP-compatible client at:Authenticated path: Console product MCP
Console product MCP is the current Remote OAuth MCP pilot implementation. Its URL on your Console origin is:Discovery
At{consoleOrigin}:
Clients discover the resource and authorization server from those documents. An unauthenticated request to
/api/mcp receives HTTP 401 with a WWW-Authenticate bearer challenge pointing to the protected-resource metadata. Do not invent alternate OAuth endpoints.
OAuth
- Grant type: authorization code with PKCE
- Dynamic client registration is disabled
- Only pre-registered pilot clients can connect
- There is no public self-serve client onboarding
prompt=create. Create your 86d account outside that authorization request, then start a new OAuth connection from the registered client.
A successful grant is scoped to the business and store selected when access was approved. The scopes in this pilot are store:read and store:update. store:update requires update permission on that store. A missing or invalid token does not reveal store data.
What you do in Console
- Sign in to 86d Console.
- Select the Business and the Store the client may touch.
- Review the client and requested scopes on the OAuth consent page.
- Allow or cancel the request. The consent page does not offer scope editing.
Find the granted store
After OAuth, call MCPresources/list and read 86d://agent/store with resources/read. Its JSON text contains the exact storeId and businessId bound to the grant:
storeId in tool calls. The resource contains no credentials. An invalid or revoked grant does not expose it. A 12-character store slug alone is rejected by the MCP store binding.
Pilot tools
Four tools, all bound to the one selected Store:
The MCP server returns tool input schemas through
tools/list. Read those schemas before calling a tool. Both command tools require a client-generated idempotency key. The store:update scope also permits the read tools, but a read-only grant cannot prepare or apply a change.
Read tool results
The two read tools return operation data directly in MCPstructuredContent. The two Command tools return a Command response envelope in structuredContent:
An MCP tool call can return without a transport error while its Command envelope has
ok: false. An MCP isError result is another failure path. Handle both before using a review link or reporting that an update applied.
Review and apply a change
- Call
stores_prepare_updatewithinput.idset to the grantedstoreId,input.edit.nameorinput.edit.descriptionset to the merchant-supplied value, and a uniqueidempotencyKeyof 8 to 200 characters. Continue only afterok: trueandreceipt.status: "succeeded". Thereceipt.resultthen containschangeSetIdand an absolutereviewUrl. - Give
receipt.result.reviewUrlto the person who will approve the change. Its path is/stores/reviews/{storeId}/{changeSetId}on the Console origin. The person signs in, checks the before and after values, effects, charges, permissions, and validation blocks, then approves the exact Change Set. - Call
stores_get_update_change_setwithstoreIdandchangeSetId. This query returns its status directly. Ifstatusisapproved, callstores_updatewithinputset to the exact returnednextAction.input, the returnedapprovalReference, and a freshidempotencyKey. Do not change the approved input or invent a reference. - If the proposal is
conflicted, prepare it again and request another review. If it isfailed, stop and report the failure. Forstores_update, check its Command envelope and succeeded receipt before reporting that the change applied.
stores_update does not let the agent approve its own proposal. Changing store identity requires human review and exact approval in 86d Console. Approval alone does not apply the change; the authorized agent must execute the approved action.
There are no Order, Payment, Inventory, Product, provisioning, or billing tools on this surface today.
What this pilot does not prove
- General MCP client registration or marketplace onboarding
- Production agent deployment for every merchant
- Broad commerce operations beyond the four Store tools above
- A completed live Agent pass against production launch evidence
OpenAPI boundaries
Do not confuse three different HTTP surfaces:
The Console OpenAPI document requires a signed-in Console session and returns 401 without one. It filters operator-only operations for other accounts and is served with private, no-store caching. OAuth MCP bearer tokens and store API keys do not authorize this document or its Console session HTTP operations. The website OpenAPI file is public and separate.