Settings, MCP connections lists every AI assistant connected to the store you are working in, such as Claude or ChatGPT, what each one may do, and when it was last used. It is also where you revoke a connection and cut an app off from your store. If you want to stop an assistant reading your orders, customers or anything else, this is the screen. You need the Settings permission to open it.
Where to find it
- Open Settings.
- Under Developer, open MCP connections.
What the table shows
- App: the name the app reported when it connected.
- Access: either a green Read only tag or an amber Can change your store tag. Hover it to see the full list of permissions that were approved.
- Connected by: the account that approved it. A connection covering more than one store also shows a +N stores tag.
- Connected and Last used: when it was approved, and when it last made a request. Never means it has been approved but has not used the connection yet.
Recent activity
Below the table, Recent activity lists the last changes assistants made to this store, each with an outcome: Done when the change went through, Refused when it asked for something it was not allowed to do, and Failed when it went wrong. Reading is deliberately not listed, because it is frequent and changes nothing. A run of Refused entries is worth a look: it means an app is trying for permissions you did not grant.
Disconnecting
- Tick the connections you want to remove.
- Choose Disconnect connections, or use the delete action on a single row.
- Confirm. Access is cut immediately, on that assistant's very next request.
Disconnecting cannot be undone from here. To let the app back in, connect it again from the app's own settings and approve it, see Connect an AI assistant.
How permissions are decided
- An assistant can never exceed the person who approved it. A staff member with no access to orders cannot grant an assistant access to orders, no matter what the app asked for. See Staff and permissions.
- Permissions are re-checked on every request. Narrow a staff member's access and every connection they approved narrows with it on the next request, with nothing to wait for.
- Remove their access entirely and their connections stop working. The connection is refused rather than silently continuing under someone else's rights.
- On a multi-store connection the weakest store decides. A permission has to hold in every covered store, or it is dropped everywhere in that connection.
- Custom code is owner-only. Permission to add custom JavaScript or CSS can only be granted by the store owner, never by staff, whatever their other permissions.
How this differs from access tokens
Access tokens are for your own scripts and integrations, and they are a different thing from an MCP connection. If one is used with an AI assistant, it is capped to reading only, so it can never become a way around the approval screen. A token created with a limited data window also hides older orders and products from the assistant without saying so, which is a common reason for an answer that looks wrong.
Rules and corner cases
- Connections are per store. The list shows the store you are working in, so check each store separately unless the connection covers several.
- Changing what an app may do means connecting it again. This screen has no edit control, and that is deliberate: both widening an app and narrowing it, say to stop it reading customers while it keeps reading orders, go back through the approval page with fewer or more boxes ticked.
- Disconnecting does not undo what was already done. Orders an assistant moved stay moved, stock it set stays set, and storefront changes stay live. Cutting access stops the next change, not the last one.