Shopify ships two MCP surfaces: the open-source Dev MCP server for builders (docs, GraphQL schema, store operations) and the Storefront MCP that already runs on every store for AI shopping assistants. Here is how to set up the one you need.
Dev MCP server (for developers)
Shopify open-sourced the Dev MCP server in 2026. It connects coding agents to Shopify's developer docs, GraphQL API schemas and validation tools — no API key needed for docs and schema access. Requires Node 18+.
{
"mcpServers": {
"shopify-dev": {
"command": "npx",
"args": ["-y", "@shopify/dev-mcp@latest"]
}
}
}
In Claude Code, the one-liner is claude mcp add --transport stdio shopify-dev -- npx -y @shopify/dev-mcp@latest. Restart the client; see MCP config file location.
What it gives you: validate GraphQL queries, Liquid templates and UI extensions, and search Shopify docs — without touching a real store.
Storefront MCP (for shopping assistants)
There is nothing to install here. Every Shopify store exposes a live MCP endpoint at /api/mcp that AI assistants use to search the catalogue, manage carts and answer policy questions on a shopper's behalf. If you run a store, it is already on; you just point a compatible assistant at https://yourstore.com/api/mcp.
Verify
For the Dev server, ask: "Validate this Shopify GraphQL query against the Admin API schema." A schema-aware answer confirms it works.
Common problems
- No tools in client — Node 18+ required (
node --version); see Cursor MCP not working. - Confusing the two — Dev MCP is for building apps/themes; Storefront MCP is for shopper-facing AI. They are different jobs.
- Live store mutations — the Dev MCP can touch store operations via the CLI; review write actions before approving. See MCP security best practices.
Going further
Shopify pairs with filesystem and GitHub servers for theme/app work — see the backend developer stack or browse the finance category. Built a Shopify server? Submit it.