Shopify Dev
Shopify Dev MCP is a stdio server published by Shopify as @shopify/dev-mcp. It gives a coding agent five tools for building on Shopify: one that loads API context on demand, three validators for GraphQL, Polaris components and theme files, and a documentation chunk search. It talks to Shopify's public docs, not to your store.
How we started it
npx -y @shopify/dev-mcpUse it if you write Shopify code and are tired of your agent inventing GraphQL fields that were removed two API versions ago. The validators are the real product; they turn a guess into a compile error you can act on. The cost is the boot: we started it and initialize did not return for 60,819 ms, because npx was still fetching the package, and the tools/list payload it then hands you weighs 6,590 tokens. That is a lot of ceiling for five tools, and most of it is one tool's description.
Use it if
Skip it if
The bill for your context window
| Tool | Est. tokens | Described? | Required params |
|---|---|---|---|
| learn_shopify_api | ~2,942 | yes (10111 chars) | 1 |
| validate_graphql_codeblocks | ~1,465 | yes (1019 chars) | 2 |
| validate_component_codeblocks | ~1,284 | yes (2494 chars) | 3 |
| validate_theme | ~546 | yes (964 chars) | 3 |
| search_docs_chunks | ~352 | yes (154 chars) | 2 |
Five tools, 26,416 bytes of tools/list, 6,590 estimated tokens at 4 chars per token. The distribution is lopsided: learn_shopify_api alone carries a 10,111-character description worth about 2,942 estimated tokens, roughly the price of the other four combined. That description is effectively a manual telling the model how to ask for API context, so it is doing real work rather than padding, but it means you cannot trim this server much. Dropping search_docs_chunks, the cheapest at 352 estimated tokens, saves you nothing worth the loss. Either you want Shopify guidance in the window or you do not.
Setup reality
There is no auth dance, which is the nicest thing about it. We ran it with a clean environment and no credentials at all and it came up: the harness scraped zero env var hints, and stderr's last line was the server announcing v1.14.5 on stdio. Transport is stdio, so the command is npx -y @shopify/dev-mcp and nothing else. The one wrinkle is npm noise on first run, including deprecation warnings for inflight and an old glob, which are transitive dependencies rather than anything you configure. Pre-install the package if your agent host has a startup timeout shorter than a minute.
Questions people ask
Can the Shopify Dev MCP server read my store's orders or products?
No. Its five tools cover documentation search, on-demand API context, and validation of GraphQL, component and theme code. There is no store credential anywhere in setup, which is also why it booted for us with an empty environment.
What is it doing during that long startup?
The 60,819 ms we measured is almost entirely npx downloading and installing the package on a cold cache. Subsequent starts read from the npm cache. If your agent runner enforces a boot timeout, install @shopify/dev-mcp ahead of time and point the command at the local binary.
Is 6,590 tokens a lot for five tools?
Per tool, yes. It sits well above the median server in the batch we measured, despite listing fewer tools than most. The weight is concentrated in learn_shopify_api's description, which is a deliberate design choice rather than sloppy schema writing.
Does it replace the Shopify CLI?
No. It validates code your agent writes; the CLI still builds, serves and deploys. The overlap is theme checking, where validate_theme covers similar ground to what the CLI already runs locally.
How this page is made: the server is spawned as an unprivileged user with a clean environment and no credentials, then asked for its tools, resources and prompts over stdio. Token figures are estimates at four characters per token, not a tokenizer count. One run, one machine. Corrections: contact the desk.