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.
Connection issues
The connector authorizes but no tools appear
The connector authorizes but no tools appear
OAuth flow fails or times out
OAuth flow fails or times out
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.
Permission and visibility
Tools return 'permission denied' or 'not found' for records I can see
Tools return 'permission denied' or 'not found' for records I can see
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 returns no results for a vendor I know exists
Search returns no results for a vendor I know exists
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
Write actions are not executing
Write actions are not executing
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.Confirmed write succeeded but the change isn't visible in the UI
Confirmed write succeeded but the change isn't visible in the UI
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
Rate limit errors
Rate limit errors
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.Tools are slow or timing out
Tools are slow or timing out
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
The favicon or logo is not rendering correctly in the connector card
The favicon or logo is not rendering correctly in the connector card
Try removing and re-adding the connector. If the issue persists, contact support@coverbase.ai with a screenshot.
My client is not in the supported list
My client is not in the supported list
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.
Status and updates
Status and uptime
status.coverbase.com
Changelog
Tool additions, parameter changes, and deprecations with at least 30 days notice for breaking changes.