The client cannot connect
Confirm that the MCP URL ishttps://api.superdata.so/mcp. Restart the client
after installing or updating a plugin. In Claude Code, run /reload-plugins
before checking /mcp again.
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 completesd_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.
The tool asks for clarification
This is expected when important targeting context is missing or a taxonomy term is ambiguous. Answer the returned questions and retry. Clarification responses do not consume credits.A search returns no matches
No match means the tool executed successfully. Broaden one filter at a time,
check the country and industry suggestions, or increase the company-size range.
The accepted execution consumes one credit.
The cursor is invalid
Use only the latestnextCursor and keep every search filter unchanged. If the
original request is unavailable, restart the search without a cursor.
Credits look incorrect
Open Dashboard, choose Current cycle, and inspect recent activity. Remember that completed,No match, and failed accepted calls each consume one
credit. Rejected requests 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