A
licenseNot graded
qualityC
maintenanceLocal authenticated MCP bridge enabling bounded cross-model review between Claude Code and Codex, with isolated artifacts/workspaces and secure per-role endpoints.
162 npm
MIT
claude_mcp
by catid
Related Servers
Alternatives to claude_mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables Claude Code to delegate coding tasks—investigation, review, long-running background jobs, and optional file edits—to a locally installed OpenAI Codex CLI, with the model and reasoning effort chosen per task and read-only execution by default. Follow-up requests reuse Codex's existing context, and write-enabled delegations can be confined to a managed git worktree so the user's own checkout stays untouched.9108 npmMIT
- FlicenseCqualityBmaintenanceEnables 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-
- 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 gradedqualityCmaintenanceEnables bidirectional, asynchronous task delegation between Codex and Claude Code, plus optional DeepSeek API consultations, with workspace locking, recursion protection, and bounded permissions.MIT
TDQS
A3.6/5.0
Scored across 3 tools
Disambiguation4/5
The three tools map onto a clear read-only / non-editing / editing split: opus_status inspects configuration, opus_consult plans and reviews without writes, and opus_execute delegates with write access. opus_consult and opus_execute could still be momentarily confused since they both invoke a model session, but the descriptions explicitly distinguish edit vs. no-edit behavior.
Naming Consistency5/5
All three tools follow the same opus_<verb> pattern, with concise verbs (status, consult, execute) that consistently describe the action. No mixing of conventions or casing.
Tool Count4/5
Three tools is minimal but each serves a distinct role in the delegate-to-Opus workflow, so nothing is redundant. It sits at the thin edge of the acceptable range, with no lifecycle tooling (cancel, resume, list sessions) to round it out.
Completeness3/5
Configuration check, planning/review, and execution are covered, but the surface has notable gaps: no way to list or resume sessions, cancel or abort a long run, or retrieve results of a previously delegated task. Agents must work around these lifecycle omissions.
Maintenance
ActivityStale
ResponsivenessNo recent community issues