codex-subagent-mcp
Related Servers
Alternatives to codex-subagent-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceLets Codex delegate coding and repository work to an installed Claude Code CLI with permission-aware inspect/write access, model and effort selection, resumable and cloud-attached sessions, and durable synchronous or asynchronous jobs.MIT
- AlicenseAqualityDmaintenanceEnables Claude Code to delegate tasks to OpenAI's Codex CLI (GPT-5.4) with structured execution traces, parallel execution, session persistence, and adversarial code review.15MIT
- AlicenseNot gradedqualityBmaintenanceEnables Claude Code to delegate bounded, read-only analysis and isolated patch proposals to the locally installed Codex CLI over MCP, with sanitized live status, revision-aware polling, and reviewable results.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables Codex to delegate bounded engineering jobs to Claude Code CLI in isolated Git worktrees with strict security and allowance pacing.MIT
- AlicenseNot gradedqualityBmaintenanceEnables Claude Code to call OpenAI Codex for read-only design, deep reasoning, and code review tasks.18 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables Codex to delegate tasks to Claude Code, allowing Claude to investigate, edit, and verify changes in the repository with background job management.7 npmMIT
TDQS
Scored across 8 tools
Each tool targets a clearly distinct operation: delegation, follow-up on a thread, diagnostics, and three separate job-management actions (cancel/result/status) that are well differentiated by their descriptions. The only near-overlap is codex_recommend vs list_codex_models, but one advises and the other enumerates, which the descriptions make explicit.
Most tools follow a consistent codex_<action> or codex_job_<action> snake_case pattern, which is predictable and readable. list_codex_models deviates by putting the verb first (list_) instead of the codex_ prefix used elsewhere, a minor inconsistency in an otherwise coherent scheme.
Eight tools is well-scoped for a delegation wrapper: one core action, one follow-up, three job-lifecycle controls, one diagnostic, and two model-selection helpers. Nothing feels padded or redundant.
The surface covers the full delegation lifecycle (run, follow-up, background status/result/cancel) plus setup diagnostics and model discovery, which is solid coverage of the stated domain. Minor gaps remain, such as no explicit way to enumerate or resume prior threads beyond a job_id from status.