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. Use for general programming questions, algorithm explanations, or getting a second opinion from Kimi's model.

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 installation status, version, and authentication. Use this to diagnose issues before running analysis.