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 set 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. Create or copy a scoped MCP URL

Go to Settings → Connections, create a new MCP URL, and name it something obvious like OpenClaw production agent.

For a quick proof, choose All integrations. For a real agent, choose Custom and grant only the modules that agent should touch. ShopMCP puts the token in the URL, so you paste one value into OpenClaw instead of adding a separate authorization header.

Copy the URL when it appears

ShopMCP shows the full URL once. If you lose it, revoke it and create a fresh one; we only keep a hash after the dialog closes.

3. Register ShopMCP in OpenClaw

On the machine or host where OpenClaw runs, save ShopMCP as a Streamable HTTP MCP server. Replace the example URL with the full MCP URL you copied from ShopMCP:

bash
openclaw mcp set shopmcp '{
  "url": "https://my.shop-mcp.app/api/mcp?token=smcp_xxxxxxxxxxxxxxxxxxxx",
  "transport": "streamable-http",
  "connectionTimeoutMs": 10000
}'

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?token=smcp_xxxxxxxxxxxxxxxxxxxx
OpenClaw's mcp set command saves config. It does not open a live MCP session or prove the ShopMCP endpoint is reachable yet. The first real check happens when an OpenClaw runtime starts and loads the saved server.

4. Check the saved entry

Confirm OpenClaw stored the server:

bash
openclaw mcp show shopmcp --json

You should see shopmcp with https://my.shop-mcp.app/api/mcp?token=smcp_xxxxxxxxxxxxxxxxxxxx, transport: "streamable-http", and no separate authorization header.

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.

Rotating or removing

To rotate access, create a new ShopMCP MCP URL and run the same set command again with the new URL.

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 — create a new URL in Settings → Connections and make sure the OpenClaw config includes ?token=smcp_... in the URL.
  • Tools list is empty — the MCP URL belongs to a workspace with no connected modules, or its custom scope excludes every connected module. Check Settings → Integrations and URL access.
  • Need OpenClaw's side of the config — see the OpenClaw MCP command reference for its registry, transport, and runtime notes.