Skip to main content
Retailgrid exposes an MCP endpoint, so an AI assistant can read your catalog and your grids and — with your explicit approval on each action — also do work for you, all in your own words and without exporting anything. This page walks through connecting a client. For everything the connection can read and do, and how to manage or disconnect clients, see AI connections.
AI connections is rolled out per organization. If it isn’t available to you yet, ask us to switch it on and we’ll send you the endpoint to use.

​
Connect a client

The connection starts in your AI client, not in Retailgrid. In broad terms:
  1. Add Retailgrid as an MCP server in your client, using the endpoint we provide for your organization.
  2. Sign in. The client sends you to Retailgrid to sign in if you aren’t already.
  3. Approve the consent screen. Retailgrid shows you which client is asking for access. Read it, then approve or decline. Because consent is tied to your own sign-in, the client only ever gets the access you already have — it can’t see your teammates’ grids.
  4. The client connects and appears in the list on the AI connections page.
The exact steps for adding an MCP server differ by client — follow your client’s instructions for Claude, ChatGPT, Cursor, or another MCP-capable tool, using the Retailgrid endpoint at the server-URL step.

​
Try a few questions first

Once connected, confirm it works with a few plain-language questions about your own data:
  • “Show me all overpriced SKUs.”
  • “What is the CPI min price for Category X?”
  • “List my KVI products.”
The assistant answers from the same data and permissions you’d see in the grid. Once you trust the reads, you can also ask it to do things — for example:
  • “Run a profit-maximizing Price Optimization on my Dairy grid.”
  • “Approve every proposed price under a 5% change and publish them.”
Actions like these ask you to confirm before anything changes (see below).

​
Good to know

  • The connection can read and act. It reads your data, and — only after you confirm each action — can run a Price Optimization, edit a grid, or approve and publish prices. Nothing is changed in the background.
  • Every write asks first. A client can’t change a price, run an agent, or edit a grid without your explicit consent on that action, and it only ever acts with your own permissions.
  • A client sees the grids you own, not your teammates’.
  • For scheduled syncs into an ERP or BI tool, use the public API instead — it’s built for extraction, paginated, and scoped to an organization key rather than one person.