codex-manager-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CODEX_HOME | No | Codex config/session directory (if non-standard location). Default: ~/.codex | ~/.codex |
| CODEX_MANAGER_STATE | No | Path to the state file. Default: ~/.codex-manager/state.json | ~/.codex-manager/state.json |
| CODEX_MANAGER_CHANNELS | No | Set to '1' to enable claude/channel push (requires launching Claude Code with --dangerously-load-development-channels server:codex-manager). | 0 |
| CODEX_MANAGER_CODEX_PATH | No | Explicit path to the codex executable. If not set, auto-resolved. | |
| CODEX_MANAGER_CODEX_WINDOWS_HIDE | No | Set to '1' to use CREATE_NO_WINDOW to hide codex windows (only needed in console-less environments; keep off in normal terminals). | 0 |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| codex_runD | – |
| codex_listD | – |
| codex_messagesD | – |
| codex_sendD | – |
| codex_stopD | – |
| codex_hookD | – |
| codex_discoverD | – |
| codex_adoptD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Without descriptions, tools like codex_hook, codex_discover, and codex_adopt are highly ambiguous. codex_send, codex_messages, and codex_run could easily be confused for similar actions.
All tools share the codex_ prefix and mostly use verb-like names (run, list, send, stop, adopt), though codex_messages is a noun, creating a minor deviation.
Eight tools is a well-scoped count for a manager-style server, providing enough varied operations without being overwhelming.
The surface appears to cover run/stop/send/list but lacks evident update/delete or configuration operations. The absence of descriptions makes it impossible to confirm full lifecycle coverage.