Busabase for ZooWork

Connect ZooWork to Busabase

An agent delivery platform: build agents in chat with Agent Builder, or run them through the Managed Agents API in an isolated cloud sandbox with shell, files, web tools, Skills and remote MCP servers.

Paste this into ZooWork

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 ZooWork Skills documentation

Busabase

Agent Skill

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

Sign-in spans two turns: the agent stops after posting the approval link, so send a follow-up message in the same Session once you've approved it. Don't deny exec or web_fetch in tool_policy, or the agent can't read the setup document or run busabase-cli.

Other ways in

Busabase can't be added to this agent as an MCP connector, so there is nothing to wire in. These routes work instead.

At a glance

Vendor: Serendipity One
How it connects: Plugin / Skill · busabase-cli · REST API
Transport: Streamable HTTP
Authentication: None

Run this

npm install @zoowork-ai/sdk      # TypeScript SDK
python -m pip install zoowork     # Python SDK

ZooWork's MCP integration cannot reach Busabase: an Agent's mcp servers must be public endpoints that accept unauthenticated requests, and the platform attaches no stored credentials, OAuth, or custom headers. Connect through the Agent's own tools instead.

Create and start an Agent by following the Quickstart. Keep exec and web_fetch available — they are on the default tool surface unless your tool_policy denies them. The default cloud sandbox ships Node.js 24 and has unrestricted outbound network access.
In a Session, send the agent this message:

Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.
The agent runs busabase-cli login --no-wait and replies with an approval link. Approve it in your browser, then send another message in the same Session so the agent can finish signing in.
Ask the agent to run busabase-cli whoami to confirm the connected Space.

For a production integration where your backend already holds a Busabase API key, ZooWork recommends an application-executed custom tool for authenticated services: your application calls the Busabase REST API and returns the result to the agent.

ZooWork — MCP servers

Known gotchas

MCP is not a route in: ZooWork only connects to public MCP endpoints that accept unauthenticated requests, with no OAuth, stored credentials, or header configuration — Busabase's MCP server requires sign-in. Managed Agents is a Developer Preview, so the API may change. busabase-cli stores its credential in the home directory, while only /workspace is documented as shared across an Agent's sessions, so a new sandbox instance may need to sign in again (not yet tested by us). Sessions on the same Agent share its workspace and therefore the Busabase sign-in; use an Agent per user for separate identities.

How it compares

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

Capability	ZooWork	Claude Code	Cursor
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 + OAuth · Plugin / Skill	MCP + OAuth · Plugin / Skill
Transport	Streamable HTTP	Streamable HTTP	Streamable HTTP
Authentication	None	OAuth (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.

Where these steps come from Official site

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 ZooWork

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