> ## Documentation Index
> Fetch the complete documentation index at: https://docs.coverbase.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Troubleshooting
> Common issues when connecting and using the Coverbase MCP server.
For AI agents: a documentation index is available at [https://docs.coverbase.com/llms.txt](https://docs.coverbase.com/llms.txt) — this page is also available in markdown by appending .md to the URL.
## Connection issues
Confirm your Coverbase user has API access enabled. Some plans gate this; your admin can confirm in account settings.
Also confirm the client supports OAuth 2.0 for MCP, not just API-key configurations. Older MCP clients sometimes only support stdio transport, which won't work with the Coverbase server.
Check that your browser allows pop-ups from the AI client's domain and that you're signed into the correct Coverbase account in the browser session handling the OAuth callback.
If you have multiple Coverbase accounts, sign out of all of them in the browser first, then re-initiate the connection so you're prompted to sign in fresh.
A command-line client such as Claude Code may report an error like:
```text theme={null}
SDK auth failed: HTTP 403: Invalid OAuth error response:
SyntaxError: ... Unrecognized token '<'. Raw body: ... 403 Forbidden ...
```
This happens when something in front of the server returns a raw HTML `403` page where the client expects a JSON OAuth response. The usual cause is a web application firewall that blocks requests with no `User-Agent` header — command-line MCP clients built on Node send their OAuth and tool requests without one. The Coverbase MCP server explicitly allows header-less requests on the MCP, OAuth, and discovery paths, so on the hosted server this is resolved.
If you still hit it:
* Make sure you added the server with the HTTP transport: `claude mcp add --transport http coverbase https://mcp.coverbase.app/mcp`.
* Update to the latest version of your client and retry.
* If you front the server with your own proxy or firewall, allow requests with a missing `User-Agent` on the `/mcp`, `/oauth/`, and `/.well-known/` paths.
If the error persists, contact [support@coverbase.ai](mailto:support@coverbase.ai) with the client name and version.
## Permission and visibility
The connector enforces your role and permissions. If a record is restricted (for example, an assessment in a restricted folder), it will be invisible to the connector even if you can find it elsewhere in the UI.
Ask your Coverbase admin to confirm the scope of your role.
Search uses partial-name matching but is case-insensitive. Try a shorter query (just the first distinctive word of the vendor name).
If the vendor was recently created or renamed, it may take a few minutes to index. Try again after a short wait.
## Write actions
Every write tool requires `confirm=true`. If the assistant is calling the tool without confirmation, the call returns a precondition error rather than executing silently.
Re-issue the request and approve when the assistant proposes the change. If the assistant isn't surfacing a confirmation step, that's a client behavior issue; report it to your client vendor.
Refresh the affected record in the Coverbase UI. Some object types cache briefly.
Check the audit trail for the record (Vendor → Activity, Assessment → Activity, etc.) to confirm the write was applied. If the audit trail shows the action but the UI doesn't reflect it, report it to support.
## Rate limits and performance
The MCP server applies the same per-org rate limits as the underlying Coverbase API. If you hit a limit, you'll see an explicit rate-limit error with a `retry_after` hint.
For production use cases that require higher throughput, contact your account manager.
Some tools (notably `get_org_activity_digest` and `get_vendor_detail`) consolidate many internal calls into one to save tokens, which can be slower on accounts with very large data volumes. Try narrower scoping (specific vendor ID, shorter time window).
## Other
Try removing and re-adding the connector. If the issue persists, contact [support@coverbase.ai](mailto:support@coverbase.ai) with a screenshot.
If it speaks MCP with OAuth 2.0 and Streamable HTTP transport, it should work. Let us know what you're using and we'll add it to the test matrix: [support@coverbase.ai](mailto:support@coverbase.ai).
## Status and updates
status.coverbase.com
Tool additions, parameter changes, and deprecations with at least 30 days notice for breaking changes.
## Contact
[support@coverbase.ai](mailto:support@coverbase.ai)
[security@coverbase.ai](mailto:security@coverbase.ai)
[privacy@coverbase.ai](mailto:privacy@coverbase.ai)