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.

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
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 · MCP + OAuth
- Transport
- Streamable HTTP
- Authentication
- API key
- Config file
- Settings > Agent behavior > 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. Two sign-in routes are documented: an API-key header (below), or OAuth — set "oauth": true on the remote entry instead of the header, then use Connect in the same panel; AgentsRoom opens the sign-in page in your browser and renews the tokens on its own. You can also use Add from catalog (the official MCP registry) or From my projects (imports servers from CLI config files) in the same panel.
Create a key in Busabase Settings → API Keys with the smallest permission that works and a finite expiration.
- Store your Busabase API key in AgentsRoom's Secret Manager as
BUSABASE_API_KEY. - Open Settings > Agent behavior > MCP servers and choose Paste JSON.
- Paste:
{
"busabase": {
"type": "http",
"url": "https://busabase.com/api/mcp",
"headers": { "Authorization": "Bearer {{secret:BUSABASE_API_KEY}}" }
}
}
- Save, launch a new agent and ask it to call
auth_verify.
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. OAuth servers are delivered to every CLI through the open-source mcp-remote bridge, so OAuth needs Node.js/npx on the computer and the sign-in is per-computer (sign in again on another machine). Switching a server off writes `"disabled": true`. Codex and Mistral Vibe have no SSE transport — an `sse` server is ignored for them; use `http`.
How it compares
Connection capabilities side by side with other agents already in this directory.
| Capability | |||
|---|---|---|---|
| Type | Desktop apps | Terminal agents | AI editors |
| Recommended path | Agent Skill | Agent Skill | Agent Skill |
| How it connects | Plugin / Skill · busabase-cli · REST API · MCP + API key · MCP + OAuth | 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 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.