Give AI agents commerce capabilities with merchant scope and action guardrails.

Publication status

Remote MCP: restricted read-only Pilot live at https://merchant.yeedoor.com/mcp. Merchant authorization uses OAuth Authorization Code + PKCE (S256). The authorization server supports mcp:read and optional offline_access. Access tokens expire after 1 hour. A rotating 30-day refresh token is issued only when the client actually requests offline_access; the current ChatGPT development connection requested only mcp:read, so no refresh token was issued and reauthorization after access expiry is the correct fallback. The authenticated user selects a YEEDOOR merchant workspace from their actual membership, and that merchant scope is bound server-side to the access token. The Pilot exposes only five R0 tools: operating snapshot, Shopify catalog, Shopify inventory, Shopify business metrics and Store-to-Google asset inspection. Runtime acceptance is 5/5: operating snapshot and Google asset mapping return real merchant-scoped results; the three Shopify reads correctly return store_not_configured until a Shopify store is registered. Shopify order reads and every R1/R2/R3 action remain outside the Pilot. ChatGPT development custom MCP: connected; OAuth → initialize → tools/list → real yeedoor_get_operating_snapshot call has passed. It is not submitted for public listing.

1. Merchant authorization

YEEDOOR connects providers through their official authorization mechanisms. Provider access tokens and merchant credentials are not published to the model or placed in public documentation.

2. Tenant and store scope

Every read or action must resolve the merchant workspace and, where applicable, the specific store or seller connection before provider data is accessed.

3. Capability discovery

An agent should be able to determine whether a connector is available, whether it is read-only or action-capable, and whether the current merchant granted the required permission.

4. Approval guardrails

Material actions can remain merchant-approved. A recommendation is not automatically equivalent to permission to mutate a store, feed or advertising account.

5. Verification

Supported actions should be followed by a read-back or other verification step so the agent can distinguish a requested change from a successfully applied change.