Shop MCP

Agent clients

OpenClaw

Add ShopMCP to OpenClaw's MCP registry so your OpenClaw agents can call the same connected platforms you already manage in ShopMCP.

What this gives OpenClaw

ShopMCP runs as the remote MCP server. OpenClaw acts as the MCP client. Once configured, an OpenClaw agent can discover ShopMCP tools with tools/list and call the platforms connected to your ShopMCP workspace: Shopify, GA4, Search Console, Klaviyo, Stripe, marketplace accounts, inventory systems, and any other modules your API key can reach.

Use openclaw mcp add for this setup. openclaw mcp serve is the other direction: it exposes OpenClaw conversations to external MCP clients, which is not what you need for letting OpenClaw agents call ShopMCP.

1. Connect at least one ShopMCP module

Open Settings → Integrations and connect the platforms OpenClaw should be able to use. You only need one connected module for a first test.

2. Use the ShopMCP OAuth endpoint

ShopMCP's remote MCP endpoint is https://my.shop-mcp.app/api/mcp. OpenClaw supports MCP OAuth, so keep credentials out of the URL and its JSON configuration.

OAuth binds this client to the ShopMCP workspace you approve in the browser. Connecting OpenClaw does not bypass ShopMCP roles, connection scopes, write toggles, or confirmations.

3. Register ShopMCP in OpenClaw

On the machine or host where OpenClaw runs, add ShopMCP as a Streamable HTTP MCP server with OAuth:

bash
openclaw mcp add shopmcp \
  --url https://my.shop-mcp.app/api/mcp \
  --transport streamable-http \
  --auth oauth \
  --connect-timeout 10

The OpenClaw MCP docs describe transport: "streamable-http" as the canonical setting for Streamable HTTP servers. A ShopMCP MCP URL looks like this:

text
https://my.shop-mcp.app/api/mcp
Registry commands save configuration. They do not prove the endpoint is reachable; use the authenticated probe in the next step.

4. Authenticate and run a live probe

Complete ShopMCP OAuth, then test the real MCP session:

bash
openclaw mcp login shopmcp
openclaw mcp doctor shopmcp --probe

Sign in to ShopMCP in the browser and verify the workspace before approving. A successful probe reports the server, discovered tool count, and capabilities. This proves reachability and tool discovery rather than only checking saved JSON.

5. Start a fresh OpenClaw agent turn

Start or restart the OpenClaw agent runtime that should use ShopMCP. Use a normal tool profile such as coding or messaging; OpenClaw's minimal profile hides configured MCP tools.

Then ask for a task that clearly requires ShopMCP data:

  • Use ShopMCP to pull yesterday's Shopify orders and summarize revenue, refunds, and top SKUs.
  • Use ShopMCP to compare last week's GA4 revenue with Google Ads spend and flag anything odd.
  • Use ShopMCP to find GSC queries that lost clicks over the past 28 days.

Reconnect or remove

To change workspaces, run openclaw mcp logout shopmcp, then repeat the login and probe.

To remove ShopMCP from OpenClaw:

bash
openclaw mcp unset shopmcp

Troubleshooting

  • OpenClaw saved the server but the agent cannot see tools — restart the agent runtime, avoid the minimal tool profile, and check that configured MCP tools are not denied in the OpenClaw runtime config.
  • Authentication failed — run openclaw mcp logout shopmcp, then openclaw mcp login shopmcp and finish the browser flow again.
  • Tools list is empty — the approved workspace has no connected modules, or the current member/key scope excludes them. Check Settings → Integrations and the workspace approved during login.
  • Need OpenClaw's side of the config — see the OpenClaw MCP command reference for its registry, transport, and runtime notes.