Scope
- One account. The assistant sees the storekit account of the person who signed in (their first account, if they belong to several), and nothing else. Every request is scoped to that account on the server; the assistant cannot ask for another account’s data by guessing an ID.
- All stores on that account. Access is not narrowed to the stores a user can see in the dashboard. If a manager who only works one store connects an assistant, the assistant can still report on every store on the account.
- No user-level permissions. The dashboard’s user roles do not apply to the assistant. On an account with Full access, treat “can connect an assistant” as equivalent to “can read everything on the account, create discount codes and payment links, and change item or store availability by snoozing”.
- One account-wide switch. The only control is the account’s MCP access setting, which applies to every assistant anyone on the account connects — see Turning Off or Limiting Access.
Turning Off or Limiting Access
An account Owner can choose what assistants may do under Settings → Developers & AI → MCP access. The dropdown has exactly three options:
The change applies straight away to every assistant connected to the account, whoever connected it. Choosing Off asks you to confirm first. Other team members see the setting greyed out and cannot change it.
Developers & AI is available on storekit+ and on accounts with API access. On other plans, clicking it shows the storekit+ upgrade screen, and MCP access stays on Full access.
Read and Write
Twenty-three of the twenty-nine tools are read-only. The six writes are:
Claude, ChatGPT, Cursor, VS Code and Claude Code ask you to approve a write before it runs by default, but that prompt belongs to the client, not to storekit: a client set to auto-allow tools or a custom agent runs writes without any confirmation. Keep approval prompts on. Apart from creating these codes and links and changing availability by snoozing, there are no tools to change orders, menu content, settings, users or payouts.
Creating a payment link also sends the
payment_link.created webhook if you subscribe to it, exactly as it would from the dashboard.
What Your Assistant’s Provider Sees
Whatever storekit returns to the assistant — order details, customer names, email addresses, phone numbers, feedback text and totals — is processed by the assistant’s provider (Anthropic, OpenAI, Cursor, and so on) under their terms. storekit does not control what they retain or train on. Check their data policies, and prefer business or enterprise plans that exclude training, if that matters to you.What storekit Records
For every request the assistant makes, storekit records:- which tool was called, when, how long it took and whether it succeeded;
- the names and types of the arguments — for example “a store ID and a date range” — but not their values;
- which user made the call, and the name and version of the assistant software.
Disconnecting
Disconnecting is immediate and does not delete anything the assistant has already been shown. Remove the connector in the assistant itself — see the “Disconnecting” section of your connect guide. There is no list of connected assistants in the storekit dashboard. To cut off every assistant on the account at once, set MCP access to Off (see Turning Off or Limiting Access). If a user leaves your team, remove them from the account under Members — click your profile in the bottom-left sidebar (see Team Members). Their sign-in stops working, and so does any assistant they connected.Related
Users
Managing who has access to your account.
Event Tracking
How storekit handles analytics data more broadly.