codex-mcp-tool
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CODEX_CLI_PATH | No | Path to the Codex CLI executable, e.g., /opt/homebrew/bin/codex | |
| CODEX_MAX_SESSIONS | No | Maximum number of sessions to keep (default: 50) | 50 |
| CODEX_SESSION_TTL_MS | No | Session time-to-live in milliseconds (default: 24h) | 24h |
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 | {} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ask-codex | Execute Codex CLI with file analysis (@syntax), skills ($syntax), model selection, and safety controls. Supports changeMode. |
| batch-codex | Delegate multiple atomic tasks to Codex for batch processing. Ideal for repetitive operations, mass refactoring, and automated code transformations |
| review-changes | Run a code review against the current repository using Codex CLI native review subcommand |
| pingC | Echo |
| helpC | receive help information |
| versionA | Display version and system information |
| brainstormA | 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 |
| list-sessions | List all active conversation sessions with metadata, or manage sessions |
| health | Check Codex CLI and session health status |
| list-skillsA | Discover available Codex skills from .agents/skills/ directory |
| do-actA | Execute task via Codex, verify with shell command, auto-fix on failure. Act-Check-Fix loop. |
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 |
| review-changes | Execute Codex's built-in code review on current changes |
| 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 |
| list-sessions | View and manage active Codex sessions |
| health | Diagnose Codex CLI installation, authentication, and session health |
| list-skills | List available Codex skills in the current project |
| do-act | Execute task with verification-driven retry |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose: ping for echo, help for guidance, version for system info, brainstorm for idea generation, fetch-chunk for retrieving subsequent chunks, timeout-test for testing timeouts, list-skills for discovering skills, and do-act for task execution with verification. No overlapping purposes.
Tool names mix single words (ping, help, version, brainstorm) and hyphenated compounds (fetch-chunk, timeout-test, list-skills, do-act). While many follow a verb-noun pattern (fetch-chunk, list-skills, do-act), inconsistences like 'timeout-test' (noun-verb) and single-word names reduce overall coherence.
With 8 tools, the server is well-scoped for its purpose. Each tool earns its place by covering essential functionalities: basic info, brainstorming, workflow handling, testing, skill discovery, and task execution.
The tool set covers major areas: health check (ping), help, version, creativity (brainstorm), multi-step responses (fetch-chunk), timeout testing, skill discovery, and task execution (do-act). Minor gaps exist, such as a tool to list available modes or configure settings, but core workflows are supported.