← Explore all 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.

“A command line tool for setting up Shopify Dev MCP server”

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.

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • Shopify AI Toolkit page (the former /docs/apps/build/devmcp URL redirects there) and its .md version, read 2026-10-13.
  • npm registry metadata for @shopify/dev-mcp latest (1.16.0, published 2026-09-25).
  • Published 1.16.0 tarball: README, ISC LICENSE, package.json, dist/index.js and the bundled tool and telemetry module; its sha512 matched the registry integrity value.

Our findings

  • The package exposes documentation/API learning and GraphQL, theme and component validation tools: the 1.16.0 bundle defines learn_shopify_api, search_docs_chunks, validate, validate_graphql_codeblocks, validate_component_codeblocks, validate_theme and validate_theme_codeblocks. The README says validate_theme is registered only when LIQUID_VALIDATION_MODE is full, the default.
  • The 1.16.0 README says published builds send usage events, which can include tool inputs and results, to https://shopify.dev/mcp/usage. The bundle contains that endpoint and the OPT_OUT_INSTRUMENTATION and DO_NOT_TRACK checks.
  • The bundle also defines a feedback tool whose description tells the agent to call it once per turn with a scorecard grading Shopify’s tools and a comment of up to 500 characters.
  • Re-checked against 1.16.0, the latest release on 2026-10-13; the 2026-09-21 review read 1.15.4. The former setup URL /docs/apps/build/devmcp now redirects to the Shopify AI Toolkit page, which recommends the toolkit plugin and lists the Dev MCP server as the MCP alternative.

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

Copying does not execute this command. It may retrieve a newer version than the reviewed source.

  1. Install Node.js 18 or later and configure npx with @shopify/dev-mcp@latest in your MCP client. The command shown is the 1.16.0 README’s run line; the AI Toolkit page wraps the same npx call in each client’s configuration.
  2. 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.
  3. Use the client-specific setup guide. The JSON shown follows the published package’s mcpServers example.

Before you start

  • Node.js 18 or later, with 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"
      ]
    }
  }
}

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. https://registry.npmjs.org/@shopify%2fdev-mcp/latest

    Supports: summary, upstreamDescription, whySelected, bestFor, limitations, install, access, compatibility, transports, review

  2. https://shopify.dev/docs/apps/build/ai-toolkit

    Supports: install, compatibility, summary, configExample, limitations

  3. https://registry.npmjs.org/@shopify/dev-mcp/-/dev-mcp-1.16.0.tgz

    Supports: upstreamDescription, whySelected, bestFor, language, transports, license, limitations, install, access, review, configExample

Evidence & Ask