ecompick.
For makers中文Submit a tool

Popular seller tasks

Product & keyword researchListings & product copyProduct photosProduct video & ad creativeAdvertising & PPCEmail & marketing

Saleor MCP

Retrieve product information from a Saleor instance

SaleorOpen source
#mcp
Visit website

Overview

Saleor MCP is an official read-only connector for commerce data. It gives an assistant product, customer and order context without exposing Saleor mutation tools.

Who it suits

Technical commerce teams running Saleor who need product and order context for an investigation while keeping the MCP tool surface read-only.

Who it may not suit

Store operators seeking an assistant to edit products, issue order changes, or write customer records through this connector.

Seller use cases

  • Retrieve a product’s information to explain a catalog issue without changing its record.
  • Read order context for a support investigation, then handle any required correction in the authorized commerce interface.
  • Bring relevant customer and order information into a scoped analysis while limiting exposure of personal data.

What you can do

  • Retrieve product information from a Saleor instance. ↗
  • Read order context for operational investigations. ↗
  • Query customer data within the token’s authorized scope. ↗

What you need

  • Saleor API URL and token; the hosted service requires a saleor.cloud instance compatible with Saleor 3.21+.

Install

VS Code / Copilot

{
  "servers": {
    "saleor-mcp": {
      "type": "http",
      "url": "https://mcp.saleor.app/mcp",
      "headers": {
        "X-Saleor-Auth-Token": "YOUR_TOKEN",
        "X-Saleor-API-URL": "https://example.saleor.cloud/graphql/"
      }
    }
  }
}
Installation source ↗

Permissions & data

The service receives your Saleor URL and token in headers and returns store data to the client. Local deployment runs Python.

Project info

Maintainer
saleor
GitHub stars at check date
19
Last commit
2026-10-23
License
AGPL-3.0
Last checked
2026-10-30
GitHub ↗

Pricing at a glance

The repository offers local Python deployment and documents a public hosted endpoint. It lists no standalone connector subscription; Saleor infrastructure and the assistant used to inspect its results have their own operating costs.

Open source

Good to know

The hosted service only accepts the documented saleor.cloud environment and Saleor version range. Although the token requires named management permissions, this MCP exposes no mutation tools; keep the credential’s wider capabilities in mind.

Alternatives to Saleor MCP

Medusa Agent Skills help build another headless-commerce stack; Saleor MCP reads data from an existing Saleor deployment.

GeLi2001 operates Shopify Admin records with read and write tools, so it suits a different store backend and permission model.

BigCommerce API MCP targets BigCommerce and can register writes explicitly; Saleor’s connector remains read-only.

Frequently asked questions

Can this MCP update Saleor products?

The official README explicitly describes it as read-only. Product and order mutations are not part of the exposed tool surface.

Will the public endpoint connect to any Saleor URL?

The hosted deployment is restricted to saleor.cloud instances compatible with Saleor 3.21 or later. A local deployment has separately configurable allowed-domain rules.

What is required in the connection headers?

The documented setup uses X-Saleor-API-URL and X-Saleor-Auth-Token. Supply them through the client’s protected connection configuration rather than in analysis prompts.

Why does the token need management permissions for a read-only server?

The README specifies permissions needed to reach the available Saleor data. The MCP’s absence of mutation tools limits its interface, while the underlying token can still carry broader authority outside that interface.

Checked against the official site on 2026-10-30 · Official source ↗

Sources