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

Forty tools, all scoped to the authenticated account. Thirty are read-only (readOnlyHint: true). The ten writes are create-discount-code, update-discount-code, create-payment-link, update-menu-items, snooze-menu-items, unsnooze-menu-items, snooze-menu-categories, unsnooze-menu-categories, snooze-venue and unsnooze-venue. The full input reference is on Tools. The snoozing tools change the availability of menu items, menu categories and whole stores. update-menu-items edits a menu item’s name, description and popular flag. The other writes create and edit discount codes and create payment links. There are no tools to change order state, prices or settings, or to manage users. An account owner or admin can limit every connection to the read tools, or turn MCP off, with MCP access under Settings → Developers & AI. With Read only, write tools are left out of tools/list and refused if called.

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. Arguments that fail a tool’s input schema are refused by the MCP SDK with a plain-text message instead. 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. Most tools work these out from a one-row lookahead; list-transactions and search-customers use the total count.

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.