Busabase for PicoClaw

Connect PicoClaw to Busabase

Sipeed's tiny open-source personal AI assistant in Go (runs on Raspberry Pi, RISC-V boards, Android) with channels, an exec tool, SKILL.md skills and MCP.

Paste this into PicoClaw

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 PicoClaw 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

Skills are loaded from `SKILL.md` files in the workspace (`~/.picoclaw/workspace/skills/`, listed as 'Custom skills'); `picoclaw skills search|install` pulls from ClawHub/GitHub registries and `picoclaw skills list` shows them. Whether it follows the agentskills.io spec is not stated. The exec tool's deny patterns apply (`enable_deny_patterns`), and it only checks the top-level command.

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: Sipeed
How it connects: Plugin / Skill · busabase-cli · REST API · MCP + API key
Transport: Streamable HTTP
Authentication: API key
Config file: ~/.picoclaw/config.json (or $PICOCLAW_CONFIG) -> tools.mcp.servers

Run this

Download the launcher/binary from https://picoclaw.io (or GitHub Releases); source: git clone https://github.com/sipeed/picoclaw.git && cd picoclaw && make deps && make install

PicoClaw has an exec tool and a web fetcher, so the Skill path applies: paste the prompt above into the WebUI launcher or a connected channel. The default exec guard blocks curl | sh, npm install -g and similar patterns; npx is not on the documented block list but needs Node installed.

Prefer a connector?

PicoClaw's MCP client reaches remote HTTP servers with static headers (no OAuth is documented). Create a Busabase API key (Settings -> API Keys, smallest permission, finite expiry), then:

picoclaw mcp add busabase --transport http https://busabase.com/api/mcp --header "Authorization: Bearer <key>"
picoclaw mcp test busabase

Restart the gateway, then ask the agent to call auth_verify. The equivalent JSON in ~/.picoclaw/config.json:

{
  "tools": {
    "mcp": {
      "enabled": true,
      "servers": {
        "busabase": {
          "enabled": true,
          "type": "http",
          "url": "https://busabase.com/api/mcp",
          "headers": { "Authorization": "Bearer <key>" }
        }
      }
    }
  }
}

PicoClaw MCP server CLI

Known gotchas

Early, fast-moving project; the README warns 'Do not deploy to production before v1.0'. `--header` values and `--env` values are written to config.json in plain text. When `type` is omitted and only `url` is set, PicoClaw auto-detects `sse`, so set `type: http` (or `--transport http`) explicitly for Busabase's Streamable HTTP endpoint. The official site is picoclaw.io only; the README warns many .ai/.org/.com look-alike domains are third parties.

How it compares

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

Capability	PicoClaw	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 + 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)

These stepsFrom official docsLast checked Oct 21, 2026

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 PicoClaw

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