> ## Documentation Index
> Fetch the complete documentation index at: https://storeinspect.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP troubleshooting

> Fix StoreInspect MCP OAuth, client setup, permission, quota, and contact reveal issues.

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/mcp` exactly.                             |
| 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 that has API access.                  |
| 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            | The StoreInspect account is not on a plan with API access.            |
| Missing scope            | The client did not request or receive the scope required by the tool. |
| 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:

```text theme={null}
https://storeinspect.com/dashboard/settings/mcp
```

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

## Quota and credit issues

Ask the client:

```text theme={null}
Use StoreInspect to show my current usage.
```

Then check:

* Request quota
* Search-row quota
* Remaining shared contact credits
* Current plan and API access

See [MCP quotas and credits](/mcp/quotas-and-credits) for how each tool uses quota.

## Contact reveal refused

The `reveal_contacts` tool requires explicit credit-spend confirmation.

This fails:

```json theme={null}
{
  "contact_ids": ["ct_AbCdEf_GhIjKlMnOpQrStUv"]
}
```

This succeeds when you have enough credits and permission:

```json theme={null}
{
  "contact_ids": ["ct_AbCdEf_GhIjKlMnOpQrStUv"],
  "confirm_spend_credits": true
}
```

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

```text theme={null}
Call StoreInspect reveal_contacts with confirm_spend_credits set to true for these selected contact IDs.
```

## Cursor and VS Code JSON issues

For Cursor-style configuration, use:

```json theme={null}
{
  "mcpServers": {
    "storeinspect": {
      "url": "https://mcp.storeinspect.com/mcp"
    }
  }
}
```

For VS Code-style configuration, use:

```json theme={null}
{
  "servers": {
    "storeinspect": {
      "type": "http",
      "url": "https://mcp.storeinspect.com/mcp"
    }
  }
}
```

Restart or reload the client after editing MCP configuration.

## Still blocked

Include the StoreInspect `request_id` when contacting support. MCP tool responses include a `request_id` when StoreInspect receives the request.