Skip to main content
Who this is for: a developer wiring an AI client or agent to a merchant’s own storekit account. For the customer-side surfaces — an agent reading a public menu and building a basket — see Ordering Agents. For the non-technical setup guides, see Connect Your AI Agent.
Beta feature - The merchant MCP is in beta and accounts are enabled from a waitlist. Request access, or email mcp@storekit.com.

​
Endpoint

Every request creates a fresh MCP server bound to the authenticated account, handles one message and closes. Nothing is remembered between calls; a conversation carries venue IDs and order IDs itself.

​
Tools

Eighteen tools, all scoped to the authenticated account. Sixteen are read-only (readOnlyHint: true); create-discount-code and create-payment-link are writes. The full input reference is on Tools. There are no tools that mutate orders, menus, venues, users or settings.

​
Contract in Brief

  • Every success is a { data, meta } envelope, returned both as structuredContent and as JSON in the first text block. Every tool publishes an outputSchema for it. See Response Format.
  • Errors are text-only isError: true results carrying an { error } envelope with a stable code. See Errors.
  • Money is in minor units with an explicit currency code. Dates are strict ISO. Venue-scoped queries default to the venue’s timezone, account-wide queries to UTC.
  • Pagination starts at page 1, is capped at 100 rows, and reports hasMore/nextPage from a one-row lookahead rather than from totals.

​
Limits

​
Reference

Authentication

OAuth discovery and sign-in, how the account is chosen.

Tools

Every tool with its inputs, defaults and date basis.

Response Format

The envelope, pagination, dates, timezones and money.

Errors

Error codes, retry rules and the shapes clients must handle.