Kimi MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Kimi MCP Server review the changes in my current branch"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Kimi MCP Server
MCP server (stdio) that bridges Claude / Cursor / any MCP client to Moonshot AI's Kimi Code CLI.
Architecture mirrors @trishchuk/codex-mcp-tool — same patterns, adapted to Kimi's flag surface (--print, --quiet, -r, --continue, --add-dir, --mcp-config-file, --config).
Why
Kimi K2.6 (April 2026) is a 1T-parameter MoE open-weight model with native agent-swarm orchestration, 262k context, and SWE-Bench Pro on par with GPT-5.5. Kimi Code CLI is the reference agent harness. This server lets MCP-aware editors call Kimi as a sub-agent without leaving their primary interface.
Related MCP server: mcacp
Install
npm install -g @trishchuk/kimi-mcp-serverYou also need Kimi Code CLI:
curl -LsSf https://code.kimi.com/install.sh | bash
# OR
uv tool install --python 3.13 kimi-cliThen run kimi once and use /login to authenticate via the Kimi Code platform — or set MOONSHOT_API_KEY.
Configure (Claude Desktop / Cursor / Claude Code)
Minimal — working directory is auto-detected from PWD / INIT_CWD / process.cwd(), just like codex-mcp-tool:
{
"mcpServers": {
"kimi": {
"command": "kimi-mcp"
}
}
}Pin a specific project root only if your client launches the server from somewhere unrelated:
{
"mcpServers": {
"kimi": {
"command": "kimi-mcp",
"env": { "KIMI_MCP_CWD": "/absolute/path/to/your/project" }
}
}
}You can also override per call via the workingDir argument on ask-kimi, or let the server infer it from @path/to/file references in the prompt — same priority chain as codex-mcp-tool: workingDir arg → KIMI_MCP_CWD → PWD → INIT_CWD → @path inference → process.cwd().
Tools
Tool | What it does |
| Main entry — file analysis ( |
| Structured ideation (divergent / convergent / SCAMPER / design-thinking / lateral / auto) |
| Sequential or parallel atomic tasks with priority, stop-on-error, structured report |
| Code review of working tree / branch diff / specific commit (collects |
| List, delete, or clear active conversation sessions |
| Diagnose Kimi CLI installation, auth, and session state |
| Smoke tests + help passthrough |
ask-kimi highlights
prompt— supports@path/to/fileto drop file context (Kimi reads via working dir).model— overridesdefault_modelat runtime via--config. Known:kimi-for-coding,kimi-k2-6,kimi-k2-thinking-turbo,kimi-k2-5,kimi-latest.thinking— toggles thinking mode (writesdefault_thinkinginto runtime config).outputFormat—text(default) orstream-json(JSONL of assistant + tool messages, parsed transparently).responseMode—clean(default; final assistant text only) orfull(tool calls + stderr log + final).sessionId— workspace-isolated session ID (md5 of repo:head:path). The server tracks the native Kimi session ID returned by the CLI and replays it viakimi -r <id>.continueLatest— sets--continue(resume the most recent session in the cwd).mcpConfigFile— passes--mcp-config-fileso Kimi can talk to other MCP servers from inside this process.addDirs— repeats--add-dirfor multi-root projects.yolo/afk— approval shortcuts (print mode auto-approves anyway, but useful for documentation/logging).
CLI compatibility
Feature | Kimi CLI |
Print / non-interactive |
|
JSON streaming |
|
Sessions |
|
Configuration |
|
Workspace | spawn cwd + |
MCP passthrough |
|
Exit codes |
|
Environment
Var | Default | Purpose |
| — | Override working directory for every tool call |
| 86400000 (24h) | Session expiration |
| 50 | Max concurrent sessions |
| — | Forwarded to Kimi CLI for unattended auth |
Development
npm install
npm run build # tsc → dist/
npm run lint # tsc --noEmit
node dist/index.js # smoke run on stdioLicense
MIT — Taras Trishchuk
Available Tools
14 toolsask-kimiBDestructive
Execute Kimi Code CLI with file analysis (@syntax), session resume, MCP passthrough, and safety controls.
Inputs: prompt (required), cd, afk, plan, +23 more.
batch-kimiADestructive
Delegate multiple atomic tasks to Kimi for batch processing. Ideal for repetitive operations, mass refactoring, and automated transformations.
Inputs: tasks (required), yolo, model, timeout, +4 more. Returns: total, failed, results, skipped, +1 more
bg-kimiADestructive
Run Kimi CLI as a detached background task. Subactions: start (returns taskId), status, tail (log output), stop, remove, list. Use for long-running autonomous work — the MCP call returns immediately and you poll status later.
Inputs: action (required), cd, plan, yolo, +15 more.
brainstormA
Generate creative ideas using structured frameworks with domain context and feasibility analysis.
Inputs: prompt (required), cd, afk, yolo, +8 more.
delegate-kimiADestructive
Delegate an implementation task to Kimi in an isolated git worktree. Kimi runs autonomously (--yolo) on a fresh branch, optionally looping against a test command. Returns a taskId; later 'collect' to grab the diff. Safe: changes are sandboxed, caller reviews & applies.
Inputs: task, model, action, taskId, +7 more.
digest-kimiARead-only
Ingest many files at once and answer a focused question. Uses Kimi's 262K context to swallow whole modules / docs that don't fit in the caller's context. Walks directories, filters by extension, truncates oversized files, caps total payload. Returns a concentrated brief.
Inputs: paths (required), question (required), model, shape, +7 more.
healthARead-onlyIdempotent
Check Kimi CLI installation, authentication, and session health
Inputs: verbose, sessionId. Returns: issues, status, kimiCli, sessions
HelpARead-onlyIdempotent
Show Kimi CLI help output
Inputs: no named parameters.
list-sessionsBDestructive
List active conversation sessions with metadata, or manage them (delete/clear)
Inputs: action, sessionId. Returns: stats, action, sessions
metricsARead-onlyIdempotent
Expose Prometheus-formatted metrics for Kimi MCP server
Inputs: no named parameters.
pingCRead-onlyIdempotent
Echo
Inputs: prompt.
plan-kimiARead-only
Generate a structured implementation plan using Kimi's --plan mode. Use BEFORE coding to get steps, files-to-touch, risks, and open questions. Distinct from ask-kimi: uses --plan flag (different system prompt) and parses structured output.
Inputs: goal (required), model, format, timeout, +4 more.
review-changesARead-onlyIdempotent
Run a code review against the current repository using Kimi (collects git diff + structured review prompt).
Inputs: base, model, title, commit, +5 more.
versionARead-onlyIdempotent
Display version and system information
Inputs: no named parameters. Returns: nodeJs, kimiCli, platform, mcpServer
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 14 tools
Each tool has a clearly distinct purpose: from single queries (ask-kimi) to batch processing, code review, brainstorming, background tasks, planning, file ingestion, sandboxed delegation, session management, and server info. No two tools overlap in functionality.
Most tools use lowercase with hyphens (e.g., ask-kimi, batch-kimi), but there are inconsistencies: some are single words (ping, health, version), 'Help' is capitalized, and patterns vary between verb-noun and noun-verb. The naming is readable but not fully consistent.
With 14 tools, the server provides a comprehensive interface to the Kimi CLI, covering core interactions (query, batch, planning, code review, brainstorming), background tasks, file digestion, sandboxed delegation, and management. The count feels well-scoped for its purpose.
The tool surface covers the major workflows expected from a CLI-based coding assistant: interactive queries, batch processing, code review, planning, brainstorming, file ingestion, and sandboxed execution. Minor gaps might include a direct file-editing tool, but the existing tools enable comprehensive automation.
Maintenance
Related MCP Connectors
Shared memory MCP server for Claude Code, Codex, Gemini CLI and Cursor. Cited, editable.
Talk to your public-facing AI from any MCP client — Claude, ChatGPT, Cursor, Cline, Windsurf.
Share one project context across ChatGPT, Claude, Telegram and any MCP client.
Connect ChatGPT and Claude to your Mac, Windows or Linux with secure MCP remote access.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceMCP server that provides file operations and Moonshot API-powered tools (reasoning, code review, testing, research, web search, agent) for Kimi K2.5, requiring only a Moonshot API key.199 npm1MIT
- AlicenseAqualityDmaintenanceBridges any MCP client (like Claude Code, Zed, VS Code) to any ACP coding agent, enabling multi-agent orchestration from a single chat interface.24627 npm12Apache 2.0
- AlicenseBqualityDmaintenanceWindows-first MCP bridge for Kimi Code CLI, exposing code analysis, editing, sessions, and diagnostics as tools for AI agents.6MIT
- AlicenseBqualityCmaintenanceBridges Codex Desktop with Kimi Code CLI, enabling direct control of AI coding sessions via MCP tools for prompt, status, cancel, and CLI operations.1MIT