MiMo Code

Xiaomi's official coding agent — mimocode.jsonc, local and cloud both real.

local stdio
cloud API key
verified

MiMo Code is Xiaomi's own official coding-agent tool (mimo.xiaomi.com) — not the unofficial third-party "MiMo-CLI" community wrapper. Real, documented MCP support for both local and remote servers, configured in mimocode.jsonc. Verified end-to-end against a real MiMo Code installation, both local and cloud.

Local (stdio)

Add under mcp in mimocode.jsonc. command is the full argv, so this runs via uvx — no install step:

{
  "mcp": {
    "spomory": {
      "type": "local",
      "command": ["uvx", "--from", "spomory[llm,embedding,mcp]", "spomory-mcp"],
      "environment": {
        "LLM_API_KEY": "...",
        "LLM_BASE_URL": "https://api.deepseek.com",
        "LLM_MODEL": "deepseek-v4-flash"
      },
      "enabled": true
    }
  }
}

Prefer a fixed, pinned install over uvx's on-demand cache? Install into a virtual environment outside ~/Documents (pip install 'spomory[llm,embedding,mcp]'), then set command to a single-element array with that venv's bin/memory-core-mcp.

Where do these environment variables come from?

LLM_API_KEY is your key for whichever OpenAI-compatible provider you use for extraction — OpenAI, DeepSeek, Qwen, and others all work. LLM_BASE_URL and LLM_MODEL default to OpenAI if you leave them out; swap them to point at DeepSeek, Qwen, or any other OpenAI-compatible provider, or a fully local server (Ollama, vLLM, llama.cpp, MLX):

export LLM_API_KEY=...
export LLM_BASE_URL=https://api.deepseek.com   # optional, defaults to OpenAI
export LLM_MODEL=deepseek-v4-flash             # optional, defaults to gpt-4o-mini
export EMBEDDING_MODEL=BAAI/bge-m3             # optional, defaults to bge-m3

Full local setup guide, including the macOS ~/Documents gotcha →

MiMo Code's MCP docs →

Cloud (API key)

Same file, type "remote" with a headers block:

{
  "mcp": {
    "spomory-cloud": {
      "type": "remote",
      "url": "https://api.yliuai.com/mcp-apikey/",
      "headers": {
        "x-api-key": "<your key>"
      },
      "enabled": true
    }
  }
}

Verified against a real MiMo Code installation, resolving to the same account/memory graph as every other client on this page.

Where does <your key> come from?

Get one instantly with curl — fine for your own testing:

curl -X POST https://api.yliuai.com/users/register \
  -H "Content-Type: application/json" \
  -d '{"email": "you@example.com"}'
# the api_key in the response (starts with mck_) is shown only this once -- save it

That hands you a key with no proof you control the email — fine for testing, but for real use, get one through the email-confirmation form instead, which actually verifies the address.

Get a verified key on the Cloud & Apps page →

MiMo Code's MCP docs →

Make it actually get used

Connecting the tools doesn't mean your client reaches for them on its own — it needs to be told to call search_memory before answering and add_memory after you share something worth keeping. SKILL.md is a short instructions file that does that. How you load it is specific to each client: some auto-discover a skills folder the same way Claude Code does, others only have a custom-instructions or system-prompt field instead. Verified for this one:

MiMo Code auto-discovers skills from .mimocode/skills/**/SKILL.md (project) or ~/.config/mimocode/skills/**/SKILL.md (global) — it also reads an existing .claude/skills/ folder directly, by design.

SKILL.md on GitHub →