Shopify MCP Server

Official

Build for Shopify with current APIs — the official Dev MCP server for schema-accurate storefront and admin code.

Local serverstdioTypeScriptISC 500

What is the Shopify MCP server?

Shopify's dev-focused MCP server solves the problem every Shopify developer knows: the platform's APIs — Admin GraphQL, Storefront, Functions, Liquid — evolve continuously, and models trained a year ago write confidently against schemas that no longer exist. The @shopify/dev-mcp server grounds your assistant in current Shopify reality.

Its tools are developer-infrastructure rather than store-operations: search official docs, introspect the live Admin GraphQL schema (fields, types, connections as they exist today), and validate generated queries against that schema before they reach your codebase. The result is GraphQL that compiles and Liquid that renders, first try, far more often — schema introspection turns "I think products have a metafields connection shaped like…" into a lookup.

For app and theme builders the workflow is straightforward: keep the server connected while your coding assistant works, and Shopify-specific questions route through real docs and real schemas automatically. Polaris component guidance and Functions patterns come along for the ride.

Note the scope: this is the dev server — it doesn't read or mutate your store's orders and products (community servers and Shopify's storefront-agent tooling cover operational use). No API key is needed for docs and schema work, which makes setup a one-liner and the trust decision trivial. If you ship Shopify apps or themes with AI assistance, this is as close to mandatory as MCP servers get.

Working patterns for app builders

  • Introspect first, generate second. Asking for the shape of a type and then the mutation yields far fewer invented fields than asking for the mutation cold.
  • Run validate_graphql_codeblocks over anything the assistant writes. It catches deprecated fields and wrong connection shapes before your dev store answers with a 400 and a vague message.
  • Admin API versions ship quarterly and deprecate on a published schedule, so name the version you are targeting when working against anything other than the current release.
  • Its docs coverage spans Admin, Storefront, Functions and Liquid — keep it connected while writing theme code and Function inputs too, not only app backends.

What you can do with it

Schema-correct GraphQL

Admin API queries validated against today's schema before they hit code.

Doc-grounded app building

Functions, webhooks and auth flows answered from official docs.

Theme work

Liquid and Polaris guidance that matches current platform behaviour.

Available tools

ToolWhat it does
search_docs_chunksSearch current Shopify developer documentation
fetch_full_docsRead complete docs pages
introspect_graphql_schemaExplore the live Admin GraphQL schema
validate_graphql_codeblocksCheck generated GraphQL against the real schema

How to install the Shopify MCP server

{
  "mcpServers": {
    "shopify-dev": {
      "command": "npx",
      "args": ["-y", "@shopify/dev-mcp@latest"]
    }
  }
}

Configuration

Node.js 18+. No API key or store access needed — it's documentation and schema tooling.

Example prompts to try

  • Introspect the Admin schema: how do I query orders with their fulfillment holds?
  • Validate this GraphQL mutation for creating a discount against the current API.
  • Search Shopify docs for the current app-auth flow for embedded apps.

Frequently asked questions

No — the dev server does docs, schema introspection and validation only. Operational store access (orders, products) is a different, credentialed problem served by other tools.