Connect Cline to Busabase
Open-source autonomous coding extension for VS Code and JetBrains, with its own Remote Servers tab for MCP.
Paste this into Cline
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/skillsFor this agent
Cline asks for approval per command by default. Approve the setup steps, or enable auto-approve for the session.
Prefer a connector?
If you would rather wire Busabase in as MCP tools than let the agent install a skill, use the server URL below.
Cline MCP documentationAt a glance
- Vendor
- Cline
- How it connects
- MCP + API key · Plugin / Skill
- Transport
- Streamable HTTP
- Authentication
- API key
- Config file
- ~/.cline/data/settings/cline_mcp_settings.json (CLI, override with CLINE_MCP_SETTINGS_PATH); IDE extension: MCP settings JSON via the Configure tab
Add Busabase to the CLI settings file ~/.cline/data/settings/cline_mcp_settings.json (path overridable with CLINE_MCP_SETTINGS_PATH), or use the stacked-server icon → Remote Servers → Add Server in the IDE extension. The CLI also has an interactive wizard (cline mcp add opens it with the fields filled in) to list, add, edit or remove servers:
{
"mcpServers": {
"busabase": {
"type": "streamableHttp",
"url": "https://busabase.com/api/mcp",
"headers": {
"Authorization": "Bearer <YOUR_BUSABASE_API_KEY>"
},
"disabled": false,
"autoApprove": []
}
}
}
In the IDE, pick Streamable HTTP as the transport type. Then ask the agent to call auth_verify.
Create the API key at a changeRequest permission level so Cline can propose changes but never merge them itself.
Known gotchas
Cline's docs describe header-based auth rather than OAuth, so use a Busabase API key in the `headers` block. Set `"type": "streamableHttp"` explicitly instead of relying on the default. Correction (2026-11-09, current vendor docs): the CLI's MCP settings file is `~/.cline/data/settings/cline_mcp_settings.json`, not the `~/.cline/mcp.json` path this record previously carried. The current docs also show the CLI wizard can run or rerun browser OAuth authorization for a remote server, but they do not state the registration mode, so the documented Busabase path remains the API-key header above and auth-mode stays api-key.
How it compares
Connection capabilities side by side with other agents already in this directory.
| Capability | |||
|---|---|---|---|
| Type | IDE plugins | Terminal agents | AI editors |
| Recommended path | Agent Skill | Agent Skill | Agent Skill |
| How it connects | MCP + API key · Plugin / Skill | MCP + OAuth · Plugin / Skill | MCP + OAuth · Plugin / Skill |
| Transport | Streamable HTTP | Streamable HTTP | Streamable HTTP |
| Authentication | API key | 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 Cline
Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.