Reference
Troubleshooting
Most issues fall into one of five buckets. Find yours below — if none of them help, email support and we'll dig into the trace.
My chat client doesn't see ShopMCP
- Did you restart the client? Claude Desktop, Cursor, and ChatGPT cache the MCP server list — a full restart (not just closing the window) is required after adding the config.
- JSON syntax error? Open the config file in VS Code; the red squiggle tells you which line. The most common mistake is a trailing comma after the last key.
- Wrong file path? Each client looks at a specific path — check the client setup pages for the exact location on your OS.
Authentication failed
- The MCP URL is wrong, expired, or revoked. Generate a new URL in Settings → Connections and update your client config.
- You copied only the token instead of the full URL. It should include
/api/mcp?token=smcp_.... - You're hitting a stale local DNS cache.
nslookup my.shop-mcp.appshould resolve cleanly.
Tools list is empty
- No modules connected for this workspace yet. Open Settings → Integrations and connect at least one.
- All your subscriptions are paused or cancelled — check Settings → Billing.
- You're on the wrong workspace. The MCP URL token is workspace-scoped; if you have several workspaces, make sure you generated the URL from the right one.
Rate limited
- Pending (no trial or paid plan yet): tool calls are blocked before they even reach the rate limiter. The error message includes
tenant_action: upgrade. Start a 14-day free trial or pick a plan in Settings → Billing. - Paid plans: 300 rpm is available per workspace. Portfolio pools to 600 rpm account-wide, and Agency pools to 1,200 rpm account-wide. If you're calling fast in a loop, slow down or batch with playbooks.
- Upstream rate limit: Shopify, GA4, and Neto have their own per-account limits. We pass them through with
retryable: trueso the assistant knows to retry.
Tool returns weird data or no data
- Date range too wide: GA4 and GSC throttle very large windows. Try narrowing to 28 days.
- Empty Shopify result: the assistant may have filtered too aggressively. Re-ask with explicit dates.
- "Not found" on a known SKU: the SKU exists in a different store than the one tied to this connection. Disambiguate by passing the store domain.
Still stuck?
Email support@shop-mcp.app with:
- Your workspace name
- The exact error message (and the tool name if there is one)
- The chat client you're using
- Roughly when it happened (so we can find the trace)
We respond inside one business day, usually faster.

