Codex Kimi Bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KIMI_MODEL | No | The Kimi model to use. | |
| KIMI_THINKING | No | Thinking mode for Kimi. | |
| KIMI_CODE_HOME | No | Path to the Kimi Code home directory. | |
| KIMI_AUTO_START | No | Whether to auto-start the Kimi server when needed. | true |
| KIMI_SERVER_URL | No | The base URL of the Kimi server. | http://127.0.0.1:58627 |
| KIMI_SERVER_TOKEN | No | The Bearer token for authenticating with the Kimi server. | |
| KIMI_PERMISSION_MODE | No | Permission mode for Kimi. | |
| KIMI_PREFLIGHT_CACHE_MS | No | Cache lifetime for preflight checks in milliseconds. | 5000 |
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
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 11 tools
Without descriptions, many tools are ambiguous. Similar names like 'kimi_delegate_and_wait' and 'kimi_delegate_task' or 'kimi_recent_sessions' and 'kimi_find_recent_session' suggest overlapping purposes, making it hard to distinguish between them.
All tools follow the 'kimi_' prefix and use snake_case. Most follow a verb_noun pattern (e.g., 'kimi_abort', 'kimi_continue_task'), though a few are noun-based like 'kimi_bridge_status' or 'kimi_recent_sessions', which is a minor deviation.
With 11 tools, the count is well-scoped for a bridge service. It covers a variety of operations without being excessive or insufficient, striking a good balance.
The tool names suggest task management and session handling, but there are noticeable gaps like missing 'create_task' or 'cancel_task'. Core operations like delegation and review are present, but the surface feels incomplete for a full workflow.