Busabase for Kimi ClawConnect Kimi Claw to Busabase
Moonshot AI's hosted OpenClaw: a dedicated cloud (or local desktop / Android) OpenClaw wired to Kimi models, chat channels and a ClawHub skill library.
Paste this into Kimi Claw
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
The web Terminal runs commands directly, independent of chat context. Skills installed in the Claw are managed with /skills (install/uninstall/reload); installed skills follow the ClawHub library.
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
- Moonshot AI (月之暗面)
- How it connects
- Plugin / Skill · busabase-cli · REST API
- Transport
- No MCP support
- Authentication
- Unknown
Kimi Claw (an OpenClaw instance Kimi runs for you, with a web Terminal) can fetch a URL and run shell commands, so the Skill path applies. Paste this into a chat with it: Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Review the commands it proposes (npx busabase-cli login --no-wait, npx skills add busabase/skills --skill busabase busabase-app-creator), approve the sign-in link in your browser, then ask it to verify the active Busabase account.
Other ways in
Kimi's help center says plugins (the Kimi connector mechanism) are not supported in Kimi Claw, and it documents no custom-MCP setting for Claw, so there is no connector route to publish. Use the Skill prompt above, or have the Claw run busabase-cli / call the REST API from its Terminal.
Kimi Claw help · Skills in Kimi Claw
Known gotchas
One-click Claw deployment requires an Allegretto or higher Kimi plan. Plugins are not supported in Kimi Claw. Skill entry points are unavailable in third-party OpenClaw, local Claw and desktop Claw. Restarting the OpenClaw gateway disconnects the web Terminal.
How it compares
Connection capabilities side by side with other agents already in this directory.
| Capability | Kimi Claw |  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 | No MCP support | 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 Kimi Claw
Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.