MCP Ecommerce

Installation guide

How to install Saleor MCP

In Claude, ChatGPT, Gemini, Microsoft Copilot, Perplexity, Cursor and Claude Code, with what to check before you start and the first prompts to run.

Saleor MCP is a read-only server that exposes channels, orders, products and inventory. Saleor hosts a public version at `https://mcp.saleor.app/` for Saleor Cloud environments (`*.saleor.cloud`). There is no OAuth sign-in. You create an app in the Dashboard and pass its token, plus your GraphQL API address, as two HTTP headers. Self-hosters run the open-source `saleor/saleor-mcp` code from GitHub and should follow that repository's instructions.

A Saleor Dashboard admin should do this, because creating an app with `MANAGE_ORDERS` and `MANAGE_PRODUCTS` permissions needs sufficient rights. Use a dedicated app named `Saleor MCP`, not a personal account. The vendor describes this as an early first iteration, so treat the token as sensitive and check answers against the Dashboard.

Saleor MCP setup guide: Saleor's MCP documentation page on saleor.io, shown in a browser frame (store platform MCP server for e-commerce)
Saleor MCP setup guide preview: Saleor’s documentation on saleor.io, captured Oct 13, 2026. The page may have changed since; the link opens the live version.

Before you start

  • A Saleor Cloud environment on a *.saleor.cloud domain (for the hosted server), or a self-hosted Saleor plus the saleor/saleor-mcp repository from GitHub
  • Dashboard access that allows creating an app under Extensions with MANAGE_ORDERS and MANAGE_PRODUCTS permissions
  • The GraphQL API URL of your instance, in the form https://example.saleor.cloud/graphql/
  • A password manager to store the generated app token
  • An MCP client that supports Streamable HTTP and custom request headers
How it runs
Remote or local
Access
Read-only
Server address
https://mcp.saleor.app/mcp

Saleor MCP in Claude

  1. The vendor docs do not cover Claude.ai or Claude Desktop. Use the client's standard custom connector flow and check whether it allows custom headers.
  2. Create the app in the Saleor Dashboard first: Extensions > Add extension > Provide details manually, name it Saleor MCP, assign MANAGE_ORDERS and MANAGE_PRODUCTS, and copy the token.
  3. Open Settings > Connectors and add a custom connector with the URL https://mcp.saleor.app/mcp.
  4. Saleor MCP needs the headers X-Saleor-API-URL and X-Saleor-Auth-Token. If the connector form has no field for custom headers, it cannot authenticate to this server. Take the exact workaround from Anthropic's documentation.
  5. Run one of the read-only prompts below and compare the result with the Dashboard.

Saleor MCP in ChatGPT

  1. The vendor docs do not cover ChatGPT. Use ChatGPT's standard way of adding a custom MCP connector (Developer mode) by URL.
  2. Create the Saleor app and copy its token as described in the prerequisites.
  3. In ChatGPT, enable Developer mode and add a new connector with the URL https://mcp.saleor.app/mcp.
  4. The server requires X-Saleor-API-URL and X-Saleor-Auth-Token headers. Check whether the connector form supports custom headers. If it only offers OAuth or no authentication, it will not work with this server today.
  5. If headers are supported, enter both values, then start a chat with the connector enabled and run a read-only prompt.

Saleor MCP in Gemini

  1. The vendor docs do not cover Gemini. For Gemini CLI, the standard route is an mcpServers entry in the settings file.
  2. Create the Saleor app and copy its token.
  3. Add an entry for the remote server using the URL https://mcp.saleor.app/mcp. Check the Gemini CLI documentation for the exact key names for Streamable HTTP and for custom headers.
  4. Set X-Saleor-API-URL to your GraphQL URL and X-Saleor-Auth-Token to the token. Avoid committing the settings file to version control.
  5. Restart Gemini CLI, confirm the server is listed, and run a read-only prompt.

