codex-claude-agent-mcp
Related Servers
Alternatives to codex-claude-agent-mcp
No user-submitted related servers found.
Related Servers
- 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 delegating bounded tasks from Codex to Claude Code, including read-only reviews, isolated branch edits, long-running background work, and approval handling.205 npmMIT
- AlicenseBqualityDmaintenanceEnables Codex to manage a local Claude Code companion through MCP, implementing a dual-agent workflow where Codex handles reasoning and review while Claude Code performs engineering tasks.181MIT
- 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
- AlicenseAqualityCmaintenanceEnables Codex to delegate long-running work to Claude Code via blocking MCP calls, with tools for model discovery, run, and resume without polling.3MIT
- AlicenseNot gradedqualityAmaintenanceEnables Codex to delegate implementation, independent review, rework, and acceptance tasks to Claude Code via local terminal or optional Orca sessions, tracking progress and verifying changes before merge.205 npm5MIT
TDQS
Scored across 7 tools
execute_task and run_job both serve as execution entry points with overlapping purposes, and run_job can also incorporate review, blurring boundaries with review_task. Descriptions hint at differences (review option, scope) but the job vs task distinction is not defined, leaving room for misselection.
Mostly consistent snake_case verb_noun (execute_task, review_task, continue_task, run_job, run_jobs, get_job_status), but ping breaks the pattern and run/execute verbs are used interchangeably for similar actions. Still readable and predictable overall.
7 tools is well-scoped for an orchestration server covering health check, single/batch execution, review, session continuation, and status. Each tool has a distinct role without excessive surface area.
Core lifecycle is covered: start tasks/jobs, review, continue sessions, check status, and batch runs. However, missing cancellation/abort and job listing operations are notable gaps that could hinder cleanup or discovery in longer workflows.