Busabase for MiMo Code

Connect MiMo Code to Busabase

Xiaomi MiMo's terminal-native coding agent with persistent memory, skills, autonomous workflows, shell tools, and MCP connections.

Paste this into MiMo 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.

Read the MiMo Code documentation
Busabase
Agent Skill
The Busabase review inbox, showing proposed changes waiting for approval

Give your agent this one instruction

You end up with more than a connector: the busabase skill carries the whole approval-first 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

MiMo Code discovers skills and has shell access. Run setup in a trusted repository and review any external-directory permission request.

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
Xiaomi MiMo
How it connects
MCP + OAuth · MCP + API key · Plugin / Skill · busabase-cli · REST API
Transport
Streamable HTTP
Authentication
OAuth (dynamic registration)
Config file
~/.config/mimocode/mimocode.jsonc or .mimocode/mimocode.jsonc
Run this
curl -fsSL https://mimo.xiaomi.com/install | bash

Install MiMo Code, run mimo in a trusted repository, and ask: Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Review the commands and permissions, complete authentication, then ask MiMo Code to verify the active Busabase account. Its remote MCP client can also use OAuth dynamic registration.

Known gotchas

Remote MCP OAuth auto-detection attempts RFC 7591 dynamic client registration when no client ID is supplied. The default callback is http://127.0.0.1:19876/mcp/oauth/callback; keep auth.json and config files private.

These stepsFrom official docsNo check date recorded

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, reviewed access, and every change it makes afterwards arrives as a proposal you approve.

Browse every agent

Paste this into MiMo 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.