Busabase for Zoo Code

Connect Zoo Code to Busabase

Autonomous VS Code agent extension that can edit code, run terminal commands, and connect to local or remote MCP servers.

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

For this agent

Switch Zoo Code to an agent mode that can use the terminal, then let it follow SETUP_SKILL.md and review its command approvals.

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.

Zoo Code MCP documentation

At a glance

Vendor
Zoo Code Organization
How it connects
MCP + API key · Plugin / Skill · busabase-cli · REST API
Transport
Streamable HTTP
Authentication
API key
Config file
mcp_settings.json or .roo/mcp.json

Install Zoo Code from the VS Code Marketplace, open a trusted project, switch to a mode with terminal access, and ask: Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Review its commands and complete authentication. For API-key MCP fallback, configure a streamable-http server in the global MCP settings or .roo/mcp.json.

Known gotchas

Remote servers must set type to `streamable-http`; Zoo cannot infer transport from a URL. The project configuration path is still `.roo/mcp.json`. The reviewed docs show header-based authentication, not OAuth.

How it compares

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

CapabilityZoo CodeClaude CodeCursor
TypeIDE pluginsTerminal agentsAI editors
Recommended pathAgent SkillAgent SkillAgent Skill
How it connectsMCP + API key · Plugin / Skill · busabase-cli · REST APIMCP + 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 Zoo 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.