Busabase for NanoClaw

Connect NanoClaw to Busabase

NanoCo's open-source personal assistant that runs each agent in its own Linux container (Claude Agent SDK by default) and talks to you over WhatsApp, Telegram, Slack, Discord, iMessage and more.

Paste this into NanoClaw

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

Agents run in ephemeral per-group containers; the docs do not say whether skills installed by `npx skills add` or the `busabase-cli` login state persist across container spawns. Outbound HTTPS goes through the credential gateway, so busabase.com must be reachable from it. NanoClaw's own skills are SKILL.md folders (container skills at `container/skills/`, per-template `skills/<name>/SKILL.md` with `name` + `description` frontmatter, Agent Plugins 1.0.0 format); the `.claude/skills/` host skills are for the coding harness customising NanoClaw, not for the agent.

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: NanoCo
How it connects: Plugin / Skill · busabase-cli · REST API · MCP + API key
Transport: Streamable HTTP
Authentication: API key
Config file: Per agent group, in NanoClaw's central DB (container config `mcp_servers`); set with `ncl groups config add-mcp-server`. Template form: `mcp.json` -> `mcpServers`.

Run this

git clone https://github.com/nanocoai/nanoclaw.git nanoclaw-v2 && cd nanoclaw-v2 && bash nanoclaw.sh

NanoClaw agents run Claude Code (or another provider) inside a container with a shell and web access, so the Skill path applies: paste the prompt above into any channel your agent is paired with.

Prefer a connector?

NanoClaw can register a remote Streamable HTTP MCP server per agent group. It has no documented OAuth sign-in for MCP; credentials are injected by the host's credential gateway (OneCLI Agent Vault), never stored in the MCP entry.

In Busabase, open Settings -> API Keys and create a key with the smallest permission and a finite expiry.
On the NanoClaw host, store it in the vault for the Busabase host, then grant it to the agent group:

onecli secrets create --name Busabase --type api_key --value "$BUSABASE_KEY" --host-pattern busabase.com

ncl groups config add-mcp-server --id <group-id> --name busabase --url https://busabase.com/api/mcp
ncl groups restart --id <group-id>

Ask the agent to call auth_verify.

NanoClaw: give agents tools

Known gotchas

Remote MCP URLs must be HTTPS and must not embed credentials; the legacy `sse` transport is not supported; custom headers are for non-secret values only. Secrets live in the OneCLI vault and are matched by host, so the key must be registered for busabase.com and granted to the agent group. Host-side `ncl` and container-side tools differ: `ncl` write commands run from inside a container are approval-gated.

How it compares

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

Capability	NanoClaw	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 NanoClaw

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