Chat clients

Claude Desktop and Claude web

Use Claude's Connectors screen first: add the ShopMCP endpoint, sign in with ShopMCP, approve your workspace, and start chatting.

1. Use the ShopMCP connector URL

ShopMCP uses one OAuth-enabled endpoint for Claude:

text
https://my.shop-mcp.app/api/mcp

Do not add an API key to this URL. Claude discovers ShopMCP's OAuth configuration, sends you to ShopMCP to sign in, and asks you to approve the workspace it may access.

2. Add a custom connector

In Claude Desktop or Claude on the web, open Settings → Connectors. Choose Add custom connector. On Team and Enterprise plans, an Owner or Primary Owner may need to add or enable the organization connector before members can connect it.

Name: ShopMCP
URL: https://my.shop-mcp.app/api/mcp
Authentication: OAuth

Save the connector, sign in to ShopMCP when prompted, review the workspace shown on the consent screen, and approve access. Claude then completes the MCP handshake, fetches the ShopMCP tool list, and makes the connector available to your chats.

Anthropic's remote connector flow is the recommended path for Claude Desktop and Claude web because there is no config file to edit, no local server process, and no restart loop.

3. Enable it in a chat

Start a new Claude chat and enable the ShopMCP connector from the chat's connector/tool controls. Ask 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

Allow prompts for every Shopify page — if the prompt says Claude wants to run a command to save or check a page, ask Claude to use ShopMCP read tools and server-side resource analysis instead of per-page shell commands. Copy this into the chat:
```
text
Continue the Shopify read using ShopMCP tools. Do not copy tool-result files or run Bash, cp or jq for each page. Read the returned pagination cursors directly and use ShopMCP resource filter/aggregate tools for stored results. Keep the same store and filters, report any incomplete coverage, and continue from the last confirmed cursor without repeating completed changes.
```
Refresh ShopMCP's tools or start a new chat with ShopMCP enabled if Claude retains the old workflow. These local command prompts are separate from ShopMCP approvals; existing connection permissions and write authorization still apply.
Add custom connector is missing — remote custom connectors require a supported paid Claude plan and may be controlled by your organization owner. The local claude_desktop_config.jsonfile is for local MCP servers and is not a supported fallback for ShopMCP's remote endpoint.
Connector handshake failed — re-check that the URL is exactly https://my.shop-mcp.app/api/mcp, then remove and reconnect ShopMCP so Claude starts a fresh OAuth flow.
Wrong workspace — disconnect ShopMCP in Claude, switch to the intended workspace in ShopMCP, and reconnect. The consent screen shows the workspace before you approve it.
Tools list is empty — your workspace has no connected modules yet. Go back to the quickstart and connect one integration.
Tool not found— the module that owns the tool is not enabled for your workspace or is outside this key's access scope. Check Settings → Integrations and Settings → Connections.