the integrations

Kimi Code CLI (Moonshot)

null

{"id":"kimi-code","name":"Kimi Code CLI (Moonshot)","class":"B","status":"proven","install":"add nika to ~/.kimi-code/mcp.json (mcpServers map · their two-level contract) · the legacy kimi-cli `kimi mcp add` subcommand does NOT exist in kimi-code","wire":"kimi","components":{"mcp":"mcp-config","skills":"init"},"gaps":[],"class_gap":"no AGENTS.md auto-load (their docs are silent · upstream asks open) · skills scan 4 tiers including project and user .agents/skills — the init-written authoring skill is discovered · MCP carries the oracle"}

Proven live: someone ran a real task through this client against the binary, and the pair is recorded. Class B: no plugin loader, so MCP and the scaffold carry the teaching.

proventhe stateat v0.107.0
Bthe classhow much lands
2pieces landnamed below
0gapsnothing missing

get set up

add nika to ~/.kimi-code/mcp.json (mcpServers map · their two-level contract) · the legacy kimi-cli `kimi mcp add` subcommand does NOT exist in kimi-code

The binary writes that itself: nika wire kimi puts the oracle where this client looks for it, and nika doctor says so when the two fall out of step.

what lands, and how

mcpmcp-config
skillsinit

what does not

no AGENTS.md auto-load (their docs are silent · upstream asks open) · skills scan 4 tiers including project and user .agents/skills — the init-written authoring skill is discovered · MCP carries the oracle

cross-references

the rooms it touches

where this comes from

v0.107.0
kimi-code