Busabase for Kimi WorkConnect Kimi Work to Busabase
Moonshot AI's general-purpose local agent for knowledge workers (Mac/Windows beta): Kimi Code as the kernel, skills, plugins, scheduled tasks and browser control.
Paste this into Kimi Work
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
Default permission mode asks before running code on local files; use Default or Manual approval when letting it run the Busabase setup commands.
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
- Unknown
- Authentication
- Unknown
Kimi Work (Kimi's local desktop agent, Work mode of the Kimi desktop app) 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.
Prefer a connector?
Kimi Work has a built-in Plugin Builder skill. Type /plugin-builder and give it the Busabase MCP URL https://busabase.com/api/mcp when it asks for an MCP server URL; the plugin lands under Plugins → Personal, where you click + to install it. Kimi's docs do not say whether a plugin-declared remote MCP server can run an OAuth sign-in against a third-party server, so confirm the sign-in prompt appears; if not, use the Skill route.
Kimi Work overview · Create a personal plugin
Known gotchas
Beta product (launched 2026-06-03). Scheduled tasks run locally and only while the app is open. 'Fully automatic' permission lets the agent execute code and change system configuration without asking. Custom-plugin MCP transport/OAuth behaviour is not documented.
How it compares
Connection capabilities side by side with other agents already in this directory.
| Capability | Kimi Work |  Claude Code |  Cursor |
|---|---|---|---|
| Type | Desktop apps | 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 | Unknown | 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 Work
Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.