Connect Kimi Code to Busabase
Moonshot AI's terminal coding agent (TypeScript CLI, successor to kimi-cli) with MCP, Agent Skills, plugins and hooks.
Paste this into Kimi Code
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
The CLI asks before running shell commands, so approve the `npx busabase-cli` commands when prompted. Skills are SKILL.md folders.
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
- Moonshot AI (月之暗面)
- How it connects
- MCP + OAuth · MCP + API key · Plugin / Skill · busabase-cli · REST API
- Transport
- Streamable HTTP
- Authentication
- Unknown
- Config file
- ~/.kimi-code/mcp.json (user) or .kimi-code/mcp.json (project)
curl -fsSL https://code.kimi.com/kimi-code/install.sh | bashKimi Code CLI 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?
Add Busabase to ~/.kimi-code/mcp.json (or run /mcp-config in the TUI):
{
"mcpServers": {
"busabase": { "url": "https://busabase.com/api/mcp" }
}
}
Then run /mcp-config login busabase to complete browser-based OAuth. API-key alternative: add "headers": { "Authorization": "Bearer <key>" } or bearerTokenEnvVar. Start a new session (servers added mid-session only join later sessions), then ask it to call auth_verify.
Known gotchas
Servers added mid-session are not registered in already-open sessions. Docs say entries with a url and no transport are HTTP servers; OAuth uses `/mcp-config login <server>`. Whether dynamic client registration is used is not stated. In 'Ask When Needed' mode MCP tool calls are auto-approved. New in the current docs: project-level servers in an untrusted folder trigger a workspace trust prompt, and headless runs (`kimi -p`) cannot show that prompt, so project-level MCP servers stay disabled there unless the workspace is already trusted (or `KIMI_CODE_TRUST_WORKSPACE=1` is set). Servers dropped mid-session reconnect with exponential backoff.
How it compares
Connection capabilities side by side with other agents already in this directory.
| Capability | |||
|---|---|---|---|
| Type | Terminal agents | 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 | 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 Code
Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.