Busabase for Roo Code

Connect Roo Code to Busabase

Autonomous coding agent for VS Code with per-project and global MCP settings.

Paste this into Roo 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.

Read the Roo Code Skills documentation
Busabase
Agent Skill
A Base of posts in a Busabase workspace, with records, views, and agent prompts

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.

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.

Roo Code MCP documentation

At a glance

Vendor
Roo Code
How it connects
MCP + API key · Plugin / Skill
Transport
Streamable HTTP
Authentication
API key
Config file
~/.roo/mcp.json (project) / mcp_settings.json (global)

Open the Roo Code pane's settings icon, scroll to the MCP section, and click Edit Global MCP or Edit Project MCP:

{
  "mcpServers": {
    "busabase": {
      "type": "streamable-http",
      "url": "https://busabase.com/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_BUSABASE_API_KEY>"
      },
      "disabled": false
    }
  }
}

Then ask the agent to call auth_verify. Create the API key at a changeRequest permission level so Roo can propose but not merge.

Known gotchas

Roo Code does not start the OAuth flow even when the server answers 401 with a `WWW-Authenticate` header — Busabase does exactly that, so the connection simply fails rather than prompting you to sign in. Use a Busabase API key in `headers` instead. Upstream: RooCodeInc/Roo-Code issue #7296 (bug) and #8119 (OAuth 2.1 discovery + PKCE enhancement); Roo currently relies on the `mcp-remote` bridge for OAuth. Also note project-level `.roo/mcp.json` overrides the global settings, so check both if a stale server keeps loading.

How it compares

Connection capabilities side by side with other agents already in this directory.

CapabilityRoo CodeClaude CodeCursor
TypeIDE pluginsTerminal agentsAI editors
Recommended pathAgent SkillAgent SkillAgent Skill
How it connectsMCP + API key · Plugin / SkillMCP + OAuth · Plugin / SkillMCP + OAuth · Plugin / Skill
TransportStreamable HTTPStreamable HTTPStreamable HTTP
AuthenticationAPI keyOAuth (dynamic registration)OAuth (dynamic registration)
These stepsFrom official docsNo check date recorded

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 agent

Paste this into Roo 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.