cc-in-codex
Related Servers
Alternatives to cc-in-codex
No user-submitted related servers found.
Related Servers
- 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.713-
- AlicenseNot gradedqualityCmaintenanceEnables Claude Code to launch and supervise a background Codex collaborator through four MCP tools, while providing a local viewer for tracking task status and message exchanges.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that enables Claude Code to delegate tasks to Codex for real-time collaborative code generation and execution.6 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables Codex to delegate tasks to interactive Claude Code sessions as role-controlled subagents for exploration, code review, and implementation, using the existing Claude Code installation on macOS.MIT
- AlicenseAqualityAmaintenanceBridges Claude Code and OpenAI Codex through MCP, allowing cross-harness querying, code review, explanation, and implementation delegation.64 npm1MIT
- 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
TDQS
Scored across 18 tools
Most tools have clearly distinct purposes, but the SDK vs TUI variants (e.g., companion_open vs companion_tui_open, companion_send vs companion_start vs companion_tui_send) could be confused by an agent despite descriptions clarifying the differences. Overall, the boundaries are mostly clear.
All tools follow a consistent 'companion_<verb>[_noun]' pattern using snake_case, with optional 'tui' prefixes for TUI-specific actions. This makes the tool set highly predictable and easy to navigate.
With 18 tools, the set is in the 16-25 range that feels heavy. Many tools exist in both SDK and TUI variants, inflating the count, though each serves a genuine purpose for the dual interfaces.
The tool set covers the full lifecycle of a companion: create/restore, send/start tasks, monitor via status/recent/result, manage with cancel/reset/resume, and TUI-specific compact/raw operations. Minor gaps include no explicit listing of all companions for a cwd, but that's not essential.