Chat clients

Claude Desktop

Claude Desktop is the most popular way to use ShopMCP. Setup is one config file edit and a restart.

1. Find the config file

Claude Desktop reads its MCP servers from a single JSON file:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
  • Linux: ~/.config/Claude/claude_desktop_config.json

If the file doesn't exist yet, create it. Claude Desktop will pick it up on next restart.

2. Paste this snippet

Replace smcp_xxx… with the API key you generated in Settings → API keys:

json
{ "mcpServers": { "shopmcp": { "type": "http", "url": "https://mcp.shop-mcp.app/mcp", "headers": { "Authorization": "Bearer smcp_xxxxxxxxxxxxxxxxxxxx" } } } }
If you already have other MCP servers in mcpServers, add shopmcp as a sibling key — don't replace the whole object.

3. Restart Claude Desktop

Quit Claude Desktop completely (not just close the window), then reopen it. The first start after the config change runs tools/list against ShopMCP and pulls in every tool your enabled modules expose.

You can confirm it loaded by clicking the slider icon at the bottom-left of the chat input — ShopMCP should appear in the MCP servers list with a green dot.

4. Try it

Type a question that touches one of your connected modules:

  • What were yesterday's Shopify orders?
  • Run the morning ecommerce briefing
  • Which GSC queries lost the most clicks last week?

Troubleshooting

  • ShopMCP doesn't show up in the MCP list — your JSON probably has a syntax error. Open the file in VS Code, the red squiggle will tell you which line. Most common cause: a trailing comma after the last key.
  • "Authentication failed" — the bearer token is wrong, expired, or revoked. Generate a new one in Settings → API keys and paste it back in.
  • "Tool not found" — the module that owns the tool isn't enabled for your workspace. Check Settings → Integrations.
  • Tools list is empty — your workspace has no connected modules yet. Go back to the quickstart step 2.