Kimi Code 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
} |
| logging | {} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| kimiC | Directly control the installed Kimi ACP/CLI without bridge sandbox, path, permission, environment, timeout, or session-binding restrictions. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| kimi-manual | The direct-control tool actions and their intentionally unrestricted boundary. |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap. The tool's purpose is clearly defined as direct control of the installed Kimi ACP/CLI.
The single tool name is consistent with no conflicting conventions. Although it is not a verb_noun pattern, consistency is trivially satisfied.
The server provides exactly one tool, which feels minimal for general use. While it may be sufficient for a focused integration, it borders on being too thin for a typical MCP server.
The tool offers unrestricted direct control of the Kimi CLI, covering the full range of possible operations. There are no apparent gaps in functionality since it can execute any command supported by the CLI.