Connect nanobot to Busabase
HKUDS's ultra-lightweight, open-source, self-hosted personal AI agent (Python, PyPI `nanobot-ai`) with a WebUI, terminal UI, chat-app channels, skills and MCP.
Paste this into nanobot
Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.

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 directories with a `SKILL.md` (YAML frontmatter `name`, `description`, `metadata` + Markdown), format adapted from OpenClaw; custom skills live in the agent workspace `~/.nanobot/workspace/skills/`. Skills can be installed from skills.sh and SkillHub in the WebUI (Skills -> Discover; skills.sh needs `npx`) or via the bundled `clawhub` skill. Whether it follows the agentskills.io open spec is not stated; it follows the OpenClaw conventions. In Restricted access mode, shell/file work stays inside the selected project.
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
- HKUDS (HKU Data Intelligence Lab)
- How it connects
- MCP + OAuth · MCP + API key · Plugin / Skill · busabase-cli · REST API
- Transport
- Streamable HTTP
- Authentication
- OAuth (dynamic registration)
- Config file
- ~/.nanobot/config.json -> tools.mcpServers.<name>; OAuth tokens in <data dir>/auth/mcp.json
curl -fsSL https://raw.githubusercontent.com/HKUDS/nanobot/main/scripts/install.sh | sh (or: uv tool install nanobot-ai)nanobot can use shell and web fetch, so the Skill path applies: paste the prompt above into the WebUI, TUI or a connected chat app.
Prefer a connector?
nanobot supports remote MCP with browser OAuth and dynamic client registration.
- Open the WebUI (
nanobot webui) -> Apps -> MCP -> Add MCP server -> Custom. - Choose HTTP, enter
https://busabase.com/api/mcp, and set Authentication to OAuth. Save. - Choose Connect and approve in the browser window that opens.
- Ask the agent to call
auth_verify.
Manual equivalent in ~/.nanobot/config.json, then click Connect under Apps -> MCP:
{
"tools": {
"mcpServers": {
"busabase": {
"type": "streamableHttp",
"url": "https://busabase.com/api/mcp",
"auth": "oauth"
}
}
}
}
API-key alternative: replace "auth": "oauth" with "headers": { "Authorization": "Bearer ${BUSABASE_KEY}" } (key from Busabase Settings -> API Keys).
Known gotchas
HTTP/SSE MCP URLs go through an SSRF guard (private, loopback, CGNAT ranges blocked by default). For a remotely reached WebUI served over plain HTTP, nanobot registers a localhost callback and asks you to paste the full callback URL after authorisation; HTTPS plus `channels.websocket.publicWsUrl` is recommended. OAuth tokens are stored outside config.json in `auth/mcp.json`. The docs do not say which OAuth scopes nanobot requests; Busabase grants `mcp` for generic scopes.
How it compares
Connection capabilities side by side with other agents already in this directory.
| Capability | |||
|---|---|---|---|
| Type | Agent platforms | Terminal agents | AI editors |
| Recommended path | Agent Skill | Agent Skill | Agent Skill |
| How it connects | MCP + OAuth · MCP + API key · Plugin / Skill · busabase-cli · REST API | MCP + OAuth · Plugin / Skill | MCP + OAuth · Plugin / Skill |
| Transport | Streamable HTTP | Streamable HTTP | Streamable HTTP |
| Authentication | OAuth (dynamic registration) | 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 nanobot
Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.