Connect Claude Code to Busabase
Anthropic's terminal coding agent, with user / project / local MCP scopes.
Paste this into Claude Code
Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.

Give your agent this one instruction
You end up with more than a connector: the busabase skill carries the whole change-request workflow, the CLI, and the full API — available in every future session without re-pasting anything.
Asks first
Busabase Cloud or Personal Desktop — your call, before anything happens.
Connects
Signs you in and stores the credential itself. No API key to copy by hand.
Seeds a Base
Creates and fills your first Base, so the workspace is not an empty screen.
Installs the skills
busabase and busabase-app-creator become permanent, for every session after this.
npx skills add busabase/skillsPrefer a connector?
If you would rather wire Busabase in as MCP tools than let the agent install a skill, use the server URL below.
At a glance
- Vendor
- Anthropic
- How it connects
- MCP + OAuth · Plugin / Skill
- Transport
- Streamable HTTP
- Authentication
- OAuth (dynamic registration)
- Config file
- ~/.claude.json (user scope); project scope: .mcp.json
claude mcp add --transport http --scope user busabase https://busabase.com/api/mcp
claude mcp login busabaseAdd a user-scoped HTTP server so it is available in every project:
claude mcp add --transport http --scope user busabase https://busabase.com/api/mcp
claude mcp login busabase
claude mcp get busabase
You can also open /mcp inside Claude Code, select Busabase, and complete authentication there. Verify by asking Claude to call auth_verify.
If authentication is stale, clear the stored credentials and sign in again:
claude mcp logout busabase
claude mcp login busabase
Remove the configuration entirely with claude mcp remove --scope user busabase (removing a remote server also deletes its stored OAuth tokens and client registration).
Known gotchas
If authentication goes stale, clear it from /mcp, or run `claude mcp remove --scope user busabase` and repeat OAuth. Separately, the current docs warn that a JSON entry with a `url` but no `type` is read as a stdio server and skipped with an error — when copying a config from another client, add `"type": "http"`. And if you set an `Authorization` header for the server, Claude Code uses it as the credential and does not fall back to OAuth for that server.
How it compares
Connection capabilities side by side with other agents already in this directory.
| Capability | |||
|---|---|---|---|
| Type | Terminal agents | AI editors | Web chat |
| Recommended path | Agent Skill | Agent Skill | MCP connector |
| How it connects | MCP + OAuth · Plugin / Skill | MCP + OAuth · Plugin / Skill | MCP + OAuth |
| 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 agentPaste this into Claude Code
Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.