Codex Control Plane MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CODEX_HOME | No | Codex home directory. Every MCP client should use the same CODEX_HOME in central worker mode. | |
| CODEX_MCP_STATE_DB | No | Path to the shared MCP state SQLite database. Every MCP client should use the same CODEX_MCP_STATE_DB in central worker mode. | |
| CODEX_MCP_EXECUTION_MODE | No | Execution mode for the MCP server. Use 'inline' (default), 'worker', or 'client'. In central worker mode, clients run with CODEX_MCP_EXECUTION_MODE=client, and one long-running worker process uses 'worker'. | |
| CODEX_MCP_MAX_ACTIVE_TURNS_GLOBAL | No | Maximum number of active turns globally (concurrency default: 4). | |
| CODEX_MCP_MAX_ACTIVE_TURNS_PER_AGENT | No | Maximum number of active turns per agent (concurrency default: 3). | |
| CODEX_MCP_MAX_ACTIVE_TURNS_PER_THREAD | No | Maximum number of active turns per thread (concurrency default: 1). | |
| CODEX_MCP_MAX_ACTIVE_TURNS_PER_PROJECT | No | Maximum number of active turns per project (concurrency default: 3). | |
| CODEX_MCP_MAX_APP_SERVER_PENDING_REQUESTS | No | Maximum number of pending app-server requests (concurrency default: 8). | |
| CODEX_MCP_MAX_ACTIVE_WRITE_TURNS_PER_PROJECT | No | Maximum number of active write turns per project (concurrency default: 1). |
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 |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityActive
ResponsivenessNo issues