Codex Discussion MCP
Related Servers
Alternatives to Codex Discussion MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables two-way collaboration between Claude Code and the Codex CLI: Claude can hand off plans for execution or adversarial review, while the working agent can block to ask Claude questions, report progress or findings, and receive mid-run corrections. Supports multiple named, resumable sessions per project with configurable model, effort, and sandbox settings.46 npmMIT
- AlicenseNot gradedqualityAmaintenanceLets Codex delegate coding and repository work to an installed Claude Code CLI with permission-aware inspect/write access, model and effort selection, resumable and cloud-attached sessions, and durable synchronous or asynchronous jobs.MIT
- AlicenseCqualityFmaintenanceConnects AI assistants like Claude to the Codex CLI for code analysis, editing, and execution. Supports file references with @ syntax, sandboxed code execution with approval workflows, and structured code changes for automated refactoring and documentation.842 npm176MIT
- AlicenseAqualityAmaintenanceEnables 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.942 npmMIT
- AlicenseAqualityAmaintenanceTwo AIs. One answer. ChatGPT and Claude discuss with each other until they agree, through your own signed-in CLIs: no API keys. Both read your project (never change it) and search the web. Plugin for Claude Code, Codex, Claude Desktop and the ChatGPT app.281,482 npm5MIT
- AlicenseAqualityAmaintenanceEnables Claude Code and OpenAI Codex CLI to act as bidirectional partners by letting each ask the other for code review, explanations, planning, performance analysis, and implementation help. It also provides background job tools for starting, observing, waiting on, and cancelling delegated tasks.668 npm1MIT
TDQS
Scored across 5 tools
Each tool has a clearly distinct lifecycle role: model catalog, starting a new conversation, replying to an existing one, reading/polling output, and cancelling a specific turn. The start-vs-reply boundary is well clarified by 'independent' new conversation versus 'existing discussion', so misselection is unlikely.
All names are snake_case and follow a predictable resource_action pattern: models_list, discussion_start, discussion_reply, discussion_read, discussion_cancel. The only minor variation is plural 'models' versus singular 'discussion', which is natural and still consistent.
Five tools map directly to the necessary catalog lookup plus discussion lifecycle operations. There is no obvious bloat, and the surface is neither too thin nor too heavy for this purpose.
The core lifecycle is covered: model discovery, start, reply, read/poll, and cancel. Minor gaps exist, such as no tool to list or discover existing discussions and no explicit finish/archive/delete operation, but agents can work around these when they track discussion IDs and read turn status.