Skip to main content

​
The client cannot connect

Confirm that the MCP URL is https://api.superdata.so/mcp. Restart the client after installing or updating a plugin. In Claude Code, run /reload-plugins before checking /mcp again.

​
Codex reports invalid transport

If Codex fails to create a chat with invalid transport in mcp_servers.superdata, check ~/.codex/config.toml for an orphaned tool approval table like:
That table is valid only when the same file also defines a complete standalone [mcp_servers.superdata] server with a url or command. For the Superdata plugin, remove only that orphaned table or move the approval setting under the plugin-scoped path:
Keep the rest of config.toml unchanged.

​
Browser authorization does not complete

Sign in with the approved Superdata account that should own the usage. If the account is still waiting for beta approval, OAuth cannot grant MCP access.

​
An API key is rejected

Confirm the environment variable contains the complete sd_live_... value and does not include quotes or whitespace. Check Connections to make sure the key is active. Complete secrets cannot be recovered; create a replacement if needed.

​
Capability discovery finds no match

Describe the entity, signal, or action in different terms, remove an exact category filter, or search with detail: "summaries". Capability discovery does not consume credits.

​
A search returns no matches

No match means the provider operation executed successfully. Inspect the capability again, verify case-sensitive query arguments, and broaden one constraint at a time. The accepted execution consumes one credit.

​
A response is truncated

Reduce the request scope or provider page size. If the capability supports pagination, use only pagination values returned by that same operation.

​
Credits look incorrect

Open Dashboard, choose Current cycle, and inspect recent activity. Successful and No match executions consume one credit. Failed or interrupted execution restores the reserved credit and displays zero credits. Discovery, inspection, and rejected requests also display zero credits.

​
MCP results are missing from a dashboard workspace

MCP result persistence into dashboard workspaces is not currently available. The metered call appears in Usage, while the result remains in the client conversation that requested it.

​
Contact support

Email hey@superdata.so with:
  • The MCP client and version
  • The tool name and approximate timestamp
  • The public error code
  • What you expected and what happened
Never include an API key, OAuth token, or complete private provider response.