Connect Agent Zero to Busabase
Open-source autonomous agent framework that runs in Docker and can use host terminal, files, and browser tools through A0 CLI.
Paste this into Agent Zero
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
If Agent Zero runs in Docker, install A0 CLI so it can reach the host terminal and filesystem, then let it follow SETUP_SKILL.md.
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.
Agent Zero MCP documentationAt a glance
- Vendor
- Agent Zero
- How it connects
- Plugin / Skill · busabase-cli · REST API · MCP + API key
- Transport
- Unknown
- Authentication
- API key
- Config file
- Settings > MCP/A2A tab > External MCP Servers
curl -fsSL https://bash.agent-zero.ai | bashInstall Agent Zero using its official installer and enable the host tools you intend to grant. In a trusted workspace, ask: Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Review the proposed shell commands and authorization flow, then ask Agent Zero to verify the active Busabase account and list the installed Busabase skills.
Prefer a connector?
Agent Zero's MCP & A2A docs now document a remote MCP shape with header auth. Open Settings → MCP/A2A → External MCP Servers, paste the JSON below, and choose Apply now:
{
"mcpServers": {
"busabase": {
"url": "https://busabase.com/api/mcp",
"headers": { "Authorization": "Bearer <your Busabase API key>" }
}
}
}
Create the key in Busabase Settings → API Keys first. No OAuth flow is documented for remote servers, so the header route is the documented one.
Known gotchas
The MCP & A2A docs document a remote shape (url + Authorization Bearer header) but never name the transport (streamable-http / SSE) for the url form, and document no OAuth flow — so the header/API-key route above is the documented one and mcp-transport stays unknown. If Agent Zero runs in Docker and the server sits on the host, use host.docker.internal (macOS/Windows) or the container name on the same Docker network (Linux). The active Agent Profile's MCP policy decides which MCP tools the agent may use; tools are namespaced <server>_<tool>. Local stdio servers use command/args in the same mcpServers block.
How it compares
Connection capabilities side by side with other agents already in this directory.
| Capability | |||
|---|---|---|---|
| Type | Agent platforms | 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 · Plugin / Skill | MCP + OAuth · Plugin / Skill |
| Transport | Unknown | 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 Agent Zero
Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.