A
licenseNot graded
qualityC
maintenanceEnables Claude Code to call OpenAI Codex for read-only design, deep reasoning, and code review tasks.
38 npm
MIT
claude-codex-bridge
by umum-ai
Related Servers
Alternatives to claude-codex-bridge
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables Claude to hand off implementation tasks to OpenAI Codex models running through the Codex CLI, with tools for listing models, delegating work synchronously or in the background, collecting results, and continuing past sessions, while Claude stays the orchestrator that reviews diffs and runs tests.2MIT
- AlicenseNot gradedqualityDmaintenanceEnables Claude Code to leverage OpenAI models for expert code review, deep architecture analysis, and security audits, with automatic markdown report generation.MIT
- AlicenseNot gradedqualityAmaintenanceTurn ChatGPT into Codex! OR Turn Claude Web into Claude Code!443 npm5,209MIT
- 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
- AlicenseAqualityAmaintenanceBridges Claude Code and OpenAI Codex through MCP, allowing cross-harness querying, code review, explanation, and implementation delegation.63 npm1MIT
TDQS
A4/5.0
Scored across 8 tools
Disambiguation5/5
Each tool maps to a distinct Codex lifecycle action: start, message, stop, resume, answer, status, events, and model listing. There is no meaningful overlap, and edge cases like codex_message versus codex_answer are clearly separated by their descriptions.
Naming Consistency4/5
All tools share a clean codex_ prefix and use snake_case consistently. Most names are imperative verbs, but models, status, and events are noun-style read operations, which is a minor deviation from a strict verb_noun pattern.
Tool Count5/5
Eight tools is a well-scoped size for a bridge server managing a live agent lifecycle. Each tool serves a necessary function without redundancy or bloat.
Completeness5/5
The set covers the full agent lifecycle: starting, sending messages, stopping, resuming, answering questions, checking status, and reading event history. There are no obvious gaps that would leave an agent unable to complete a workflow.
Maintenance
ActivitySlowing
ResponsivenessUnresponsive