kimi-acp-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| kimi_prompt | 委派任务给本机 Kimi Code（通过 kimi acp）。Kimi 在 cwd 内自主干活（读写文件、跑命令、多步推理），结果回流。返回 text + session_id（可复用）+ stopReason。 |
| kimi_statusA | 检查 Kimi ACP 子进程与握手状态、活跃 session 数。不消耗 Kimi 配额。返回 {rows: [{label, ok, detail}]} 结构，便于 host 程序化解析。 |
| kimi_sessionsA | 列出桥本地维护的 session（按 newSession/loadSession 顺序），非 ACP session/list。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools serve entirely different purposes: one lists sessions, the other checks status. There is no overlap in functionality.
Both tools share the 'kimi_' prefix and follow a noun pattern ('sessions', 'status'), which is consistent. However, the lack of a verb-noun pattern is a minor deviation.
With only 2 tools, the server feels too thin for its apparent domain of session management, which typically requires more operations.
The server provides listing and status checking but lacks essential operations like creating, loading, or deleting sessions, leaving significant gaps.