Claude connector

ShopMCP for Claude

Connect Claude to the ecommerce systems already authorised in your ShopMCP workspace. It has the same tools and permissions as adding ShopMCP manually.

Before you connect

A ShopMCP account with an active trial or paid workspace.
At least one supported ecommerce, analytics, marketing, support, inventory, or finance integration connected in ShopMCP.
Permission to access the store, account, property, or workspace data you select.

Install and authorise

Open the ShopMCP listing in Claude's Connectors Directory, select Connect, then sign in to ShopMCP. Review the workspace on the consent screen before approving access.

For troubleshooting or MCP clients that accept a remote server URL, use the same ShopMCP endpoint:

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

Do not add an API key or token to the URL. Claude discovers ShopMCP's OAuth configuration and sends the access token as a bearer credential after you approve the workspace.

What Claude can do

Claude can discover the accounts and tools available within the approved ShopMCP workspace, run evidence-backed analysis, and use ShopMCP resources and operator playbooks. The Directory connector and a manually added ShopMCP MCP use the same capability gates.

Review revenue, orders, conversion, channel mix, products, inventory, marketing, retention, and support signals.
Resolve the intended store or account before querying a multi-account connection.
Filter, aggregate, join, and export bounded ShopMCP resources created from authorised reads.
Return evidence checked, data gaps, and an operator-ready prioritisation.

Writes start off

Every integration and account starts read-only. A workspace owner or admin must enable writes for that integration or account in ShopMCP before Claude can discover or call its write tools. Turning on writes does not bypass provider scopes, ShopMCP confirmation and safety controls, or the permissions of a team member's MCP key.

Example prompts

Run my weekly trading review. What changed, why, and what needs attention first?
Which products are losing visibility or revenue, and what evidence supports that?
Review retention and lifecycle performance for the last 30 days. Separate action required, watch, and insufficient evidence.
For the AU store, compare Shopify, GA4, Google Ads and Merchant Center for last week and explain reconciliation gaps.
What integrations and accounts can ShopMCP access for this workspace?

Permissions and data handling

OAuth connects Claude to the same owner or member MCP credential ShopMCP uses for a manual connection. ShopMCP then applies that workspace's member role, enabled modules, selected connections, per-integration and per-account write toggles, tenant isolation, rate limits, and runtime tool classification to every call. Connecting ShopMCP does not expand permissions on Shopify, Google, Meta, Stripe, Klaviyo, or another upstream platform.

ShopMCP processes only the account and platform data needed for the requested tool call. It does not sell connected customer data, use it to train a general model, or collect unrelated Claude conversation history. See the Privacy Policy, Data Processing Addendum, and subprocessors list.

Troubleshooting

Authorisation failed — remove the connector and reconnect so Claude starts a fresh OAuth flow. For a custom connector, confirm the URL is exactly https://my.shop-mcp.app/api/mcp/claude-directory with no query string.
Wrong workspace — disconnect ShopMCP, switch to the intended workspace in ShopMCP, then reconnect and verify the workspace name on the consent screen.
No useful data — confirm the relevant integration and account are connected in ShopMCP and that the upstream account contains data for the requested date range.
Action is unavailable— confirm writes are enabled for that integration or account in ShopMCP, the connected provider credential has the required upstream scope, and the MCP key permits that integration. Refresh Claude's tools after changing access.

If the issue persists, email support@shop-mcp.app with the workspace name, approximate time, and Claude error text. Never send access tokens or integration secrets.