codex-as-mcp
Related Servers
Alternatives to codex-as-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceLets Claude and other MCP clients hand coding tasks to the Codex CLI as a sub-agent, running under the user's own Codex configuration so any configured model provider (OpenAI, DeepSeek, local models) does the work. Provides tools to start, poll, cancel and inspect jobs with compact change summaries, long-task handling, token-saving lean mode and clean process teardown.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.1721 npmApache 2.0
- AlicenseAqualityBmaintenanceEnables Cursor's main agent to delegate development tasks to Claude CLI subagents via MCP, supporting synchronous, asynchronous, and parallel task execution with monitoring and control.7ISC
- FlicenseCqualityCmaintenanceEnables Codex to delegate already-scoped coding tasks to Claude Code and manage the resulting execution and fresh read-only review sessions, returning deterministic PASS/FAIL results through a local MCP interface.719-
- AlicenseAqualityBmaintenanceEnables MCP clients like Claude Code and Codex to delegate coding tasks to Cursor's CLI agent, which implements changes in the workspace and returns clean, structured results for review.3462 npm9MIT
- AlicenseAqualityCmaintenanceEnables MCP-compatible coding agents to execute the local Codex CLI as a coding agent, including code reviews, session resume/fork, and CLI diagnostics.912 npmMIT
TDQS
Scored across 2 tools
The two tools are clearly distinguished by singular vs. parallel operation, with descriptions explicitly stating that spawn_agents_parallel handles multiple agents at once. However, both share the core 'spawn agent' purpose, so they could be confused if the agent doesn't read carefully.
Both tools use consistent snake_case with the verb 'spawn' followed by a noun, and the parallel tool adds a clear '_parallel' suffix. The naming pattern is predictable and easy to follow.
With only two tools, the server feels minimal. While the focus is narrow (spawning Codex agents), two tools is on the thin side and could arguably be combined into one with a loop.
The server covers the fundamental operations: spawning a single agent or multiple in parallel. Minor gaps include lack of configuration options (e.g., working directory or model), but these are not essential for the core purpose.