Connect MiniMax Code to Busabase
MiniMax's desktop AI agent app (the former MiniMax Agent desktop, renamed) plus the `mcode` terminal CLI: local workspace, terminal, browser, skills, MCP, scheduled tasks, Telegram/WeChat/Lark/Feishu channels.
Paste this into MiniMax 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
Skills are SKILL.md folders (also auto-imported from Claude Code / Codex). Batch import from a GitHub repo is supported.
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
- MiniMax
- How it connects
- MCP + API key · Plugin / Skill · busabase-cli · REST API
- Transport
- Streamable HTTP
- Authentication
- API key
- Config file
- ~/.minimax/mcp.json (or plugin manifest *.mcp.json)
curl -fsSL https://filecdn.minimax.chat/public/install.sh | bash # CLI; or npm install -g @minimax-ai/codeMiniMax Code (desktop app / mcode 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?
Open the plugin management entry → MCP Servers → add, in JSON mode:
{
"mcpServers": {
"busabase": {
"type": "streamable-http",
"url": "https://busabase.com/api/mcp",
"headers": { "Authorization": "Bearer ${BUSABASE_API_KEY}" },
"enabled": true
}
}
}
Create the key in Busabase Settings → API Keys (smallest permission, finite expiry). The docs describe only static headers; OAuth account-connect flows are routed to MiniMax's App/Connector integration, so no OAuth route is published. Run mcode mcp list --human to check, then ask it to call auth_verify.
Known gotchas
Remote MCP auth is documented only as static headers/tokens. Packaged plugin MCP supports stdio, streamable-http and sse; the `http` alias works only in local config. Do not commit real tokens. Some plans/regions differ: mainland-China and Global accounts log in separately (`mcode login --region global`).
How it compares
Connection capabilities side by side with other agents already in this directory.
| Capability | |||
|---|---|---|---|
| Type | Desktop apps | Terminal agents | AI editors |
| Recommended path | Agent Skill | Agent Skill | Agent Skill |
| How it connects | 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 | API key | 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 MiniMax 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.