Codex App Server MCP
Related Servers
Alternatives to Codex App Server MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceLets an orchestrating agent spawn, queue, steer, and collect Codex agents through MCP tools, including resource claims, structured results, question handoff, and workflow scripts.MIT
- AlicenseBqualityBmaintenanceEnables any MCP host to delegate work to multiple coding-agent CLIs such as Codex, Claude Code, and Antigravity as subagents, preserving native sessions and supporting team-based supervision and agent-to-agent messaging.1711 npmApache 2.0
- AlicenseBqualityBmaintenanceEnables a lead AI agent to spawn and coordinate manager agents, which can in turn run child agents across Codex/ChatGPT, Google Antigravity, Claude Code, and local OpenAI-compatible models. Provides messaging, waiting, transcripts, file exchange, and saved-conversation adoption so multi-agent workflows can be orchestrated from MCP hosts.14MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP hosts to spawn, send input to, wait for, resume, and close provider-backed child agent sessions across Codex, Claude, and Grok adapters with configurable role presets, though it is experimental and not production-ready.MIT
- AlicenseNot gradedqualityBmaintenanceEnables external AI supervisors to oversee and steer native Codex through MCP, including thread and turn management, observation, interruption, approval responses, runtime status, and checkpointing.MIT
- AlicenseBqualityBmaintenanceEnables a host coding agent to launch and coordinate real subagent sessions in other agent CLIs and accounts, sharing existing MCP servers, skills, plugins, and instructions. Supports two-way messaging, automatic account failover, and mixed-CLI delegation while leaving credentials with the vendor CLIs.813Apache 2.0
TDQS
Scored across 15 tools
The tools cluster into clear lifecycle, control, and observation groups. The closest pairs—agent_send/agent_steer and agent_status/agent_result—have explicit usage guidance that distinguishes them, so an agent can usually select correctly.
The agent_ prefix is consistent, but the suffix style is mixed: most tools use imperative verbs (start, send, wait), while status, events, and result are nouns, and request_resolve/goal_set reverse the expected verb-noun order. server_info also breaks the agent_ naming pattern, though reasonably for a server-level tool.
Fifteen tools is on the higher end but fits the complexity of orchestrating background agent workers. Each tool covers a distinct lifecycle, observation, or control function, and none feels redundant or unnecessary.
The tool set covers the full agent lifecycle: start, resume, fork, guide, interrupt, observe, wait, collect results, resolve requests, set goals, and archive. There are no obvious dead ends, and every state change has a corresponding way to inspect or move forward.