A
licenseA
qualityC
maintenanceMCP server that lets Claude Code drive the local Codex CLI as a sub-agent for concurrent queries and optional file/shell actions, using the CLI's existing login and sessions.
4
81 npm
1
MIT
codex-mcp-bridge
Related Servers
Alternatives to codex-mcp-bridge
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceMCP server that routes Claude Desktop chat into Claude Code, enabling headless execution and terminal handoff with session continuity.4MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that bridges Claude Desktop with Claude Code, allowing users to delegate tasks to Claude Code directly from Claude Desktop conversations, supporting both synchronous and background execution with session reuse.2 npmMIT
- AlicenseBqualityDmaintenanceMCP server for managing Claude Code conversation sessions1296 npmMIT
- FlicenseNot gradedqualityDmaintenanceLocal MCP server for Codex to send prompts to ChatGPT Web Pro extension and manage repository tasks safely.1-
- AlicenseAqualityBmaintenanceLocal MCP bridge that lets Codex operate local Claude Code sessions, including listing, starting, resuming, forking, prompting, and stopping conversations via the Remote Control CLI.14MIT
TDQS
A4/5.0
Scored across 9 tools
Disambiguation3/5
delegate_to_codex, start_codex_thread, and send_to_codex_thread heavily overlap—delegate_to_codex is essentially a superset (create + send + wait), and the new-conversation vs unfinished-work distinction is explained only via lengthy prose that an agent can easily miss. list_codex_threads, read_codex_thread, open_codex_thread, and interrupt_codex_turn are more clearly distinct, but the core conversation-starting trio remains fuzzy.
Naming Consistency4/5
Most tools follow a consistent verb_codex_noun pattern (list_codex_threads, send_to_codex_thread, read_codex_thread, stop_codex_app_server). The main deviation is codex_bridge_status, which flips to a noun-first form, though it is still readable and clearly its own concept.
Tool Count4/5
Nine tools is well-scoped for a bridge that manages Codex sessions, covering session lifecycle, delivery, monitoring, and status. Slightly heavy given the operational overlap among the send/delegate/start trio, but each tool maps to a real capability.
Completeness4/5
The surface covers create (start/delegate), list, read, send, interrupt, open, and status—effectively the full session lifecycle an agent needs. The only notable gap is an explicit thread close/delete operation, but the descriptions imply tasks are intentionally never closed, so this is minor.
Maintenance
ActivityActive
ResponsivenessSlow