Shopify MCP means connecting an AI assistant to Shopify through the Model Context Protocol, so the assistant can act on real store data instead of guessing. There is no single "Shopify MCP": Shopify runs several servers that do different jobs, plus third-party ones. Knowing which is which saves you connecting the wrong one and concluding the whole thing does not work.
This is the map: every server, what it can actually do, and the setup for each AI client.
What is MCP, briefly
The Model Context Protocol is an open standard for letting an AI assistant call external tools. Instead of pasting your store data into a chat and hoping, the assistant connects to a server that exposes real capabilities: search this catalog, read these docs, edit this file. The assistant decides which tool to call and the server does the work.
For Shopify that matters because the interesting operations are not text generation. They are "look at my actual theme", "search my actual catalog", "check what this API actually returns". MCP is what turns a chat about your store into work on your store.
The Shopify MCP servers, and what each one is for
| Server | What it does | Who it is for | Auth |
|---|---|---|---|
| Shopify.dev MCP | Searches Shopify's documentation and introspects API schemas so your assistant answers from current docs rather than memory | Developers building apps, themes or integrations | None |
| Storefront MCP | Per-store endpoint: search that store's catalog, manage carts, answer policy questions | Agents shopping on behalf of a customer at one store | None |
| Storefront Catalog MCP | The catalog half of the above, implementing the UCP catalog spec (search_catalog, lookup_catalog, get_product) |
Single-store product discovery | None |
| Global Catalog MCP | Product discovery across the whole Shopify ecosystem, results clustered across merchants | Comparison shopping and cross-merchant recommendations | None |
| Third-party servers (including Clyro's) | Whatever the vendor exposes. Ours edits themes: read files, write sections, generate and preview | Merchants and developers changing a store | Yes, per account |
The distinction that trips people up: Shopify's own servers are about reading and shopping, not about building your storefront. The dev MCP reads documentation. The Storefront and Catalog servers read products and manage carts. None of them edit your theme, which is why "I connected Shopify MCP and it could not change my store" is a common and entirely correct observation.
Shopify.dev MCP
Announced in March 2025 and expanded through the year to cover the Storefront API, Partner API, Customer Account API, Payment Apps API, Polaris Web Components and Liquid. It gives an assistant two things: search over Shopify's live documentation, and schema introspection so generated GraphQL is validated against the real schema rather than invented.
If you write code against Shopify APIs, this is the one that stops your assistant confidently hallucinating a field that does not exist. Setup is in Shopify's own docs.
Storefront MCP
Every Shopify store exposes its own MCP endpoint covering product search, cart operations and policy questions. It requires no authentication, which is deliberate: it is built for agents shopping on a customer's behalf, not for store administration. Shopify notes that some stores may restrict access, so test against the specific store you care about. The reference is in the storefront MCP docs.
The Catalog servers and UCP
Both catalog interfaces implement the Universal Commerce Protocol catalog capability, which is the emerging standard for how agents discover products. Storefront Catalog covers one store; Global Catalog covers the ecosystem, clustering results by a Universal Product ID so an agent can compare offers from several merchants for the same item.
Two rules from Shopify's usage guidelines are worth knowing before you build on these: you may not cache search results or re-use product images, because both must reflect live merchant pricing and presentation. Catalog queries are also rate-limited, and keyless access cannot request an increase.
Where theme editing fits
None of the above touches your storefront's code. That is the gap third-party servers fill, and it is what Clyro's MCP server does: connect Claude, ChatGPT, Claude Code or Cursor to your themes and edit them in conversation, with the changes landing as real Liquid you own. On the Free plan those edits cost zero credits, up to 300 requests a week.
How to get started with Shopify MCP
The path depends on which server you need, but the shape is the same everywhere.
- Decide what you want the assistant to do. Read docs and write API code, shop a catalog, or change your storefront. Those are three different servers.
- Get the endpoint. Shopify's dev MCP and Storefront MCP endpoints are in their docs; a third-party server gives you one when you connect your account.
- Add it to your client. Claude and ChatGPT take a connector URL in settings. Claude Code and Cursor take a JSON entry in a config file. The exact steps per client are in our MCP guide.
- Verify with one call. Ask the assistant to do the smallest real thing: list your themes, look up one product, fetch one doc page. If that works, everything else is scope.
Expect the first attempt to feel underwhelming and the second to feel like a different tool. The value is not in the connection, it is in stopping the copy-paste loop between a chat window and your admin.
Which MCP server should you use?
- Building apps or themes as a developer: Shopify.dev MCP, for docs and schema accuracy.
- Building a shopping agent for one store: Storefront MCP.
- Building product discovery across merchants: Global Catalog MCP.
- Changing your own store's design or code: a third-party server, because Shopify's do not do this.
- All of the above: MCP clients connect to several servers at once, and this is the normal configuration rather than an edge case.
FAQ
What does MCP mean in Shopify? MCP is the Model Context Protocol, an open standard for connecting AI assistants to external tools. In Shopify's case it lets an assistant search documentation, query a store's catalog, manage carts, or, through third-party servers, edit a theme. It is a connection standard rather than a Shopify feature.
Is there an official Shopify MCP server? There are several. Shopify runs the dev MCP for documentation and API schemas, the Storefront MCP for per-store catalog and cart operations, and Storefront and Global Catalog MCP for product discovery under the Universal Commerce Protocol. They are official and they are separate.
What's the best MCP server for Shopify? There is no single best one because they do different jobs. Match the server to the task: dev MCP for writing code against Shopify APIs, Storefront MCP for shopping agents, Catalog MCP for cross-merchant discovery, a third-party server for editing your storefront. Most setups run more than one.
How do I connect Shopify MCP to Claude? Claude takes a connector URL in its settings; Claude Code takes a JSON entry in its MCP config. The per-client walkthrough, including ChatGPT and Cursor, is in our MCP documentation. For Shopify's own servers, their docs carry the endpoints.
Does Shopify MCP require authentication? Shopify's dev MCP and Storefront MCP do not, which is why they are limited to reading and shopping operations. Anything that changes your store requires an authenticated connection, which is what third-party servers provide.
Can Shopify MCP edit my theme? Not the Shopify-run servers. They read documentation, search catalogs and handle carts. Theme editing needs a server built for it, which is what Clyro's does: it reads and writes your theme files and returns real Liquid you keep.
Is Shopify MCP free? Shopify's servers carry no fee, though catalog access is rate-limited. Third-party servers price their own way. Clyro's is included on the free plan at 300 requests a week with edits costing zero credits.
Keep reading: connect Claude to Shopify, step by step and the full MCP documentation.