Busabase for Zo ComputerConnect Zo Computer to Busabase
Zo is an always-on personal cloud computer (a Linux server with a shell, files, browser and 50+ tools) that an AI agent operates for you, reachable from chat, SMS, email, Telegram, Slack and Discord.
Paste this into Zo Computer
Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.
Busabase
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
Zo implements the open Agent Skills format and loads skills from the `Skills` folder in the workspace. After `npx skills add busabase/skills --skill busabase busabase-app-creator`, confirm the skill folders ended up under `/home/workspace/Skills/` (the default install directory of the skills CLI was not verified against Zo); if not, move or copy them there.
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
- Zo Computer Company
- How it connects
- Plugin / Skill · busabase-cli · REST API
- Transport
- Unknown
- Authentication
- Unknown
- Config file
- /home/workspace/Skills/<skill-name>/SKILL.md (workspace Skills folder)
Zo's agent has a shell (Run command tool) and can read web pages, so the Skill path applies. Paste the prompt above into a Zo chat: Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Approve the Busabase device-login link when Zo posts it.
Prefer a connector?
Zo's documentation describes adding vendor-listed apps (Pipedream catalog, a few mcp:<slug> presets) but gives no screen for pasting an arbitrary remote MCP URL, so there is no documented connector setup for Busabase. Use the Skill path above, or have Zo call busabase-cli / the Busabase REST API from its shell.
See the vendor docs: https://www.zo.computer/guide/skills and https://www.zo.computer/reference/tools/bash
Known gotchas
Zo's own MCP server (https://api.zo.computer/mcp, bearer key) is the reverse direction: it lets other agents use Zo, not Zo use Busabase. Pricing and plan limits come from Zo's subscription/credits; check https://www.zo.computer/guide/billing.
How it compares
Connection capabilities side by side with other agents already in this directory.
| Capability | Zo Computer |  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 | Unknown | Streamable HTTP | Streamable HTTP |
| Authentication | Unknown | 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 Zo Computer
Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.