Shopify MCP server

Shopify MCP

A single MCP server exposing the full Shopify Admin GraphQL API read surface (version 2026-04) through 6 universal tools. Read-only is enforced at the query-parser level: mutations are rejected before they ever reach Shopify, not merely discouraged. Multi-store by design: one server instance can serve many shops.

Built and maintained by Scalably. Runs on the Model Context Protocol. License: MIT.

Why read-only at the parser level? Giving an AI agent write access to a live store is how you end up with a deleted product or a wrong-priced variant. This server enforces read-only by parsing every query and rejecting mutations before they leave the process, not by trusting the model to behave, and not by relying on Shopify-side scopes alone. It's the safety boundary an agent in production actually needs. (more on the pattern)

<!-- mcp-name: io.scalably/shopify-mcp -->

Install

Claude Code:

claude mcp add shopify -e SHOPIFY_DOMAIN=my-store.myshopify.com -e SHOPIFY_ACCESS_TOKEN=shpat_... -- uvx scalably-shopify-mcp

Codex:

codex mcp add shopify --env SHOPIFY_DOMAIN=my-store.myshopify.com --env SHOPIFY_ACCESS_TOKEN=shpat_... -- uvx scalably-shopify-mcp

Claude Desktop: download shopify-mcp.mcpb from the latest GitHub release and open it.

Setup

Single store (simplest)

• SHOPIFYDOMAIN or SHOPIFYSHOP_DOMAIN - .myshopify.com
• Auth path A: SHOPIFYACCESSTOKEN (legacy shpat_)
• Auth path B: SHOPIFYCLIENTID + SHOPIFYCLIENTSECRET (Dev Dashboard custom app, client-credentials OAuth, 24h tokens auto-refreshed)

The single store registers under alias default; callers can omit the shop argument on tool calls.

Multi-store (agency setups)

Set SHOPIFY_STORES to a JSON object mapping alias to store config:

{
  "main":   {"domain": "my-store.myshopify.com",        "client_id": "...", "client_secret": "..."},
  "outlet": {"domain": "my-store-outlet.myshopify.com", "client_id": "...", "client_secret": "..."},
  "legacy": {"domain": "legacy-store.myshopify.com",    "access_token": "shpat_..."}
}

• Each store can use either clientid + clientsecret (Dev Dashboard OAuth) or accesstoken (legacy shpat).
• Aliases: [a-z0-9][a-z0-9_-]{0,63}, lowercase-normalized on load.
• Token cache is per-store-domain; one throttled store doesn't block others.

Scopes needed (read-only)

Minimum viable: readproducts readorders read_customers.

Recommended baseline: readproducts readorders readcustomers readinventory readlocations readfulfillments readdiscounts readcontent readthemes readfiles readmarkets readmetaobjects readmetaobjectdefinitions readreports readtranslations readlocales readshipping.

Add readallorders for order history older than 60 days. Enable Protected customer data access in Dev Dashboard, Configuration, if the agent needs customer PII.

Tools (6)

Every non-list tool takes an optional shop argument (alias or domain). Required when more than one store is configured; auto-selected when exactly one.

Coverage

Shortened. The full README is on GitHub.