Shopify MCP is not one server: Shopify runs several, and no, none of them lets an assistant read your products or change a price in your store. They do different jobs. A Dev MCP that hands your AI coding tool Shopify's documentation and API schemas, and a set of catalog and cart servers built for shopping agents rather than for the person who owns the store. None of them is a switch that lets you open Claude and say change my prices.
That distinction is why people get stuck. You read that Shopify has an MCP server, you connect it, and the assistant cannot see a single one of your products. Nothing is broken. You connected the one that serves documentation.
The Dev MCP is documentation and schemas, and it needs no login#
The Dev MCP is the server most articles mean. Shopify describes the toolkit around it as connecting your agent to "developer docs and API schemas", to "code validation" for GraphQL, Liquid and Shopify Extensions, and to store management through the Shopify CLI's own authenticated context.
The MCP server covers the first of those. In Shopify's words, "the server runs locally and doesn't require authentication." Read that twice, because it tells you what the server can reach. A server holding no credentials has no way to know which store is yours.
For Claude Code, Shopify gives one command:
claude mcp add --transport stdio shopify-dev-mcp -- npx -y @shopify/dev-mcp@latest
Restart the client and the assistant can look up the current API surface instead of guessing. If you have watched a model invent a GraphQL field that was removed two versions ago, this is the fix for that.
What the Dev MCP will not do#
The server will not list your products, read your orders, change a price or publish a page. It holds no token pointing at your store, so there is nothing for it to read.
Store management does exist in Shopify's wider AI toolkit. It arrives through the Shopify CLI's authenticated context, with you choosing when a task runs. That is a developer's terminal rather than a chat window, and it assumes the CLI is already logged in.
So the Dev MCP makes an assistant better at building for Shopify. It does not make an assistant an operator of your shop.
The catalog servers are aimed at shopping agents#
The other servers under the Shopify MCP name are Storefront Catalog, Cart and Checkout, part of what Shopify calls the Universal Commerce Protocol. The Storefront Catalog server exposes tools named search_catalog, lookup_catalog and get_product, which sounds like exactly what a merchant wants until you read the requirement.
Shopify's documentation is direct. The endpoint "requires an agent profile", and "every request must include a meta.ucp-agent.profile URL pointing to your agent's UCP profile."
You register an agent profile because you are building a shopping agent that buys from many stores. It is not a step a merchant completes to reach their own catalog. These servers let an AI shopping assistant find and buy your products for a customer, which is a large idea and a different one from the job you opened Claude to do.
What you can get an assistant doing today#
Plenty, as long as you bring the link rather than expecting the assistant to find it.
A store URL is an ordinary URL. Copy a product, collection or cart permalink out of Shopify, and any tool that works on links works on your store. QRFLOW is one of those. Connect it once and you can say make me a dynamic QR code for this product, and the code comes back with a scan counter and a destination you can change later.
Our Claude and ChatGPT connectors cover the setup, and Claude connectors for small business covers the wider idea.
The chore this removes is real. A collection of thirty products needs thirty codes for thirty labels, which is thirty passes through a form. Pasting thirty links into a chat and getting thirty dynamic codes back is the version worth having.
The shape is the same for any tool you connect. An assistant is good at taking a list you already have and doing something repetitive to each item. It cannot, today, go and find those items inside your Shopify admin by itself.
Choosing which Shopify MCP server you want#
Ask what you are trying to do before connecting anything.
Writing code against Shopify's API? You want the Dev MCP, and the command above is all of it. If you are wiring QR codes into your own build instead, our QR code API is the REST route. Building a shopping agent that transacts across many merchants? You want the UCP catalog and cart servers, and you will be registering an agent profile. Running a store and wanting an assistant to take work off your hands? Connect tools that act on links, then feed them links.
That last case is where most store owners are, and it is the one the phrase Shopify MCP serves worst, because it sounds like a door into the admin that nobody has built yet.
Frequently asked questions#
Does the Shopify MCP server need an API key?#
The Dev MCP does not. Shopify states that it runs locally and does not require authentication, which is also why it cannot see your store data. Authenticated store work in Shopify's AI toolkit happens through the Shopify CLI instead.
Can Claude read my Shopify products through MCP?#
Not through the Dev MCP, which serves documentation and schemas only. The Storefront Catalog server can search a merchant's catalog, but it requires a registered UCP agent profile, so it is built for shopping agents rather than a merchant's own chat window.
Can an assistant place orders or change prices in my store?#
Not through the MCP servers described here. Store management tasks run through the Shopify CLI's authenticated context in Shopify's AI toolkit, where you decide when each one executes.
What is the difference between Shopify MCP and the Shopify AI toolkit?#
The toolkit is the wider offering: documentation, code validation and CLI store management for AI coding tools. The Dev MCP is how you reach the documentation half over the Model Context Protocol.
Which MCP servers are useful to a store owner right now?#
Ones that act on something you can paste. A QR code server turns product and collection links into printable codes without a form for each. Ours exposes eleven tools; the developer docs list them. Connect it in Claude or ChatGPT, give it your links, and let it work through the list.
Do I need to be a developer to use any of this?#
For the Dev MCP, effectively yes, since its value is accurate API reference while you build. For link-based tools, no. If you can copy a URL out of your store, you can use them.
Shopify's MCP story is still being built, and the servers that exist serve developers and shopping agents rather than the merchant in the middle. That will change. Until it does, the fastest way to get an assistant working for your store is to hand it links and connect a tool that does something with them.
Make a QR code for a Shopify product in a few seconds, see what a Shopify QR code generator is for, or connect QRFLOW to your assistant and ask for the whole collection at once.