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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ask-codexC | Execute Codex CLI with file analysis (@syntax), model selection, and safety controls. Supports changeMode. |
| batch-codexB | Delegate multiple atomic tasks to Codex for batch processing. Ideal for repetitive operations, mass refactoring, and automated code transformations |
| pingC | Echo |
| HelpC | receive help information |
| versionA | Display version and system information |
| brainstormC | Generate creative ideas using structured frameworks with domain context and feasibility analysis. |
| fetch-chunkA | Retrieves cached chunks from a changeMode response. Use this to get subsequent chunks after receiving a partial changeMode response. |
| timeout-testA | Test timeout prevention by running for a specified duration |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| ask-codex | Execute Codex CLI with optional changeMode |
| batch-codex | Execute multiple atomic Codex tasks in batch mode for efficient automation |
| ping | Echo test message with structured response. |
| Help | receive help information |
| version | Get version information for Codex CLI and MCP server |
| brainstorm | Create structured brainstorming with chosen methodology and analysis |
| fetch-chunk | Fetch the next chunk of a response |
| timeout-test | Test the timeout prevention system by running a long operation |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Most tools have distinct purposes, but there is some overlap and ambiguity. For example, 'ask-codex' and 'batch-codex' both involve executing Codex CLI operations, which could cause confusion about when to use each. However, descriptions help clarify that 'batch-codex' is for multiple tasks, while 'ask-codex' is more general. Tools like 'brainstorm' and 'fetch-chunk' are clearly distinct, but the set includes basic utilities like 'ping' and 'Help' that don't align well with the code-focused domain.
Naming conventions are inconsistent and chaotic with no discernible pattern. There is a mix of styles: 'ask-codex' and 'batch-codex' use hyphenated names, 'brainstorm' and 'fetch-chunk' are single words or hyphenated, 'Help' starts with a capital letter, and 'ping', 'timeout-test', and 'version' use different formats. This lack of consistency makes the tool set harder to navigate and predict.
With 8 tools, the count is borderline but reasonable for the apparent scope of a Codex MCP server. However, the inclusion of basic utilities like 'ping', 'Help', and 'timeout-test' alongside core code tools feels slightly over-scoped, as these utilities don't directly contribute to the main purpose. It's not extreme, but the mix reduces focus.
The tool surface has notable gaps in coverage for the Codex domain. Core operations like code execution and batch processing are covered by 'ask-codex' and 'batch-codex', but there are missing operations such as code review, error handling, or integration with version control. Tools like 'brainstorm' and 'fetch-chunk' add niche functions, but the set lacks a cohesive lifecycle for code tasks, which could lead to agent workarounds.