codex-cli-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CODEX_CLI_PATH | No | Path to the Codex CLI binary | codex |
| OPENAI_API_KEY | No | API key for authentication (alternative to ChatGPT login) | |
| CODEX_MCP_DEBUG | No | Set to enable debug logging to stderr | |
| CODEX_TIMEOUT_MS | No | Idle timeout for Codex process | 600000 |
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 |
|---|---|
| codexA | Run a Codex CLI session. Executes Use this tool to start a new coding task with Codex. The response includes a Thread ID that can be used with the codex-reply tool to continue the conversation. |
| codex-replyA | Continue a Codex CLI conversation by providing the thread ID from a previous codex call and a follow-up prompt. Uses |
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 2 tools
The two tools have clearly distinct purposes: codex starts a new conversation, while codex-reply continues an existing one using a thread ID. There is no ambiguity between them, as each accepts different inputs and performs a different action.
Both tool names share the 'codex' prefix, but 'codex' is a standalone verb while 'codex-reply' is a compound with a hyphen. This is a minor inconsistency, but the pattern is predictable and readable, clearly indicating the primary action and the continuation action.
With only 2 tools, the set is on the low end of the range, but it is appropriate for the narrow scope of running Codex CLI sessions. The tools cover the essential start and continue operations, though the set feels thin compared to more comprehensive servers.
The core lifecycle of starting and continuing a conversation is covered, which covers the main use case. However, there are no tools for listing active threads, ending sessions, or retrieving session history, which are minor gaps given the focus on interactive coding tasks.