Send a prompt to Kimi Code for codebase analysis. Kimi reads the codebase (256K context) and returns a compressed, structured report.

CACHE BEHAVIOR: If session_id is not provided, the MCP server will automatically use cached sessions when available.

• First call: Creates cache (may take 60-120s for large codebases)

• Subsequent calls: Reuses cached session (faster, ~10s)

• Cache auto-expires after 30 minutes or when files change

• Use kimi_cache_status to view cache statistics

Output is budget-controlled: Kimi reads 200K+ tokens of source but returns a 5-15K token analysis (configurable via detail_level). Use kimi_resume to drill deeper into specific areas. Takes 1-5 minutes for large codebases.

Ask Kimi Code a question without codebase context. Default model: k3 (K3). Use for general programming questions, algorithm explanations, or getting a second opinion.

Get an INDEPENDENT second opinion from Kimi Code (default k3 / K3, 256K context) acting as an external third-party verifier. Calls the Kimi Code API directly — no CLI install required, just an API key (env KIMICODE_API_KEY or ~/.kimi/config.toml).

USE THIS to cross-check your own work: confirm a fix is correct, hunt for bugs / edge cases / security issues in a diff, sanity-check a claim or plan, or get a dissenting view before you commit. Different model, independent judgment.

CRITICAL — pass full context: Kimi sees ONLY the 'context' string. It has NO access to this session, the repository, prior messages, or any tools. Paste the ACTUAL code/diff/claim AND the surrounding context it needs (the goal, constraints, assumptions, relevant signatures). Vague or partial context produces vague, useless verification.

Detection: every response ends with a [kimi-model …] footer (requested/observed/k3=yes|no).

List existing Kimi Code sessions with titles, working directories, and timestamps. Use to find session IDs for kimi_resume.

View session cache statistics and status. Shows cache hits/misses, active sessions, and performance metrics. Use this to monitor cache effectiveness and troubleshoot issues.

Manually invalidate session cache entries. Use when you want to force fresh analysis or if you suspect cached sessions are stale.

Resume an existing Kimi Code session with a new prompt. The session retains all previous context (up to 256K tokens). Use kimi_list_sessions to find session IDs first. Ideal for drilling deeper after an initial kimi_analyze scan.

Check Kimi CLI/API status, default model (K3 detection), and auth. Set probe_api=true for a live Coding API model echo check.