MCP troubleshooting

Use this page when a client cannot connect to StoreInspect MCP or a tool call fails.

Connection issues

Problem	What to check
The client rejects the server URL	Use `https://mcp.storeinspect.com/openai` for ChatGPT or `https://mcp.storeinspect.com/mcp` for other clients.
The client asks for a transport	Choose HTTP, Streamable HTTP, or remote MCP server.
OAuth does not start	Confirm the client supports OAuth for remote MCP servers.
The browser opens but sign-in fails	Sign in with the StoreInspect account you want to connect.
The client shows no StoreInspect tools	Disconnect and reconnect the MCP server, then approve the requested scopes.

Permission and plan issues

StoreInspect checks account access when tools are called.

Error type	What it usually means
No API access	Store/contact tools require an active paid plan. Manage the plan in the StoreInspect dashboard, or use a billing tool through the general MCP endpoint.
Missing scope	The client did not request or receive the scope required by the tool. Reconnect the client and approve the requested permissions.
Revoked client	The OAuth connection was revoked in StoreInspect MCP settings.
Expired or invalid token	Reconnect the MCP client and complete OAuth again.

Open MCP settings:

https://storeinspect.com/dashboard/settings/mcp

Revoke the client, reconnect it, and complete the OAuth flow again.

Quota and credit issues

Ask the client:

Use StoreInspect to show my current usage.

Then check:

Request quota
Search-row quota
Remaining shared contact credits
Trial cap and paid-plan credit total, if the account is on a trial
Current plan and API access

See MCP quotas and credits for how each tool uses quota. If a trial user has spent all 250 trial contact credits, reveal_contacts returns insufficient_contact_credits with a billing action of end_trial_to_unlock_pro_credits. Use the included billing URL to unlock paid Pro credits immediately.

Contact reveal refused

The reveal_contacts tool requires explicit credit-spend confirmation. This fails:

{
  "contact_ids": ["ct_AbCdEf_GhIjKlMnOpQrStUv"]
}

This succeeds when you have enough credits and permission:

{
  "contact_ids": ["ct_AbCdEf_GhIjKlMnOpQrStUv"],
  "confirm_spend_credits": true
}

If an AI client refuses to send the confirmation field, ask it directly:

Call StoreInspect reveal_contacts with confirm_spend_credits set to true for these selected contact IDs.

If the client tries to reveal by name or domain, ask it to use the contact ID from the preview result:

Use the ct_... contact ID from the StoreInspect contact preview when calling reveal_contacts.

Use list_taxonomy first when a client is unsure which categories, countries, roles, apps, pixels, traffic tiers, or revenue tiers are supported. For store search, use technology filters like:

{
  "filters": {
    "apps": {
      "any": ["Klaviyo"],
      "none": ["Recharge"]
    },
    "pixels": {
      "all": ["Meta Pixel", "Google Analytics"]
    }
  }
}

For contact search at a specific store, use store.domains:

{
  "person": {
    "roles_any": ["founder", "ceo"]
  },
  "store": {
    "domains": ["badbirdiegolf.com"]
  }
}

Cursor and VS Code JSON issues

For Cursor-style configuration, use:

{
  "mcpServers": {
    "storeinspect": {
      "url": "https://mcp.storeinspect.com/mcp"
    }
  }
}

For VS Code-style configuration, use:

{
  "servers": {
    "storeinspect": {
      "type": "http",
      "url": "https://mcp.storeinspect.com/mcp"
    }
  }
}

Restart or reload the client after editing MCP configuration.

Still blocked

When contacting support, include the tool name, approximate time of the request, and the error code shown by the MCP client. StoreInspect can correlate these details with its internal request logs.

GETTING STARTED

REFERENCE

SECURITY

Connection issues

Permission and plan issues

Quota and credit issues

Contact reveal refused

Search filter issues

Cursor and VS Code JSON issues

Still blocked

​Connection issues

​Permission and plan issues

​Quota and credit issues

​Contact reveal refused

​Search filter issues

​Cursor and VS Code JSON issues

​Still blocked

Connection issues

Permission and plan issues

Quota and credit issues

Contact reveal refused

Search filter issues

Cursor and VS Code JSON issues

Still blocked