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 | {} |
| logging | {} |
| prompts | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ask-codexA | Use OpenAI Codex to analyze, review, edit, or generate code. Call this tool whenever the user mentions "codex", "use codex", or wants to leverage OpenAI models (GPT-5.4, GPT-5.3-codex, etc.) for code tasks. Supports file references with @ syntax (e.g. @src/), model selection, reasoning effort control, and structured edits via changeMode. |
| batch-codexA | Run multiple tasks through OpenAI Codex in batch. Use when the user wants Codex to handle several tasks sequentially — mass refactoring, bulk code changes, or automated transformations. |
| pingC | Echo |
| HelpC | receive help information |
| versionA | Display version and system information |
| brainstormA | Brainstorm ideas using OpenAI Codex with structured frameworks (SCAMPER, design-thinking, lateral, etc.). Use when the user wants creative ideation, brainstorming, or idea generation via Codex. |
| 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: ask-codex for general code tasks, batch-codex for sequential tasks, brainstorm for ideation, and utility tools. There is slight overlap between ask-codex and batch-codex, but descriptions clarify the difference.
Tool names mostly follow a lowercase hyphenated pattern (ask-codex, batch-codex, fetch-chunk, timeout-test), but 'Help' is capitalized, breaking consistency. The mix of codex-specific and generic utility names also reduces pattern clarity.
8 tools is a reasonable number for a Codex integration server. Includes core functionality (ask-codex, batch-codex, brainstorm), response retrieval (fetch-chunk), and utilities (help, ping, timeout-test, version). Slightly weighted with utilities, but still well-scoped.
The tool surface covers primary use cases: code analysis/generation, batch processing, brainstorming, and partial response handling. Minor gaps exist (e.g., no explicit code review tool separate from ask-codex), but core workflows are supported.