Updated 2026-10-02

MiMo Code

MiMo Code (by Xiaomi) reads MCP server configuration from .mimocode/mimocode.jsonc (project) or ~/.config/mimocode/mimocode.jsonc (global). The root key is mcp, not mcpServers.

Manual configuration

No matching CLI installer is recorded for this client's configuration contract. Use the manual snippet below and merge only LyraShield's entry, preserving existing servers, comments where supported, and the file's current path and symlinks. Restart or reload the client and complete a read-only authenticated call; an entry alone does not prove client discovery.

Prefer to see exactly what gets written or set it up without Node.js? Configure it by hand below.

Local stdio setup

Add the following to .mimocode/mimocode.jsonc or ~/.config/mimocode/mimocode.jsonc. MiMo Code uses type: "local" with command as an array (e.g. ["npx","-y","@lyrashield/mcp@0.2.12"]) and an environment object, plus an enabled boolean.

Manual fallback: merge the following into .mimocode/mimocode.jsonc. Recommended: run npx -y lyrashield@0.2.14 login --oauth once; the local MCP server reads the selected workspace credential from ~/.lyrashield/credentials.json. If you use an API key instead, set it in your private process environment before starting the client.

{
  "mcp": {
    "lyrashield": {
      "command": [
        "npx",
        "-y",
        "@lyrashield/mcp@0.2.12"
      ],
      "environment": {
        "LYRASHIELD_API_URL": "https://app.lyrashieldai.com"
      },
      "enabled": true,
      "type": "local"
    }
  }
}

Important gotchas

• Root key is `mcp`, not `mcpServers` — using `mcpServers` silently fails.
• Local uses `type: "local"` with `command` as an ARRAY (["npx","-y","<cmd>"]) and `environment` (not `command`+`args`+`env`), plus an `enabled` boolean.
• Remote uses `type: "remote"` with `url` + `headers` and `enabled`; OAuth is handled automatically.

Remote HTTP setup

For environments where you prefer not to run a local process, connect to the remote endpoint. MiMo Code uses type: "remote" with url + headers and enabled. OAuth is handled automatically.

Manual fallback: merge the following into .mimocode/mimocode.jsonc. Enter the workspace API key only in the client's private, untracked server settings or its documented secret-backed header interpolation. The snippet contains a placeholder; never put a real key in a shared project file or shell command.

{
  "mcp": {
    "lyrashield": {
      "url": "https://app.lyrashieldai.com/api/mcp",
      "headers": {
        "Authorization": "Bearer <LYRASHIELD_API_KEY>"
      },
      "type": "remote"
    }
  }
}

Verify the connection

Restart MiMo Code and ask: "What LyraShield tools do you have access to?" to confirm the server is connected.