Busabase for AiderConnect Aider to Busabase
Terminal AI pair programmer with deep git integration — but no MCP client.
Paste this into Aider
Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.
Busabase
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.
For this agent
Aider has no MCP client, so the Skill path is the only way in — and it is a complete one. Use `/web https://busabase.com/SETUP_SKILL.md` to pull the document in, then let Aider follow it; approve the `/run` commands it asks for.
Other ways in
Busabase can't be added to this agent as an MCP connector, so there is nothing to wire in. These routes work instead.
At a glance
- Vendor
- Aider
- How it connects
- Plugin / Skill · busabase-cli · REST API
- Transport
- No MCP support
- Authentication
- None
npm exec -y --package busabase-cli@latest -- busabase-cli login --device-codeAider has no MCP client, so Busabase cannot be attached as a tool provider. Two things still work:
1. Use busabase-cli in the same terminal. Aider edits your repo while you read and propose Busabase changes alongside it:
npm exec -y --package busabase-cli@latest -- busabase-cli login --device-code
npx busabase-cli bases list
2. Use the REST API from your code. The full surface is at /api/v1, with an OpenAPI document you can hand to any client.
If you want an agent that proposes reviewed changes directly, pick one of the MCP-capable clients in this directory instead.
Known gotchas
Aider's official documentation does not document MCP client support, so there is no server to add. Third-party tutorials claiming otherwise do not match the official docs — treat them with caution.
How it compares
Connection capabilities side by side with other agents already in this directory.
| Capability | Aider |  Claude Code |  Cursor |
|---|---|---|---|
| Type | Terminal agents | Terminal agents | AI editors |
| Recommended path | Agent Skill | Agent Skill | Agent Skill |
| How it connects | Plugin / Skill · busabase-cli · REST API | MCP + OAuth · Plugin / Skill | MCP + OAuth · Plugin / Skill |
| Transport | No MCP support | Streamable HTTP | Streamable HTTP |
| Authentication | None | 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 Aider
Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.