ladder-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KIMICODE_API_KEY | No | API key used by the kimi_ask tool. Alternatively set api_key in ~/.kimi-code/config.toml. | |
| LADDER_EXPERIMENTAL | No | Set to '1' to enable experimental tools. | 0 |
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_codeA | Agentic work in a repository: analyze and edit files. Defaults to in-process CLI transport. |
| kimi_askC | Stateless question or independent review. Text only, no repo, no edits. |
| kimi_sessionsB | List/inspect Kimi sessions from the CLI catalog, ACP, or both. |
| kimi_tasksC | Manage background work: status, output, or cancel. |
| kimi_statusC | Installation, auth, and diagnostics. |
| kimi_setupC | Generate the Kimi-hosted MCP config entry for Ladder_mcp. |
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 6 tools
Each tool has a clearly distinct purpose: ask handles questions, code does repository edits, sessions lists/inspects, setup generates config, status provides diagnostics, tasks manages background work – no overlap.
All tools follow a consistent 'kimi_<noun/verb>' pattern with lowercase and underscores. The naming is uniform and predictable.
Six tools is well-scoped for a management MCP server covering core functionality without being excessive or sparse.
The set covers primary use cases (ask, code, sessions, setup, status, tasks). Minor gaps like a dedicated help or search tool exist but do not hinder core workflows.