codex-mcp-server
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| codex_taskC | Run an autonomous coding task in a new Codex thread and return the final response. |
| codex_runC | Alias for codex_task. Runs a task in a new Codex thread. |
| codex_start_threadC | Start a new conversation thread session with the Codex agent. |
| codex_run_turnC | Run a follow-up turn or send a new prompt in an existing Codex thread. |
| codex_continueC | Alias for codex_run_turn. Continue an existing conversation thread. |
| codex_continue_threadC | Alias for codex_run_turn. Continue a thread with a follow-up message. |
| codex_list_threadsB | List historical and active Codex threads querying local session caches. |
| codex_get_threadA | Get metadata and full conversation history for a specific Codex thread. |
| codex_fork_threadB | Fork an existing thread into a new thread by cloning its session history. |
| codex_archive_threadB | Archive an active conversation thread. |
| codex_unarchive_threadB | Unarchive a previously archived conversation thread. |
| codex_interrupt_turnB | Interrupt and abort the running turn or command on an active thread. |
| codex_interruptC | Alias for codex_interrupt_turn. Interrupt a running turn on an active thread. |
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 13 tools
Several tools have overlapping purposes, such as codex_continue, codex_continue_thread, and codex_run_turn all appearing to continue a thread. Aliases like codex_continue and codex_interrupt add confusion, making it hard for an agent to select the correct tool.
The snake_case and 'codex_' prefix are consistent, but the presence of aliases (e.g., codex_continue vs. codex_continue_thread) and inconsistent verb usage (run, continue, fork, archive) reduces clarity.
13 tools is a reasonable number for managing Codex threads, covering creation, continuation, interruption, archiving, and listing. It is well-scoped without being excessive.
The tool set covers essential thread operations: start, continue, fork, archive, unarchive, list, and get. Missing update/delete capabilities are minor given the conversational domain, and most workflows are supported.