Kimi Code CLI

Validated with Kimi Code CLI 2.1.1 on 2026-11-04 — a newer surface that may shift.

Configure

Create or edit ~/.kimi-code/mcp.json:

{
  "mcpServers": {
    "bloomy-earth": {
      "url": "https://mcp.bloomy.earth/mcp"
    }
  }
}

A project-level .kimi-code/mcp.json would override this home-level file, gated by workspace trust.

Load and log in

Kimi loads servers at session start, so open a new session (/new) after editing. Then run:

/mcp-config login bloomy-earth

Registration went through Dynamic Client Registration (observed) and the request carried the resource parameter plus all three scopes. Sign in with your own Dashboard → Integration API credentials. /mcp then shows connected.

Confirmation

Confirmation is conversational two-step: the assistant presents the server's not-executed summary and asks "Confirmez-vous ?"; no native popup or form appeared (observed).

Kimi additionally asks permission per tool call — a host-level confirm independent of, and never replacing, the server's two-call floor.

What this host shows

The live probe from this host returned the expected pinned value. Kimi shows tool names in the conversation but no per-parameter schema view; the confirmationCode parameter still round-trips — the server's redeem path answered a deliberately wrong-code probe.