zcode-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZCODE_BIN | No | Path to the zcode CLI entry (absolute path, .cjs). Default: /Applications/ZCode.app/Contents/Resources/glm/zcode.cjs | /Applications/ZCode.app/Contents/Resources/glm/zcode.cjs |
| ZCODE_MODEL | No | Default model. Default: GLM-5.3 | GLM-5.3 |
| ZCODE_PROVIDER | No | Preferred account provider. Default: account:bigmodel-individual-coding-plan | account:bigmodel-individual-coding-plan |
| ZCODE_MCP_DEBUG | No | Set to '1' to output debug logs to stderr. | |
| ZCODE_REASONING | No | Default reasoning level. Default: max | max |
| ZCODE_DEFAULT_CWD | No | Fallback directory when zcode_run does not pass cwd. Default: server process cwd | |
| ZCODE_MCP_AUTO_PROXY | No | Automatically detect macOS system proxy and forward it to the zcode subprocess (set to '0' to disable). Default: 1 | 1 |
| ZCODE_CREDENTIAL_SECRET | No | Encryption key for zcode credentials (consistent with zcode client, generally no need to set). Default: derived from machine fingerprint. |
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 |
|---|---|
| zcode_runA | Delegate a development task to the zcode coding agent. zcode works inside the given directory: it can read/edit files, run shell commands and git. Returns zcode's final answer plus a session_id that can be used to send follow-ups in the same conversation. |
| zcode_checkA | Report whether the zcode agent backend is reachable: binary path, stored credentials, available models after booting the app-server. Run this first when zcode_run fails. |
| zcode_sessionsA | List recent zcode sessions (id, title, directory) for a workspace, usable as session_id in zcode_run. |
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 3 tools
Each tool has a clearly distinct purpose: zcode_run executes a task, zcode_check verifies backend health, and zcode_sessions lists past sessions. There is no overlap or ambiguity between them.
All tools share the consistent 'zcode_' prefix and snake_case convention. However, 'zcode_sessions' is a noun rather than a verb-based name, deviating slightly from the verb-oriented pattern of 'zcode_run' and 'zcode_check'.
Three tools form a well-scoped set for a coding-agent management server. Each tool serves a distinct and necessary function without bloat or redundancy.
The core workflow (check backend, run tasks, list sessions) is covered, and session_id reuse enables follow-ups. A minor gap exists in having no dedicated tool to inspect a single session's full details, but this is workable via the existing surface.