Skip to content
Menu

MCP server / commerce / source-linked

Shopify Dev MCP

Shopify Dev MCP is the local, stdio server for Shopify developer resources. Shopify’s current documentation groups it under the AI Toolkit and distinguishes it from plugins and skills. The MCP server provides current docs and platform context through @shopify/dev-mcp; it does not directly expose a general store CRUD API. Store-management tasks are handled through authenticated Shopify CLI context in the broader toolkit.

Before you choose.

Identify the implementation and the job it supports.

Which implementation is this?
Shopify Dev MCP
Implementation source ↗

Shopify Dev MCP is the local, stdio server for Shopify developer resources. Shopify’s current documentation groups it under the AI Toolkit and distinguishes it from plugins and skills. The MCP server provides current docs and platform context through @shopify/dev-mcp; it does not directly expose a general store CRUD API. Store-management tasks are handled through authenticated Shopify CLI context in the broader toolkit.

Setup and connection.

The documented interface, authentication and installation path.

Connection / transport
stdio/local
Authentication
No remote OAuth for the Dev MCP server; local Shopify CLI/authentication applies to store tasks in the broader toolkit.

Run the server with npx and add it to the client config. Restart the client. For a broader toolkit, use Shopify’s plugin or skill install paths and follow CLI authentication separately.

Setup reference ↗

Documented setup example. Review the source and credentials before running; this command was not executed for this article.

claude mcp add --transport stdio shopify-dev-mcp -- npx -y @shopify/dev-mcp@latest

What it actually exposes.

Concrete capabilities with maintainer sources.

Documented capability / 01

Current Shopify context

Provide Shopify developer documentation and platform-specific context to a coding agent.

Documentation ↗
Documented capability / 02

Schema and validation guidance

The broader AI Toolkit covers GraphQL, Liquid, Polaris, Functions, Hydrogen, and CLI workflows; the Dev MCP is its local MCP path.

Documentation ↗
Documented capability / 03

Supported coding hosts

Shopify lists Claude Code, Codex, Cursor, VS Code, and other supported agents; Hermes/OpenClaw/Pi are plugin paths in the toolkit.

Documentation ↗

Evidence and method.

What was checked and what was not tested.

WHO

Editorial record

Compiled by clawbot.ai.

HOW

Source method

Public maintainer documentation and repositories. This is not a hands-on product review.

WHEN

Last checked 2026-10-01

Setup examples are documented examples. Suggested trials and comparison advice are editorial guidance.

Sources support the adjacent factual statements. A source review does not establish uptime, performance, security or current account eligibility. Read the editorial policy.

Try a specific task.

A bounded evaluation you can reproduce in your own environment.

Shopify extension migration

Suggested evaluation, not an observed test result.

  1. Install the local Dev MCP server and point the agent at the extension workspace.
  2. Ask it to map API-version, Polaris, and target-specific changes using current docs.
  3. Run the project’s own checks and review the diff before deployment.

What to inspect: A documented migration diff with Shopify-specific validation steps; execution remains with the developer. Proposed workflow; not tested by clawbot.ai.

Workflow reference ↗

Permissions and limitations.

Read these constraints before granting access.

Boundary / 01

The Dev MCP server is local and does not require remote authentication; treating it as a hosted store-data connector is inaccurate.

Boundary reference ↗
Boundary / 02

Generated migrations still need review and local testing; Shopify explicitly says the toolkit does not remove validation work.

Boundary reference ↗

Decide by workflow.

Make the expected output explicit before you connect.

A documented migration diff with Shopify-specific validation steps; execution remains with the developer. Proposed workflow; not tested by clawbot.ai.

Keep the task inputs, tool calls, output and any errors together when you evaluate. The trial above is a proposal, not a recorded result.

Compare the alternatives.

Specific reasons to choose another route, with the tradeoff shown.

Editorial decision guidance inferred from the linked documentation; no quality or speed benchmark.
AlternativeChoose it whenTradeoff
Figma MCP ServerChoose for design-file context and code generation from Figma frames.Figma is remote and design-oriented; Shopify Dev MCP is local and platform-doc oriented.
Documentation ↗
Vercel MCPChoose for deployment/runtime operations after the Shopify app is built.Vercel cannot supply Shopify schema or extension guidance.
Documentation ↗

Questions before setup.

Answers specific to this implementation.

Does this server manage my store?

The Dev MCP is for developer resources. Broader store-management tasks use Shopify CLI context in the AI Toolkit.
Documentation ↗

What is the install command?

For Claude Code, add stdio with npx -y @shopify/dev-mcp@latest; other clients use equivalent local config.
Documentation ↗