codex-mcp-longrun
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LONGRUN_STATE_DIR | No | Directory for job logs and metadata. Defaults to ~/.local/state/codex-longrun. | ~/.local/state/codex-longrun |
| LONGRUN_ALLOWED_ROOTS | Yes | Trusted project directory or colon-separated list of directories. The server validates the resolved working directory against these allowed roots. | |
| LONGRUN_HEARTBEAT_INITIAL_SEC | No | Delay before the first heartbeat notification. 0 disables heartbeats. | 300 |
| LONGRUN_HEARTBEAT_INTERVAL_SEC | No | Interval between later heartbeat notifications. | 900 |
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 |
|---|---|
| healthA | Return server paths, versions, and configured guardrails. |
| run_and_waitA | Run one approved non-interactive process and return one bounded terminal result. |
| read_log_tailA | Read only the bounded tail stored for a known job ID. |
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 distinct role: health checks server status, run_and_wait executes a process and returns a result, and read_log_tail retrieves logs for a specific job. There is no overlap or ambiguity between them.
Tool names are inconsistent in style: 'health' is a simple noun, 'run_and_wait' is a verb phrase, and 'read_log_tail' is a verb-noun-noun compound. No uniform pattern (e.g., verb_noun) is followed.
Three tools is a minimal set, but it covers the core needs of a long-run execution server: health check, run a command, and read logs. It feels slightly thin but is not unreasonably sparse for a focused utility.
The surface covers the basic workflow of running a process and checking its logs, but lacks obvious lifecycle management tools like cancel, list jobs, or check status. The domain is narrow, yet significant gaps remain for robust long-running job handling.