Saleor MCP in Microsoft Copilot

  1. The vendor docs show an example mcp.json for Copilot. For GitHub Copilot in VS Code, put it in .vscode/mcp.json.
  2. Create the Saleor app (MANAGE_ORDERS, MANAGE_PRODUCTS) and copy the token.
  3. Add the saleor-mcp server with type set to http, the URL https://mcp.saleor.app/mcp, and the two headers, as in the snippet.
  4. Replace the placeholder values with your token and your https://<store>.saleor.cloud/graphql/ URL. Do not commit the file with a real token.
  5. Start the server from the MCP view in VS Code and confirm the tools are listed.
  6. For Microsoft Copilot Studio, the docs do not cover it. Use its custom MCP tool flow and check that it can send custom headers.
.vscode/mcp.json
{
  "servers": {
    "saleor-mcp": {
      "type": "http",
      "url": "https://mcp.saleor.app/mcp",
      "headers": {
        "X-Saleor-Auth-Token": "<YOUR_APP_TOKEN>",
        "X-Saleor-API-URL": "https://example.saleor.cloud/graphql/"
      }
    }
  }
}

Saleor MCP in Perplexity

  1. The vendor docs do not cover Perplexity. Use the connector settings in the desktop app to add a remote MCP server by URL.
  2. Create the Saleor app and copy its token.
  3. Add a connector with the URL https://mcp.saleor.app/mcp.
  4. The server needs X-Saleor-API-URL and X-Saleor-Auth-Token headers. If the connector UI has no place for custom headers, it cannot authenticate to this server. Check Perplexity's documentation for current support.
  5. If it connects, run a read-only prompt and verify the answer in the Dashboard.

Saleor MCP in Cursor

  1. The vendor docs do not cover Cursor. Use Cursor's standard MCP settings, which read an mcpServers JSON config.
  2. Create the Saleor app and copy its token.
  3. Open Cursor's MCP settings and add a server entry with the url https://mcp.saleor.app/mcp and a headers object.
  4. Set X-Saleor-API-URL and X-Saleor-Auth-Token as in the snippet. Confirm the exact headers key in Cursor's documentation.
  5. Reload Cursor, check the server shows as connected with its tools, then run a read-only prompt.
Cursor MCP config (mcpServers)
{
  "mcpServers": {
    "saleor-mcp": {
      "url": "https://mcp.saleor.app/mcp",
      "headers": {
        "X-Saleor-Auth-Token": "<YOUR_APP_TOKEN>",
        "X-Saleor-API-URL": "https://example.saleor.cloud/graphql/"
      }
    }
  }
}

Saleor MCP in Claude Code

  1. The vendor docs do not cover Claude Code. It adds remote servers with claude mcp add --transport http.
  2. Create the Saleor app and copy its token.
  3. Run the command in the snippet with your token and GraphQL URL. The --header flag is Claude Code's standard way to send headers; confirm it in Claude Code's documentation if your version differs.
  4. Run claude mcp list to confirm saleor-mcp is registered.
  5. Start a session and run a read-only prompt.
Terminal
claude mcp add --transport http saleor-mcp https://mcp.saleor.app/mcp \
  --header "X-Saleor-API-URL: https://example.saleor.cloud/graphql/" \
  --header "X-Saleor-Auth-Token: <YOUR_APP_TOKEN>"

Check that it works

Start with questions that only read data. If these answer from your real account, the connection is good.

  • Which products are running low on stock?
  • Which of my recent orders need attention or action?
  • List the channels configured in my store.

Troubleshooting

+The server rejects my connection or returns an authorization error. What should I check?

Confirm both headers are present and spelled exactly `X-Saleor-API-URL` and `X-Saleor-Auth-Token`. Check that the token belongs to an app with `MANAGE_ORDERS` and `MANAGE_PRODUCTS`, that it was copied in full, and that the API URL is your GraphQL address ending in `/graphql/`.

+Can I use the hosted server with my self-hosted Saleor?

No. The hosted version at `https://mcp.saleor.app/mcp` only allows `*.saleor.cloud` domains. For self-hosted Saleor, run the open-source `saleor/saleor-mcp` repository from GitHub yourself and follow its instructions, then point your client at your own deployment.

+My client has no field for custom headers. Is there another way?

The docs describe header-based tokens only. OAuth and other auth flows are listed as planned, not available. If your client cannot send custom headers, use a client that can, such as VS Code with `mcp.json`, or check that client's documentation for a header option.

Written Oct 13, 2026 from the vendor documentation. Exact menus, addresses and commands change; the official documentation is the source of truth.