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. In central worker mode, every MCP client should use the same CODEX_HOME and CODEX_MCP_STATE_DB so they share queue and lease state. | |
| CODEX_MCP_STATE_DB | No | Path to the MCP SQLite state database used for operations, workflows, turns, hooks, leases and diagnostics. In central worker mode, every MCP client should use the same CODEX_HOME and CODEX_MCP_STATE_DB. | |
| CODEX_MCP_EXECUTION_MODE | No | Execution mode of the MCP process. The default is "inline", where one MCP process can submit and execute operations. Set to "client" for gateway entries that only submit and poll work, or "worker" for a long-running worker process that owns codex-app-server, leases, queue slots and resource locks (e.g. CODEX_MCP_EXECUTION_MODE=worker, CODEX_MCP_EXECUTION_MODE=client). | |
| CODEX_MCP_MAX_ACTIVE_TURNS_GLOBAL | No | Maximum number of concurrently active turns across the whole worker. Default is 4. | 4 |
| CODEX_MCP_MAX_ACTIVE_TURNS_PER_AGENT | No | Maximum number of concurrently active turns per agent. Default is 3. | 3 |
| CODEX_MCP_MAX_ACTIVE_TURNS_PER_THREAD | No | Maximum number of concurrently active turns per thread. Default is 1. | 1 |
| CODEX_MCP_MAX_ACTIVE_TURNS_PER_PROJECT | No | Maximum number of concurrently active turns per project. Default is 3. | 3 |
| CODEX_MCP_MAX_APP_SERVER_PENDING_REQUESTS | No | Maximum number of pending app-server requests. Default is 8. | 8 |
| CODEX_MCP_MAX_ACTIVE_WRITE_TURNS_PER_PROJECT | No | Maximum number of concurrently active write turns per project. Default is 1. Pass resource_keys to codex_submit_task to allow disjoint write turns to run in parallel. | 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
ResponsivenessResponsive