Skip to main content
Connecting an assistant means letting a third-party AI product read your business data. This page sets out exactly what that involves so you can decide who on your team should connect one.

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. Only people with access to all stores can connect an assistant. Someone whose dashboard login is limited to some stores is refused at sign-in with “Your login doesn’t have access to all venues, so it can’t connect an MCP client.” Once connected, the assistant can 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 and edit discount codes, create payment links, edit menu item names and descriptions, and change item, category or store availability by snoozing”.
  • One account-wide switch. Apart from the all-stores rule, 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.
Because access is account-wide and not limited by user roles, connect assistants only for people you would trust with account-wide reporting and, on Full access, with the writes listed below.

Turning Off or Limiting Access

An account owner or admin 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 on every account. Only the API keys card on that page depends on your plan: accounts without API access see a request form there instead.

Read and Write

Thirty of the forty tools are read-only. The ten 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 these writes, there are no tools to change orders, prices, 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, and the values of filters that are not personal data — such as store and order IDs, dates, statuses, rating filters and table numbers. Free text, email addresses, names, codes and payment-link details are not logged this way;
  • a short reason the assistant gives for each call, with personal details removed, and the AI model it reports;
  • which user made the call, and the name and version of the assistant software.
For a sample of calls, storekit’s error-monitoring traces also keep the arguments the assistant sent, including any search text or email address. storekit does not record the data returned to the assistant. This log is used to run and improve the service and to investigate problems. Writes are additionally logged on the server with the account and the user who made them.

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 picture in the top-right corner, then Members (see Team Members). Their sign-in stops working, and so does any assistant they connected.

Users

Managing who has access to your account.

Event Tracking

How storekit handles analytics data more broadly.