codex-monitor
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CODEX_MONITOR_HOME | No | Optional. Overrides the configuration directory used for custom probes. Defaults to platform-specific path. |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| monitor_createA | Create a background monitor that watches for a condition and settles when it becomes true. Evaluation happens inside the plugin, so never write your own sleep/poll loop. Returns a monitor id; pass it to monitor_wait to pause until the condition holds. Use this for anything long-running: cluster jobs, builds, deploys, downloads, servers coming up. Installed condition types: command, file, log. |
| monitor_waitA | Block until the given monitor(s) settle (satisfied, failed, timeout, or cancelled). mode 'all' waits for every listed monitor; 'any' returns as soon as one settles. If wait_timeout_seconds elapses first, returns outcome 'wait_timeout'. Monitors keep running whenever a wait ends early, including when the call is interrupted, so call monitor_wait again with the same ids to resume. |
| monitor_runA | Convenience: monitor_create + monitor_wait in one blocking call. Creates the monitor and pauses until it settles (or wait_timeout_seconds elapses, in which case the monitor keeps running and you can monitor_wait on the returned id later). |
| monitor_statusA | Snapshot of monitors without blocking. Omit ids for all monitors. Use for a quick look; use monitor_wait (not repeated status calls) to wait for completion. |
| monitor_cancelA | Stop an active monitor. Settled monitors are left untouched. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/naowalrahman/codex-monitor'
If you have feedback or need assistance with the MCP directory API, please join our Discord server