Connect Claude.ai to Busabase
Web Claude (also Claude Desktop and Cowork): Customize → Connectors → Add custom connector, then paste the URL.
Busabase MCP server
https://busabase.com/api/mcp

Set it up
Hosted chat has no shell and no file system, so a connector is the way in.
Add the server
Point your chat client at the Busabase MCP endpoint.
Sign in
Complete OAuth in the browser — no client id or secret to create.
Pick the smallest permission
changeRequest lets the agent propose but never merge.
Verify
Ask the agent to call auth_verify before it does any work.
Step by step
This host has no shell, so a connector is the only way in.
At a glance
- Vendor
- Anthropic
- How it connects
- MCP + OAuth · MCP + API key
- Transport
- Streamable HTTP
- Authentication
- OAuth (dynamic registration)
- Open Customize → Connectors, click + Add, then Add custom connector. (On Team and Enterprise an Owner adds it first under Organization settings → Connectors → Add → Custom → Web; members then click Connect in Customize → Connectors.)
- Enter a name and the remote MCP server URL
https://busabase.com/api/mcp, then Continue. - Review the authentication settings Claude detected (Authentication: Sign in now; OAuth client: keep the recommended Use Claude's published identity, or Register automatically), then Continue and Add.
- Complete OAuth in the browser, then enable the connector for a conversation via + → Connectors.
- Ask Claude to call
auth_verify.
Free users are limited to one custom connector. As an alternative to OAuth, the Request headers section accepts a fixed Authorization: Bearer <key> (create the key in Busabase Settings → API Keys).
Get started with custom connectors using remote MCP
Known gotchas
Claude connects to the MCP server from Anthropic's cloud, not from your device, so it cannot reach Busabase Desktop on localhost:15419 (this is also true of Claude Desktop and Cowork); it works with Busabase Cloud only. Free plan: one custom connector. On Team/Enterprise only Owners (or Enterprise roles with Manage access to Libraries) can add a custom connector.
How it compares
Connection capabilities side by side with other agents already in this directory.
| Capability | |||
|---|---|---|---|
| Type | Web chat | Terminal agents | AI editors |
| Recommended path | MCP connector | Agent Skill | Agent Skill |
| How it connects | MCP + OAuth · MCP + API key | MCP + OAuth · Plugin / Skill | MCP + OAuth · Plugin / Skill |
| Transport | Streamable HTTP | Streamable HTTP | Streamable HTTP |
| Authentication | OAuth (dynamic registration) | OAuth (dynamic registration) | OAuth (dynamic registration) |
Written from this agent's own documentation. We have not re-run every step on a real machine, so check the linked docs if a command has changed.
Let your agent do the setup
One instruction, one authorization, and every change it makes afterwards carries a message and a diff you can check or revert.
Browse every agentBusabase MCP server
https://busabase.com/api/mcp