mcp-server-codex
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CODEX_BIN | No | Chemin ou nom du binaire Codex. Défaut : codex | codex |
| CODEX_HOME | No | Racine Codex : sessions et images générées y sont lues. Défaut : ~/.codex | ~/.codex |
| CODEX_MCP_MAX_EVENTS | No | Taille du tampon d'événements par job. Défaut : 2000. | 2000 |
| CODEX_MCP_ALLOWED_ROOTS | No | Répertoires autorisés, séparés par ';' (Windows) ou ':'. Liste exhaustive, remplace le défaut (cwd du serveur). | |
| CODEX_MCP_ALLOW_DANGEROUS | No | À '1', débloque danger-full-access et le contournement des approbations. Défaut : '0'. | 0 |
| CODEX_MCP_DEFAULT_SANDBOX | No | Sandbox par défaut : read-only, workspace-write ou danger-full-access. Défaut : workspace-write. | workspace-write |
| CODEX_MCP_JOB_TTL_SECONDS | No | Durée de consultation d'un job terminé. Défaut : 1800. | 1800 |
| CODEX_MCP_DEFAULT_TIMEOUT_SECONDS | No | Attente avant bascule en arrière-plan. 0 = toujours en arrière-plan. Défaut : 120. | 120 |
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 |
|---|---|
| codex_execA | Start a new Codex agent session against a prompt. Codex can read and edit files and run commands in the sandbox. Returns the final message, the commands it ran and a thread_id you can pass to codex_resume. Long runs move to the background and return a job_id. |
| codex_resumeA | Continue a previous Codex session with its full history, either by session_id or with last=true for the most recent one. Use this instead of codex_exec to follow up on earlier work without re-explaining the context. |
| codex_forkA | Branch an existing Codex session into a new one, leaving the original untouched. Useful for trying a different approach from a shared starting point. |
| codex_reviewA | Run a Codex code review over uncommitted changes (default), a diff against a base branch, or a specific commit. Optionally steer it with custom instructions. |
| codex_applyA | Apply the latest diff produced by a Codex task to the local working tree, as a git apply. Modifies files on disk. |
| codex_list_sessionsA | List recorded Codex sessions with their id, name, working directory and last update, read straight from disk. Use it to find a session_id for codex_resume or codex_fork. |
| codex_generate_imageA | Generate an image using the image_gen tool built into Codex, and save it to output_path. No API key is needed: it runs through your Codex session. Returns the path of the file written, not the image bytes. |
| codex_job_statusA | Report the state of a run that moved to the background: whether it is still running, its exit code, how long it has taken and how many events it has produced. |
| codex_job_logsA | Page through the JSONL events of a background run. Pass the returned next_cursor back as "since" to read only what is new. Filter with "types" to cut the noise. |
| codex_job_cancelA | Stop a run that is still going: SIGTERM first, then SIGKILL after a grace period. Reports honestly whether this call is what cancelled it. |
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 10 tools
Each tool targets a distinct action: starting, resuming, forking, reviewing, applying, listing, image generation, and job management are clearly separated. The session-lifecycle tools (exec/resume/fork) and job tools (status/logs/cancel) have well-defined boundaries with explicit descriptions.
All tools share the codex_ prefix and use lowercase snake_case, making the set predictable. The naming shifts slightly between verb-first (codex_exec, codex_list_sessions) and noun-first (codex_job_status, codex_job_logs), but the pattern remains readable and consistent in style.
Ten tools is well-scoped for a Codex agent server covering session lifecycle, background jobs, code review/apply, and image generation. Each tool has a clear purpose and none feel redundant.
The core workflows are covered: start/resume/fork sessions, review and apply changes, manage background jobs, and list sessions. A few minor gaps exist, such as no explicit job listing or session deletion, but agents can work around these without major failures.