把 PicoClaw 連接到 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.
把這段貼進 PicoClaw
請閱讀 https://busabase.com/SETUP_SKILL.md,並幫我設定好 Busabase。請照著文件一路做到完成,最後確認連線是否正常運作。

把這一句指令交給你的 Agent
你得到的不只是一個連接器:busabase 技能還帶著完整的變更請求工作流程、CLI 與完整 API —— 之後每一次工作階段都在,不必再重新貼一次。
會先問你
Busabase Cloud 還是個人桌面版 —— 在動手之前,由你決定。
完成連線
幫你登入並自行儲存憑證,不需要手動複製 API 金鑰。
建立一個資料表
建立並填入你的第一個資料表,讓工作區一開始就不是空白畫面。
安裝技能
busabase 與 busabase-app-creator 會永久安裝,之後每一次工作階段都能直接使用。
此 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.
比較想用連接器?
如果你不想讓 Agent 自行安裝技能,而是想把 Busabase 當作 MCP 工具接進來,可以使用下面這個伺服器網址。
一覽表
- 廠商
- Sipeed
- 連接方式
- 外掛/技能 · busabase-cli · REST API · MCP + API 金鑰
- 傳輸方式
- Streamable HTTP
- 驗證方式
- API 金鑰
- 設定檔
- ~/.picoclaw/config.json (or $PICOCLAW_CONFIG) -> tools.mcp.servers
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 installPicoClaw 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>" }
}
}
}
}
}
已知的注意事項
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.
能力比較
與目錄中其他已收錄的 Agent,並列比較連線能力。
| 能力 | |||
|---|---|---|---|
| 類型 | Agent 平台 | 終端機 Agent | AI 編輯器 |
| 推薦路徑 | Agent Skill | Agent Skill | Agent Skill |
| 連接方式 | 外掛/技能 · busabase-cli · REST API · MCP + API 金鑰 | MCP + OAuth · 外掛/技能 | MCP + OAuth · 外掛/技能 |
| 傳輸方式 | Streamable HTTP | Streamable HTTP | Streamable HTTP |
| 驗證方式 | API 金鑰 | OAuth(動態註冊) | OAuth(動態註冊) |
把這段貼進 PicoClaw
請閱讀 https://busabase.com/SETUP_SKILL.md,並幫我設定好 Busabase。請照著文件一路做到完成,最後確認連線是否正常運作。