code-agent-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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| dispatchC | Dispatch a subtask to a code agent worker (opencode|codex|claude). Returns {job_id}. |
| pollA | Poll job state. Returns {state, result, stderr, elapsed_ms, exit_code}. |
| list_jobsA | List jobs (newest first). Optional state filter (pending|running|done|error|cancelled). |
| cancelA | Cancel a job. SIGTERM then SIGKILL after 5s if still running. Returns {ok, prev_state}. |
| waitA | Block server-side until job reaches a terminal state or timeout expires. Returns the same shape as poll(). Reduces driver-side polling cost — one wait call replaces N poll calls. If timeout hits before completion, returns the current (non-terminal) state; caller may wait() again. |
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 5 tools
Each tool has a distinct purpose: dispatch creates jobs, poll and wait check status (polling vs. blocking), list_jobs lists all, cancel terminates. No overlap or ambiguity.
Most tools use single verbs (poll, dispatch, cancel, wait), but list_jobs uses verb_noun. This slight inconsistency prevents a perfect score but remains readable.
Five tools cover the essential lifecycle of job management (create, monitor, list, cancel) without being too many or too few.
Core operations are covered, but missing features like job retry or modification are minor gaps that agents can work around.