Skip to main content
MCP clients connect to StoreInspect with OAuth. Each approved client is tied to your StoreInspect account and the scopes you approved during the connection flow.

​
Open MCP settings

Manage connected MCP clients from the StoreInspect dashboard:
From MCP settings, you can:
  • Copy the hosted MCP configuration.
  • View connected OAuth clients.
  • Revoke clients you no longer use.

​
Revoke a client

Revoke access when you stop using a client, lose access to a device, or want to force a fresh OAuth approval. After revocation:
  • The OAuth consent is removed.
  • Refresh-token access for that client is invalidated.
  • StoreInspect blocks MCP tool calls from that client on the next request.
To reconnect, add StoreInspect MCP in the client again and complete the OAuth flow.

​
MCP connections vs API keys

MCP connections are separate from REST API keys. Do not paste StoreInspect API keys into AI clients. Use the hosted MCP server instead:

​
Permission changes

MCP access is checked at request time. Plan changes can block Store/contact tools while billing tools remain available. Revoked consent, exhausted credits, or missing scopes can still block the relevant tool call even if a client was previously connected. If a client still appears connected but cannot call tools, revoke the connection and reconnect it. See MCP troubleshooting for common errors.