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 disconnect an app from your store. If you want an assistant to stop 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.
The top of the window also shows the Connection address to add in your AI app, with a copy icon and a link to the setup guide, see Connect an AI assistant.
What the table shows
- App: the name the app gave when it connected.
- Access: a green Read only tag or an amber Can change your store tag. Hover it to see every permission that was approved.
- Connected by: the person who 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 not been used yet.
With nothing connected, the table reads "No AI assistant is connected to this store yet".
Recent activity
Below the table, Recent activity lists the last changes assistants made to this store, each with a result: Done when the change went through, Refused when it asked for something it was not allowed to do, and Failed when something went wrong. Reading is not listed, because it changes nothing. Many Refused entries are worth a look: an app is trying to do things you did not allow.
Disconnecting
- Tick the connections you want to remove.
- Choose Disconnect connections, or use the delete button on a single row (Disconnect this connection).
- Confirm. Access stops on that assistant's very next request.
This cannot be undone from here. To let the app back in, connect it again from the app and approve it.
How permissions are decided
- An assistant can never do more than the person who approved it. A staff member with no access to orders cannot give an assistant access to orders. See Staff members and permissions.
- Permissions are checked again on every request. Narrow a staff member's access and every connection they approved narrows with it right away.
- Remove a staff member and their connections stop working.
- On a multi-store connection the weakest store decides. A permission has to be allowed 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 come from the store owner.
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 can only read, so it can never skip the approval page. A token created with a limited data window also hides older orders and products from the assistant, 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.
- Changing what an app may do means connecting it again. There is no edit button on purpose: to give an app more or less access, disconnect it and connect it again, ticking only what you want.
- Disconnecting does not undo past changes. Orders it moved stay moved, stock it set stays set, and storefront changes stay live.