> ## Documentation Index
> Fetch the complete documentation index at: https://86d.store/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect an agent to 86d

> Connect to public documentation and understand the bounded Console OAuth MCP implementation and its current access limits.

> [!WARNING]
>
> **In development.** Console product MCP is implemented for a bounded OAuth pilot with pre-registered clients. General client onboarding, production deployment, and the launch Agent pass are not proven. See [maturity levels](https://86d.store/docs/resources/versioning.md).

86d has a public documentation MCP server and a separate Console product MCP endpoint implemented for a limited pilot. The product endpoint uses OAuth and is scoped to one store selected in [86d Console](https://86d.store/docs/resources/glossary.md#86d-console). They do not share credentials, and neither uses a store API key.

| Surface | URL | Auth | What it can do |
| - | - | - | - |
| [Docs MCP](https://86d.store/docs/resources/mcp.md) | `https://86d.app/docs/mcp` | None | Search and read these pages |
| Console product MCP pilot | `{consoleOrigin}/api/mcp` | OAuth, pre-registered client | Four tools for one selected store; an identity update requires exact human approval |

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:

```text theme={null}
https://86d.app/docs/mcp
```

No sign-in. No token. Do not send credentials. The server cannot see a [Business](https://86d.store/docs/resources/glossary.md#business), a Store, an [Order](https://86d.store/docs/modules/orders.md), a [Payment](https://86d.store/docs/modules/payments.md), or a deployment.

Full tool contract: [Docs MCP server](https://86d.store/docs/resources/mcp.md).

For how to build Modules and Templates rather than operate a managed Store, install the [agent skills](https://86d.store/docs/resources/skills.md). Skills hold no credentials and reach nothing at runtime.

## Authenticated path: Console product MCP

Console product MCP is the current [Remote OAuth MCP](https://86d.store/docs/resources/glossary.md#remote-oauth-mcp) pilot implementation. Its URL on your Console origin is:

```text theme={null}
{consoleOrigin}/api/mcp
```

### Discovery

At `{consoleOrigin}`:

| Metadata | Path |
| - | - |
| Protected resource | `/.well-known/oauth-protected-resource` |
| Authorization server | `/.well-known/oauth-authorization-server` |

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

If your client is not registered, [contact 86d](https://86d.app/contact) about pilot access. Registration is controlled by 86d; creating a store API key does not register an OAuth client.

The pilot refuses OAuth authorization requests with `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

1. Sign in to 86d Console.
2. Select the Business and the Store the client may touch.
3. Review the client and requested scopes on the OAuth consent page.
4. Allow or cancel the request. The consent page does not offer scope editing.

The client receives short-lived OAuth tokens for that grant. API keys created under store settings are a separate credential family. They do not authenticate Console product MCP.

### Find the granted store

After OAuth, call MCP `resources/list` and read `86d://agent/store` with `resources/read`. Its JSON text contains the exact `storeId` and `businessId` bound to the grant:

```json theme={null}
{"storeId":"<granted-store-uuid>","businessId":"<granted-business-id>"}
```

Use `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:

| Tool | Scope | Role |
| - | - | - |
| `stores_get_by_id` | `store:read` | Read the granted store by its `storeId` |
| `stores_prepare_update` | `store:update` | Prepare a Change Set for the store name or description |
| `stores_get_update_change_set` | `store:read` | Inspect the proposal status and exact approved action |
| `stores_update` | `store:update` | Apply the approved action with its approval reference |

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 MCP `structuredContent`. The two Command tools return a Command response envelope in `structuredContent`:

| Field | How to use it |
| - | - |
| `ok` | If `false`, inspect `failure` and any receipt. Do not continue as if the Command succeeded |
| `receipt.status` | If `ok` is `true`, check for `succeeded`. `pending` or `running` does not mean the operation finished |
| `receipt.result` | Read only after a succeeded receipt. For `stores_prepare_update`, this contains `changeSetId` and `reviewUrl` |

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

1. Call `stores_prepare_update` with `input.id` set to the granted `storeId`, `input.edit.name` or `input.edit.description` set to the merchant-supplied value, and a unique `idempotencyKey` of 8 to 200 characters. Continue only after `ok: true` and `receipt.status: "succeeded"`. The `receipt.result` then contains `changeSetId` and an absolute `reviewUrl`.
2. Give `receipt.result.reviewUrl` to 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.
3. Call `stores_get_update_change_set` with `storeId` and `changeSetId`. This query returns its status directly. If `status` is `approved`, call `stores_update` with `input` set to the exact returned `nextAction.input`, the returned `approvalReference`, and a fresh `idempotencyKey`. Do not change the approved input or invent a reference.
4. If the proposal is `conflicted`, prepare it again and request another review. If it is `failed`, stop and report the failure. For `stores_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

Treat a successful pilot call as evidence for that call alone. See [What launch evidence means](https://86d.store/docs/operations/launch-evidence.md) and [How agents work with 86d](https://86d.store/docs/concepts/agentic-design.md).

## OpenAPI boundaries

Do not confuse three different HTTP surfaces:

| Document or surface | What it describes |
| - | - |
| Public website OpenAPI at `https://86d.app/openapi.json` | Site contact and discovery operations only |
| Console first-party OpenAPI at `{consoleOrigin}/openapi.json` | The `/api/v1` HTTP transport used by 86d Console; it is not the agent contract |
| Console product MCP | The OAuth MCP pilot above |

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.

## Related pages

* [How agents work with 86d](https://86d.store/docs/concepts/agentic-design.md)
* [Docs MCP server](https://86d.store/docs/resources/mcp.md)
* [Agent skills](https://86d.store/docs/resources/skills.md)
* [How 86d separates product authority](https://86d.store/docs/concepts/architecture.md)
* [Glossary](https://86d.store/docs/resources/glossary.md)
* [Public Beta status](https://86d.store/docs/resources/public-beta.md)
* [Versioning and maturity](https://86d.store/docs/resources/versioning.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.