Skip to main content
The merchant MCP accepts one credential: an OAuth 2.1 access token from a storekit dashboard sign-in. Every tool call is scoped to the account the token resolves to; nothing in a tool’s arguments can change that. storekit API keys do not work with the MCP. A request with an x-api-key header is refused with 401 and the WWW-Authenticate header below, even if it also carries a bearer token; connect with OAuth instead. An account whose MCP access is Off is refused with 403. An unauthenticated request receives 401 with a WWW-Authenticate header (below).

OAuth

The endpoint is an OAuth 2.1 protected resource. The authorisation server is hosted by Scalekit, with the login itself delegated to the storekit dashboard, so a user signs in with their normal storekit credentials.
1

Discovery

An unauthenticated POST /mcp returns:
GET that URL for the protected-resource metadata:
The authorisation server’s own metadata is at its /.well-known/oauth-authorization-server path, as usual. Clients register themselves with it; there is no client ID or secret to configure. Clients supporting the MCP authorisation spec (Claude, ChatGPT, Cursor, VS Code, Claude Code) do all of this without configuration.
2

Sign-in

The authorisation server redirects the user to the storekit dashboard, which shows Connecting your MCP client, please wait… while it confirms the login request with the storekit API, then redirects back to the client. A user who is not signed in to the dashboard signs in first. If the user belongs to several accounts, the token resolves to their first account; there is no account picker.The dashboard refuses the sign-in when the account’s MCP access is Off, or when the user does not have access to all venues on the account. Token use is refused with 403 in the same two cases.
3

Calls

Send the access token as Authorization: Bearer. The token’s sub is the storekit user; its scope claim is attached to the request as scopes (defaulting to read). Write tools for OAuth users are controlled by the account’s MCP access setting, not by this scope. Refresh as your OAuth library dictates; an expired token gets a 401 and the client re-runs discovery.
Dashboard user roles do not apply to MCP. Only users with access to all venues can connect, and a connected user reads every venue on the account and, unless MCP access is Read only, can call all ten write tools. Choose who connects accordingly — see Permissions & Privacy.

Checking the Endpoint

An unauthenticated call is enough to confirm the server is reachable and to see the discovery header a client follows:
Expect 401 Unauthorized with the WWW-Authenticate header shown above. Questions about access or the beta: mcp@storekit.com.

Origin and Host Checks

Requests carrying an Origin header are checked against storekit’s allow-list of browser origins when one is configured, and rejected with 403 before authentication if they do not match. Requests without an Origin header — every desktop client, CLI and server — pass straight to authentication. The Host header must match the public hostname.

Rate Limit

60 requests per minute, counted per user. The count runs in fixed one-minute windows, after authentication, so unauthenticated requests are answered 401 and not counted. Exceeding it returns HTTP 429 with a Retry-After header, outside the MCP envelope.