# Shopify

> Read products, orders, and inventory from your Shopify store.

[Canonical HTML page](https://top-mcps.com/mcp/shopify) · [server.json](https://top-mcps.com/mcp/shopify.json) · [methodology](https://top-mcps.com/about/methodology)

## Install

### Claude Desktop — `claude_desktop_config.json`

Paste under mcpServers. Fully quit and reopen Claude after editing.

```json
{
  "mcpServers": {
    "shopify": {
      "command": "npx",
      "args": [
        "-y",
        "@shopify/dev-mcp"
      ],
      "env": {
        "SHOPIFY_ACCESS_TOKEN": "${SHOPIFY_ACCESS_TOKEN}",
        "SHOPIFY_SHOP": "${SHOPIFY_SHOP}"
      }
    }
  }
}
```

### Claude Code — `CLI or .mcp.json`

Run from your repo. Commit .mcp.json to share with your team.

```shell
# export SHOPIFY_ACCESS_TOKEN=shpat_your_token
# export SHOPIFY_SHOP=your-shop.myshopify.com
claude mcp add shopify -- npx -y @shopify/dev-mcp
```

### Cursor — `.cursor/mcp.json`

Global path: ~/.cursor/mcp.json. Reload window after editing.

```json
{
  "mcpServers": {
    "shopify": {
      "command": "npx",
      "args": [
        "-y",
        "@shopify/dev-mcp"
      ],
      "env": {
        "SHOPIFY_ACCESS_TOKEN": "${SHOPIFY_ACCESS_TOKEN}",
        "SHOPIFY_SHOP": "${SHOPIFY_SHOP}"
      }
    }
  }
}
```

### VS Code — `.vscode/mcp.json`

VS Code uses the "servers" key (not "mcpServers").

```jsonc
{
  "servers": {
    "shopify": {
      "command": "npx",
      "args": [
        "-y",
        "@shopify/dev-mcp"
      ],
      "env": {
        "SHOPIFY_ACCESS_TOKEN": "${SHOPIFY_ACCESS_TOKEN}",
        "SHOPIFY_SHOP": "${SHOPIFY_SHOP}"
      }
    }
  }
}
```

### Windsurf — `~/.codeium/windsurf/mcp_config.json`

Open via Cascade → hammer icon → Configure.

```json
{
  "mcpServers": {
    "shopify": {
      "command": "npx",
      "args": [
        "-y",
        "@shopify/dev-mcp"
      ],
      "env": {
        "SHOPIFY_ACCESS_TOKEN": "${SHOPIFY_ACCESS_TOKEN}",
        "SHOPIFY_SHOP": "${SHOPIFY_SHOP}"
      }
    }
  }
}
```

### Cline — `cline_mcp_settings.json`

Open via the Cline sidebar → MCP Servers → Edit.

```json
{
  "mcpServers": {
    "shopify": {
      "command": "npx",
      "args": [
        "-y",
        "@shopify/dev-mcp"
      ],
      "env": {
        "SHOPIFY_ACCESS_TOKEN": "${SHOPIFY_ACCESS_TOKEN}",
        "SHOPIFY_SHOP": "${SHOPIFY_SHOP}"
      }
    }
  }
}
```

### Continue — `~/.continue/config.json`

Continue uses modelContextProtocolServers with a transport block.

```json
{
  "experimental": {
    "modelContextProtocolServers": [
      {
        "transport": {
          "type": "stdio",
          "command": "npx",
          "args": [
            "-y",
            "@shopify/dev-mcp"
          ],
          "env": {
            "SHOPIFY_ACCESS_TOKEN": "${SHOPIFY_ACCESS_TOKEN}",
            "SHOPIFY_SHOP": "${SHOPIFY_SHOP}"
          }
        }
      }
    ]
  }
}
```

### Codex CLI — `~/.codex/config.toml`

Codex uses TOML. Each server is a [mcp_servers.<name>] subtable.

```shell
# ~/.codex/config.toml
[mcp_servers.shopify]
command = "npx"
args = [
  "-y",
  "@shopify/dev-mcp",
]
env = { SHOPIFY_ACCESS_TOKEN = "${SHOPIFY_ACCESS_TOKEN}", SHOPIFY_SHOP = "${SHOPIFY_SHOP}" }
```

### Zed — `~/.config/zed/settings.json`

Zed calls them "context_servers". Settings live-reload on save.

```jsonc
{
  "context_servers": {
    "shopify": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "@shopify/dev-mcp"
        ]
      },
      "env": {
        "SHOPIFY_ACCESS_TOKEN": "${SHOPIFY_ACCESS_TOKEN}",
        "SHOPIFY_SHOP": "${SHOPIFY_SHOP}"
      }
    }
  }
}
```

### ChatGPT — `ChatGPT → Settings → Connectors → Developer mode`

Enable Developer mode (paid plans) and enter these values in the UI.

```json
{
  "name": "Shopify",
  "transport": "stdio",
  "command": "npx",
  "args": [
    "-y",
    "@shopify/dev-mcp"
  ],
  "env": {
    "SHOPIFY_ACCESS_TOKEN": "${SHOPIFY_ACCESS_TOKEN}",
    "SHOPIFY_SHOP": "${SHOPIFY_SHOP}"
  }
}
```

## At a glance

- **Maintainer:** Shopify
- **Transport:** stdio
- **Auth model:** API key
- **Required secrets:** SHOPIFY_ACCESS_TOKEN, SHOPIFY_SHOP
- **Supported clients:** Claude, Cursor, Any MCP-compatible client, Shopify stores
- **License:** MIT
- **Language:** TypeScript
- **Latest version:** latest
- **Last verified:** 2026-04-19
- **Score:** 61/100 (rubric 2026-04 — see https://top-mcps.com/about/methodology)
- **Source:** https://github.com/Shopify/dev-mcp

## Security & scope

- **Access scope:** read-write
- **Sandbox:** Authenticates with a Shopify Admin API access token scoped to a single shop. Capabilities equal the scopes granted at installation.
- **Gotchas:**
  - The access token is per-shop — switching stores requires a new token and a restarted MCP process.
  - Destructive actions (delete product, refund order) run immediately if the token has `write_*` scopes.

## Quick answer

**What it does.** Wraps the Shopify Admin GraphQL + REST APIs as MCP tools for products, orders, customers, inventory, and fulfillments.

**Best for:**
- Order triage
- Inventory adjustments
- Product-catalog maintenance
- Customer-support agent context
- Sales reporting

**Not for:**
- Storefront rendering
- High-volume unattended fulfillment

## Recipes

### Identify the best-selling products

```
List my 10 best-selling products by units sold in the last 30 days, with: title, units, revenue (in the shop default currency), and current inventory level. Flag any that are low-stock (<50 units).
```

_Tested with: Claude Desktop, Cursor_

## Description

The official Shopify MCP connects AI agents to your Shopify admin API. Fetch orders, inspect product catalogs, adjust inventory, read customers, and trigger fulfillments — a command-line-like surface for the store that runs your business.

## Why it matters

Commerce ops today happen in Shopify admin. Agent-accessible, they happen in chat — "which orders are stuck in fulfillment?" gets an answer and a bulk action in one turn.

## Key features

- Products + variants CRUD
- Orders + fulfillments
- Inventory levels per location
- Customer reads
- Shopify Admin GraphQL support

## FAQ

### Do I need to create a custom app?

Yes. In your Shopify admin, create a custom app with the scopes you need (`read_products`, `read_orders`, `write_inventory`, etc.) and install it to your store. The install flow hands back an admin access token the MCP uses.

### Can it operate across multiple stores?

One store per MCP server instance. For multi-store operations, add multiple entries to your MCP config — each pointed at a different shop domain and token.

### Does it support Shopify's GraphQL bulk operations?

Yes. For large exports (all orders in a date range, full product catalog) the MCP uses bulk operations under the hood, polls for completion, and streams results back — so large queries do not time out.

### Is it safe to let an agent update inventory?

Turn approvals on for writes. Inventory mismatches cascade fast (oversells, cancelled orders). The MCP supports dry-run mode for many write operations so you can preview an agent's changes before approving.

## Changelog

- **2026-04-19** — Refreshed install snippets and fact sheet; verified for 2026.
- **2025-03-25** — Initial directory listing.