--- title: "Shopify Dev MCP: review, setup & limitations · Undominated.ai" canonical: https://undominated.ai/mcp-servers/shopify-dev/ description: "Search Shopify references and validate GraphQL, Liquid themes and extension code with the publisher’s local developer server." --- # Shopify Dev MCP: review, setup & limitations · Undominated.ai > Search Shopify references and validate GraphQL, Liquid themes and extension code with the publisher’s local developer server. [← Explore all mcp servers](/mcp-servers/) DEVELOPER DOCUMENTATION / Shopify # Shopify Dev MCP Search Shopify references and validate GraphQL, Liquid themes and extension code with the publisher’s local developer server. See setup guidance ↓Original source ↗ SOURCE REVIEW Reviewed 2026-09-21 Evidence 3 linked sources Publisher Shopify Licence ISC (published Dev MCP package) ↗ Read what was—and wasn’t—checked ↓ “A command line tool for setting up Shopify Dev MCP server” Shopify · upstream description ↗ Our analysis follows below. 01 / THE REASONING ## Why this made the selection. - Combines current Shopify docs and schema lookup with platform-specific validation tools. - Runs without merchant authentication for its developer-reference and validation workflow. ### A good fit for - Check Shopify GraphQL or extension code before integration. - Look up supported Shopify APIs and theme guidance. ### Weigh up before choosing - Published builds send usage events that can include tool inputs and results; use the documented opt-out for sensitive work. - A local process still fetches developer resources and can read theme/project material. It is not an offline privacy boundary. - Merchant operations in the broader AI Toolkit use separate authenticated Shopify CLI workflows; this profile does not attribute them to Dev MCP. 02 / THE REVIEW RECORD ## What we actually inspected. Source review has boundaries. A clear record is more useful than a “safe” badge. ### Material inspected - Current Shopify developer setup page and npm package metadata. - Published package README, ISC licence, manifest, stdio entrypoint and tool/telemetry bundle; tarball integrity matched to registry metadata. ### Our findings - The package exposes documentation/API learning and GraphQL, theme and component validation tools. - The compiled usage handler posts tool parameters and results unless the documented opt-out is enabled. ### Not established by this review - Server launch, authenticated tool calls, and release-to-source parity were not tested. The review applies to the material and revision named here. A newer upstream release can change its behavior. 03 / PUT IT TO WORK ## Connect a server deliberately. Upstream setup instructions ↗ DOCUMENTED COMMAND npx -y @shopify/dev-mcp@latest Copy command ↗ Copying does not execute this command. It may retrieve a newer version than the reviewed source. - Install Node.js and configure npx with @shopify/dev-mcp@latest in your MCP client. - Review telemetry before using sensitive code; set OPT_OUT_INSTRUMENTATION=true or DO_NOT_TRACK=1, or create the documented user-level opt-out file. - Use the client-specific setup guide. The JSON shown follows the published package’s mcpServers example. ### Before you start - Node.js and npm/npx. - Outbound access to Shopify developer resources; readable project paths for local validation. ### Documented configuration example Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts. { "mcpServers": { "shopify-dev-mcp": { "command": "npx", "args": [ "-y", "@shopify/dev-mcp@latest" ] } } } Copy configuration ↗ ### Compatibility Claude Code · Codex · Cursor · VS Code ### Implementation JavaScript ### Transports stdio ### Local developer tools with optional telemetry - Reads developer reference/schema data and validation inputs. - Published releases can send tool input/output usage events to Shopify unless opted out. ### Cost model No merchant account is required for the documented developer-server workflow; model-client and Shopify service terms are separate. 04 / FOLLOW THE EVIDENCE ## The source trail. Our notes are separate from the original resource. Check upstream before adopting a new version. - Shopify Dev MCP setup and scope ↗ Checked 2026-09-21 https://registry.npmjs.org/@shopify%2fdev-mcp/latest Supports: summary, upstreamDescription, whySelected, bestFor, limitations, install, access, compatibility, transports, review - Shopify official client setup ↗ Checked 2026-09-21 https://shopify.dev/docs/apps/build/devmcp Supports: install, compatibility, summary - Publisher-distributed package: README, licence, entrypoint and tools ↗ Checked 2026-09-21 https://registry.npmjs.org/@shopify/dev-mcp/-/dev-mcp-1.15.4.tgz Supports: upstreamDescription, whySelected, bestFor, language, transports, license, limitations, install, access, review KEEP COMPARING ## Other approaches to consider. Related by category or shared topics. These are alternatives to inspect, not a measured quality order. [### Context7 MCP ↗ Resolves a library identity and retrieves documentation relevant to a specific coding question through Context7's hosted index.](/mcp-servers/context7/) [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)