Connect the MCP

Copy-paste configuration to connect the shop MCP on popular platforms.

The shop MCP server runs two ways:

• stdio — the client launches the local shop-mcp binary (good for one developer on one store; key + context via environment variables).
• hosted HTTP — the client connects to a /mcp URL with a Bearer crmk_ key (good for shared/remote use; the key resolves the org/store).

Pick your platform below and paste the config. Replace <your-host> and the crmk_… key with your values (create one under API keys).

// .mcp.json  (project root) — or: claude mcp add
{
  "mcpServers": {
    "shop": {
      "command": "/abs/path/to/shop-mcp",
      "env": {
        "SHOP_GRAPHQL_ENDPOINT": "https://<your-host>/graphql",
        "SHOP_API_KEY": "wmk_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
      }
    }
  }
}

{
  "mcpServers": {
    "shop": {
      "type": "http",
      "url": "https://<your-host>/mcp",
      "headers": { "Authorization": "Bearer wmk_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" }
    }
  }
}

Notes per transport

• stdio needs the shop-mcp binary on the machine and SHOP_GRAPHQL_ENDPOINT
  • SHOP_API_KEY in its env. Optional overrides: SHOP_STORE_SLUG, SHOP_ORG_ID, SHOP_STORE_ID, SHOP_THEME_ID.
• hosted HTTP needs only the URL + Authorization: Bearer crmk_…. Everything (org/store/theme) resolves from the key.

Verify the connection

Once connected, your agent should see the shop tools (try get_context) and the skill catalog. The model can pull a playbook with get_skill (e.g. shop-builder). See Tools and Skills.

Next

• Tools reference · Skills