Connect ZeroClaw to Busabase
ZeroClaw Labs' open-source personal AI agent: a single Rust binary that answers on 30+ channels, runs shell/browser/HTTP tools under a supervised-by-default policy, and acts as an MCP client.
Paste this into ZeroClaw
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.
For this agent
ZeroClaw loads SKILL.md (or SKILL.toml) from `<install>/agents/<alias>/workspace/skills/<name>/` or shared bundles `<install>/shared/skills/<bundle>/<name>/` (agent must list the bundle in `skill_bundles`); the global `<install>/data/skills/` is not auto-loaded. SKILL.md frontmatter supports `name`, `description`, `author`, `version`, `tags`, `always`, `slash_options`. A generic `npx skills add` will not necessarily write into those directories, so copy the installed `busabase` skill folders into a bundle and list it in `skill_bundles` (not verified against Busabase's installer). Shell commands are subject to allow/deny lists and approval.
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
- ZeroClaw Labs
- How it connects
- Plugin / Skill · busabase-cli · REST API · MCP + API key
- Transport
- Streamable HTTP
- Authentication
- API key
- Config file
- ~/.zeroclaw/config.toml (`[[mcp.servers]]`, `[mcp_bundles.*]`, `agents.<alias>.mcp_bundles`)
curl -fsSL https://raw.githubusercontent.com/zeroclaw-labs/zeroclaw/master/install.sh | sh && zeroclaw quickstartZeroClaw has shell and web_fetch tools, so the Skill path applies: paste the prompt above into any channel or zeroclaw agent -a <alias>. Approve the commands when it asks (default autonomy is supervised).
Prefer a connector?
ZeroClaw's MCP client reaches remote servers over http (Streamable HTTP) with static headers; the docs describe no OAuth sign-in. Use a Busabase API key (Settings -> API Keys, smallest permission, finite expiry). Add to ~/.zeroclaw/config.toml, merging with your existing entries:
[[mcp.servers]]
name = "busabase"
transport = "http"
url = "https://busabase.com/api/mcp"
[mcp_bundles.busabase]
servers = ["busabase"]
[agents.assistant] # your agent alias
mcp_bundles = ["busabase"]
Then set the header as a secret (it is encrypted at rest) in the dashboard (Config -> MCP servers -> busabase -> headers.Authorization = Bearer <key>) or zerocode /config. Restart the session, then ask the agent to call busabase__auth_verify.
Known gotchas
An agent connects to no MCP server unless it lists a bundle in `mcp_bundles` (omission is not a grant); changes take effect on session restart. MCP tool calls go through the approval gate unless `auto_approve` lists the prefixed name (e.g. `busabase__...`). `http_request` is limited to allowlisted domains. HTTP/SSE MCP URLs must be https when a custom CA is set.
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 | 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 ZeroClaw
Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.