Busabase for AgentsRoom

Connect AgentsRoom to Busabase

AgentsRoom is a desktop app (macOS, Windows, Linux) with a mobile companion that runs many coding-agent CLIs, including Claude Code, Codex, Copilot CLI, OpenCode and Cursor, across your projects from one window.

Paste this into AgentsRoom

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 AgentsRoom 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.

For this agent

AgentsRoom also has its own Skills Library. A skill can come from a Git source (repository `https://github.com/busabase/skills`, subfolder `skills/busabase`), but AgentsRoom injects skill bodies into the agent's prompt at launch instead of installing them the CLI's usual way. The prompt above is the simpler route. Agents launched from the phone don't currently get project or folder skill baselines.

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.

At a glance

Vendor
AgentsRoom
How it connects
Plugin / Skill · busabase-cli · REST API · MCP + API key
Transport
Streamable HTTP
Authentication
API key
Config file
Settings > AI providers & accounts > MCP servers (also Project settings > AI providers > MCP servers, or per agent: Advanced options > MCP servers)

AgentsRoom runs each agent through its own CLI in a terminal (Claude Code, Codex, GitHub Copilot CLI, OpenCode, Cursor and more), so the Skill path applies: open an agent and paste the prompt above ("Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me"). For per-agent details see Claude Code, Codex or OpenCode.

Prefer a connector?

AgentsRoom can declare an MCP server once and pass it to every agent it launches. Its docs cover URL + header servers, not an OAuth sign-in, so use a Busabase API key:

Create a key in Busabase Settings → API Keys with the smallest permission that works and a finite expiration.

  1. Store your Busabase API key in AgentsRoom's Secret Manager as BUSABASE_API_KEY.
  2. Open Settings > AI providers & accounts > MCP servers and choose Paste JSON.
  3. Paste:
{
  "busabase": {
    "type": "http",
    "url": "https://busabase.com/api/mcp",
    "headers": { "Authorization": "Bearer {{secret:BUSABASE_API_KEY}}" }
  }
}
  1. Save, launch a new agent and ask it to call auth_verify.

AgentsRoom docs: MCP Servers

Known gotchas

Aider has no MCP client, so Aider agents won't get the server. For Codex, OpenCode and most other CLIs, AgentsRoom writes the server, with the key filled in, into the project's CLI config file. That file is git-ignored, but don't commit it by hand. Team steps have no MCP servers field. Servers added before version 1.176.0 only reached Claude Code (and Codex with the personal-config switch), so update the app.

How it compares

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

CapabilityAgentsRoomClaude CodeCursor
TypeDesktop appsTerminal agentsAI editors
Recommended pathAgent SkillAgent SkillAgent Skill
How it connectsPlugin / Skill · busabase-cli · REST API · MCP + API keyMCP + 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 AgentsRoom

Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.