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.
The exact connection flow depends on which client you’re using. The general pattern is the same: point the client at the Coverbase MCP endpoint, complete the OAuth flow in your browser, and the tools become available in your session.

​
Server endpoint

https://mcp.coverbase.app/mcp
The server speaks MCP over Streamable HTTP and authenticates with OAuth 2.0 (PKCE, no client secret). On first connection your client opens a browser window so you can sign in to Coverbase and authorize access. Your permissions in Coverbase determine what the connected assistant can see and do.

​
Claude Code

Add the Coverbase server with the HTTP transport: 
claude mcp add --transport http coverbase https://mcp.coverbase.app/mcp
Then start Claude Code, run /mcp, and choose Authenticate to complete OAuth sign-in in your browser. The Coverbase tools are available once the status shows connected.
Use --transport http for the remote Coverbase server. Without it, the CLI assumes a local stdio command and the connection will fail.

​
Claude.ai

1

Open Connectors

In Claude, open Settings → Connectors.
2

Add Coverbase

Click Add custom connector, name it Coverbase, and paste the server endpoint.
3

Authorize

Click Add, then Connect. You’ll be redirected to Coverbase to sign in, review the requested scopes, and approve.
4

Use the tools

Return to Claude. The Coverbase tools are now available in your conversations.

​
Claude Desktop

Open Claude Desktop, go to Settings → Connectors, and click Add custom connector. Name it Coverbase, paste the server endpoint, and click Add. Click Connect and sign in to Coverbase when prompted.

​
Cursor

In Cursor’s settings, open MCP → Add new server, or add the server to ~/.cursor/mcp.json: 
{
  "mcpServers": {
    "coverbase": {
      "type": "streamable-http",
      "url": "https://mcp.coverbase.app/mcp"
    }
  }
}
Cursor handles the OAuth flow in your browser on first use.

​
VS Code

VS Code supports MCP servers natively in GitHub Copilot agent mode. Add the server to your settings.json: 
{
  "mcp": {
    "servers": {
      "coverbase": {
        "type": "streamable-http",
        "url": "https://mcp.coverbase.app/mcp"
      }
    }
  }
}
Reload VS Code and sign in to Coverbase when Copilot prompts you.

​
Microsoft Copilot Studio

Copilot Studio can call Coverbase as a Model Context Protocol tool.
1

Add a tool

In your agent, open Tools → Add a tool → Model Context Protocol, then add a new MCP server.
2

Configure the server

Set the transport to Streamable HTTP and enter the server endpoint https://mcp.coverbase.app/mcp.
3

Authenticate

Choose OAuth 2.0 authentication. Copilot Studio uses dynamic discovery to find the authorization server, so no manual endpoint configuration is required. Complete sign-in to Coverbase to finish.
Copilot Studio probes the RFC 8414 §3.1 path-insertion discovery variant (/.well-known/oauth-authorization-server/{path}). The Coverbase server serves authorization-server metadata at that path, so dynamic discovery works out of the box. If discovery fails with “Could not discover authorization server metadata,” confirm you entered the full /mcp endpoint.

​
Microsoft ecosystem and other agents

Coverbase works with any framework that speaks MCP over OAuth 2.0 with Streamable HTTP transport, including Semantic Kernel, the Microsoft Agent Framework (AutoGen), and Azure AI Foundry agents. Register https://mcp.coverbase.app/mcp as a remote MCP server / tool in your framework’s MCP client and let it run the OAuth flow. Other popular clients:
  • Cline (VS Code): open the Cline MCP Servers panel and add a new remote server with the Coverbase endpoint.
  • Goose: run goose configure, choose to add a remote MCP server, and enter the endpoint.
  • MCP Inspector: run npx @modelcontextprotocol/inspector, enter the endpoint, authenticate, and exercise tools directly.

​
Clients without remote MCP support (mcp-remote)

For clients that only support local stdio servers, bridge to the remote server with mcp-remote: 
{
  "mcpServers": {
    "coverbase": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.coverbase.app/mcp"]
    }
  }
}
mcp-remote proxies the connection and handles the OAuth handshake in your browser on first use.

​
Other clients

Any client that supports MCP with OAuth 2.0 and Streamable HTTP transport should work. The OAuth discovery documents are published at https://mcp.coverbase.app/.well-known/oauth-protected-resource and https://mcp.coverbase.app/.well-known/oauth-authorization-server. Point your client at the server URL and the rest is standard.

Troubleshooting

No tools appearing, permission denied errors, write actions not executing, 403 Forbidden during authentication, and other common issues.