codex-mcp-swarm
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CODEX_SWARM_LOG | No | Log file path | /tmp/codex_mcp_swarm.log |
| CODEX_SWARM_TASK_DIR | No | Task output storage directory | /tmp/codex_swarm_tasks |
| CODEX_SWARM_LOG_LEVEL | No | Log level (DEBUG, INFO, WARNING, ERROR) | WARNING |
| CODEX_SWARM_TASK_MAX_AGE | No | Seconds before completed task artifacts (and worktrees) are cleaned up | 86400 |
| CODEX_SWARM_WORKTREE_DIR | No | Worktree storage directory | /tmp/codex-swarm-worktrees |
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| codexB | Run a Codex session synchronously. Parameters match the official Codex MCP tool. |
| codex_asyncA | Start a Codex task in the background and return immediately with a task_id. Use codex_wait to collect results from one or more tasks, or codex_status to monitor progress. Set worktree=true to isolate each task in its own git worktree so parallel tasks don't conflict -- merge the branch back when done. |
| codex_replyA | Continue a Codex conversation by providing the thread/session ID and a follow-up prompt. Uses |
| codex_statusA | Get live status of running async Codex tasks. Shows what each task is currently doing: last tool call, reasoning, progress. Works on both running and completed tasks. |
| codex_waitA | Block until one or more async Codex tasks complete, then return all results. Accepts a list of task_ids. This avoids repeated polling -- call once after launching codex_async tasks. Default timeout is 1800s (30 min). If a task times out, it is NOT killed -- it keeps running. You can call codex_wait again with the same task_ids to resume waiting, or use codex_status to check progress. |
| codex_cancelA | Kill a running async Codex task. The process is terminated and the task is marked as cancelled. Any worktree and partial output are preserved for inspection. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Server Info | Server version, configuration, and capabilities. |
| Server Config | Current server-level defaults and flags. |
| Active Tasks | List of all known async tasks and their current state. |
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: sync execution, async launch, cancel, reply, status polling, and waiting. No two tools overlap in functionality.
Most tools follow the 'codex_' prefix with a clear verb, but the sync tool is simply 'codex' without an underscore, creating a minor inconsistency.
6 tools is appropriate for managing Codex sessions, covering sync and async operations, cancellation, continuation, status, and blocking wait.
Core lifecycle is well-covered (start, wait, cancel, continue, monitor). Minor gap: no tool to list all active tasks, though status can query known task IDs.