Skip to main content
Work through the section that matches what you see. If none of them fit, email mcp@storekit.com with the name of your assistant, the question you asked and the time you asked it — every request carries an ID that we can look up.

​
Connecting

The sign-in link your assistant opened was used already or took too long. Go back to the assistant and start the connection again; do not reload the storekit tab.
storekit could not finish the hand-off to your assistant. Try once more from the assistant. If it fails a second time, your account is probably not yet enabled for the beta — request access, or email mcp@storekit.com quoting the email you signed in with.
  • Your sign-in has expired or was cleared. Use the assistant’s reconnect option (see your connect guide).
  • Some clients need you to switch the connector on inside the chat as well as adding it. Check the chat’s tools menu.
storekit uses MCP Streamable HTTP. A client that supports only stdio or SSE cannot connect directly; see Connect Other Clients for the options.

​
Answers Look Wrong

Name the store in your question. When you do not, order lists cover the whole account and totals are summed across it. If the account has stores in different currencies, account-wide totals are refused and the assistant asks you to pick one.
storekit returns money in minor units (pence, cents) and the assistant has shown the raw number. Tell it “amounts are in pence, show them in pounds”. This is a presentation slip by the assistant, not a data error; the currency is included with every figure.
Check three things:
  1. Which clock. A single store is reported in its local time. Account-wide questions use UTC unless you name a timezone.
  2. Which date. Orders are listed by when they are due (their slot), not when they were placed, unless you ask for “placed” or “created”. Sales stats and top products always use when the order was placed. Refunds use the refund date unless you ask by order date.
  3. Which orders. Totals exclude rejected and cancelled orders and are gross of refunds.
The Reports pages describe how the dashboard counts, so you can line the two up.
One question can cover at most 90 days. Ask in two parts, or ask for a monthly breakdown.
Large order lists report an estimated total for speed; the individual pages are exact. Order lists are also live, so an order that arrives while the assistant is paging can shift the results. Ask again with a narrower period if you need a firm count.
Events per item are capped at 100 in one answer. The summary and totals are still complete; only the individual on/off events are cut. Ask for a shorter period to see them all.
Prices in the top-products answer are current menu prices, for reference. Quantities are historical; prices are not.

​
Slow or Failing Requests

Each request has 30 seconds. Long periods on busy stores can exceed that — ask for a shorter period or one store at a time. If a write timed out, check the dashboard before asking again: the discount code or payment link may already have been created.
Requests are rate-limited per user. Wait a minute and try again. If an automated setup hits this regularly, space out its calls.
This happens when the assistant retries a write after a timeout or a dropped connection. Archive the duplicate discount code or deactivate the duplicate payment link in the dashboard, and keep write approvals set to per call rather than “always allow”.

​
Still Stuck

Email mcp@storekit.com

Tell us the assistant, the question and the time.

Merchant MCP reference

For developers: the protocol, tools and error codes.