Skip to main content
AI connections lists the AI clients you have connected to Retailgrid, and lets you cut any of them off. Retailgrid exposes an MCP endpoint, so an AI assistant can work with your catalog and your grids in your own words, without you exporting anything. Open it from Settings in the left sidebar, then AI connections.
Settings - AI connections, with no clients connected yet
AI connections is rolled out per organization. If the tab is missing or the endpoint is not yet available to you, ask us to switch it on for your account and we will send you the endpoint to use.

​
What an AI client can do

A connected client can both read your data and — with your explicit approval on each write — act on it. It always works with your own sign-in, so it can only ever do what you could do in the app yourself. Read — look at your data and reason about it: Act — with your consent — each of these asks you to confirm before it changes anything:
Write actions are never silent. The client asks for your explicit consent before each one, and nothing changes until you confirm. A client still only ever gets the access you have — it can’t reach your teammates’ grids or do anything your account can’t.
Two limits are worth knowing before you ask an assistant a question and wonder why the answer looks thin:
  • Grids are per person, not per organization. A client connected to your account sees the grids you own. Your teammates’ grids stay private to them.
  • Live formula columns are not readable. A client can read canonical and stored columns from a grid; formula columns that compute on the fly are not exposed. If you want an assistant to see a calculation, materialize it rather than leaving it as a live formula.
Paged reads reflect live data rather than a frozen snapshot, so a long walk through a large catalog can see values change underneath it. For a stable, point-in-time extract of your transactions, ask the assistant to start a transaction export (above), which snapshots the data and hands back download links. For scheduled, repeatable extraction into another system, use the public API instead.

​
Connect a client

The connection starts in the AI client, not here. In broad terms:
  1. Add Retailgrid as an MCP server in your client, using the endpoint we provide for your organization.
  2. The client sends you to Retailgrid to sign in, if you are not already signed in.
  3. Retailgrid shows you a consent screen naming the client that is asking for access. Read it, then approve or decline.
  4. On approval the client is connected, and it appears in the list on this page.
Because consent is tied to your own sign-in, a client only ever gets the access you have. Connecting a client does not grant it anything your account cannot already reach, and it does not expose your teammates’ grids.

​
Disconnect a client

Find the client in the list and disconnect it. Access stops immediately: the client’s existing authorization is revoked rather than left to expire. If you want it back later, connect again from that client. Disconnecting is not destructive and does not affect your data. Disconnect when:
  • You are no longer using that assistant.
  • You installed a client on a device you no longer have.
  • You are not sure what a listed client is. Disconnect first and reconnect deliberately.

​
Good practice

  • Review the list periodically. Treat it like any other list of things holding access to your data.
  • Connect one client at a time and check the list afterwards, so every entry is one you recognize.
  • Write actions need your consent. A client can run agents and approve or publish prices, but only after you confirm each action — it can’t change anything on its own or in the background.
  • Prefer the API for integrations. This endpoint is built for interactive assistants. Scheduled syncs into an ERP or BI tool belong on the public API, which is stable, paginated for extraction, and scoped to an organization key rather than one person.