Skip to main content
For AI agents: a documentation index is available at https://docs.coverbase.com/llms.txt — this page is also available in markdown by appending .md to the URL.
Coverbase is published in Anthropic’s Connectors Directory, the curated list of MCP servers that Claude users can add to their workspace in a single click. Listed connectors ship with a branded card (logo, tagline, screenshots) and a security review from Anthropic’s team.

​
What this means for you

One-click install

Add Coverbase from Settings → Connectors → Browse directory in Claude.ai. No URL to copy, no permission prompts to dismiss.

Branded card

The Coverbase logo, tagline, and supported tools render natively in the connectors picker — the same visual treatment as built-in connectors.

Anthropic-reviewed

Anthropic reviews every directory submission against their Software Directory Policy for safety, security, and tool design before listing.

Same server, same scope

The directory entry points at the same mcp.coverbase.app/mcp endpoint as a custom connector. Data access is still scoped to your Coverbase user and your org’s permissions.

​
How to add Coverbase from the directory

1

Open Connectors in Claude.ai

Click Settings → Connectors in the sidebar, then Browse directory.
2

Find Coverbase

Search for Coverbase or filter by the GRC / Risk category.
3

Add the connector

Click Add, then Authorize to complete the OAuth sign-in in your browser. You’ll be sent to Coverbase to confirm the connection.
4

Start using it

The Coverbase tools appear in your Claude session immediately. Try one of the example prompts.
Already added Coverbase as a custom connector? You can keep it — the directory entry and a custom entry both point at the same server. Custom connectors render with a generic globe icon, so most users prefer to remove the custom entry and re-add from the directory once they have access.

​
What’s included in the directory listing

  • Server endpoint — https://mcp.coverbase.app/mcp
  • Transport — Streamable HTTP (stateless)
  • Auth — OAuth 2.0 + PKCE
  • Tools — All 11 dispatcher tools (vendor / assessment / finding / engagement / control / questionnaire / radar / platform queries, the get_report aggregations, the mutate write dispatcher, and mcp_capabilities discovery)
  • Resources — Direct URI reads for vendors, assessments, engagements, controls, and findings
  • Prompts — TPRM workflow templates (vendor onboarding, portfolio risk briefing, …)

​
Custom connector vs directory entry

Custom connectorDirectory entry
InstallPaste URL https://mcp.coverbase.app/mcpOne click from Browse directory
Logo in Claude.aiGeneric globeCoverbase branded card
OAuthSame Coverbase OAuth flowSame Coverbase OAuth flow
Tool surfaceIdenticalIdentical
Security reviewSelf-managedReviewed by Anthropic
UpdatesManual reconnect for major changesAnthropic notifies on breaking changes
Both routes connect to the same production server and inherit the same Coverbase permissions. The directory entry is purely an installation and discovery improvement.

​
Other clients

The directory listing is a Claude.ai surface. To use Coverbase from Claude Code, Claude Desktop, Cursor, VS Code, Microsoft Copilot Studio, or any other MCP client, follow the Connecting clients guide — the server endpoint, OAuth flow, and tool surface are identical regardless of where you connect from.