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.

Shopify

Name: Top MCPs — curated MCP directory
Creator: Top MCPs
License: https://creativecommons.org/licenses/by/4.0/

Official

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

Score 61(?)ShopifyMITVerified May 31, 2026Top MCPs for Commerce & Payments →

Install View on GitHub

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

Not for

Storefront rendering
High-volume unattended fulfillment

Setup recipe

Pick your client, then follow the three steps.

Install

claude_desktop_config.jsonjson

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

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

CLI or .mcp.jsonshell

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

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

.cursor/mcp.jsonjson

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

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

.vscode/mcp.jsonjsonc

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

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

~/.codeium/windsurf/mcp_config.jsonjson

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

Open via Cascade → hammer icon → Configure.

cline_mcp_settings.jsonjson

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

Open via the Cline sidebar → MCP Servers → Edit.

~/.continue/config.jsonjson

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

Continue uses modelContextProtocolServers with a transport block.

~/.codex/config.tomlshell

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

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

~/.config/zed/settings.jsonjsonc

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

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

ChatGPT → Apps directorynone

Shopify is also available in the official ChatGPT Apps directory — no manual setup, no Developer mode required. Open the app from the directory and grant access on first use.

Open in ChatGPT directory

2
Set required secrets
Set SHOPIFY_ACCESS_TOKEN, SHOPIFY_SHOP in your shell environment before launching your MCP client.
3
Try a minimum working prompt
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.

Tools & permissions

Tools list pending verification. The server exposes tools over MCP; we haven’t yet parsed its capability manifest into this page. Check the GitHub repo for the authoritative list.

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.

Agent prompt pack

— copy into Claude, Cursor, or ChatGPT.

Paste into Claude, Cursor, or ChatGPT. Edit the [brackets] before sending.

Recommend the best MCP servers for [task: e.g. commerce & payments work] in [client: Claude].

Constraints:
- Prefer tools that are [official | open-source | read-only] — pick what matters for my use case.
- Exclude MCPs that require [e.g. a paid plan, OAuth-only flows, remote-only transport].
- Return at most 3 picks, ranked.

For each pick include:
1. One-sentence rationale.
2. The ready-to-paste install snippet for my client.
3. Any required secrets I need to create before installing.

Cross-check the top-mcps.com listing: https://top-mcps.com/top-mcps-for-commerce-payments

Compare Shopify against a real alternative. Swap the second MCP in [brackets] if you want a different match.

Compare Shopify MCP vs [Stripe MCP] for the following job: [describe the job, e.g. "let an agent create GitHub issues on bug triage"].

Judge them on:
- Setup time and complexity (what a new user hits first).
- Auth model (none / API key / OAuth 2.1) and credential risk.
- Transport (stdio / Streamable HTTP / SSE) and where the server runs.
- Required secrets and the blast radius if they leak.
- Operational risk in an unattended agent loop.
- Which one is "good enough" for a weekend prototype vs. production.

End with one sentence: which should I pick for my scenario, which is: [my scenario].

References:
- https://top-mcps.com/mcp/shopify
- top-mcps.com listing for Stripe

Asks the agent to install and verify. Works inside Claude Code, Cursor Agent, Codex CLI.

Install the Shopify MCP server for my [client: Claude] at the default config path for that client.

Use the exact install snippet published at https://top-mcps.com/mcp/shopify (fetch https://top-mcps.com/mcp/shopify.json for the canonical server.json if you can read URLs).

Before finishing:
1. Create the required secrets (SHOPIFY_ACCESS_TOKEN, SHOPIFY_SHOP) and put them in the appropriate env block — do not hard-code them.
2. Restart or reload the client so it picks up the new server.
3. Verify the server is connected (green / running state) and at least one tool is listed.
4. If anything fails, read the client's MCP logs and report the exact error — do not silently retry.

Confirm when done and list the tools the server now exposes.

Frequently asked questions

What changed

— 2 updates tracked.

May 31, 2026
Refreshed install snippets and fact sheet; verified for 2026.
Mar 25, 2025
Initial directory listing.

More Commerce & Payments MCPs

Other tools in the same category worth evaluating.

Stripe

Official

Manage payments, customers, and subscriptions through Stripe.

stripepaymentsbillingcommerce

5 minMedium

Compared with Shopify

Side-by-side breakdowns for the choices people most often weigh against this MCP.

ShopifyvsStripe ShopifyvsBrex ShopifyvsEthos

Exploring Top MCPs for Commerce & Payments? See all Commerce & Payments MCPs →