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.23 npmMIT
- AlicenseNot gradedqualityCmaintenanceLets 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
- AlicenseCqualityDmaintenanceConnects 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.8140 npm176MIT
- 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.995 npmMIT
- AlicenseAqualityBmaintenanceTwo 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.8377 npm6MIT
- AlicenseAqualityBmaintenanceEnables 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.6116 npm1MIT
TDQS
Scored across 6 tools
Each tool maps to a distinct action in the discussion lifecycle: start, reply, read, cancel, forget, and model catalog lookup. The potentially confusing pair, cancel and forget, is explicitly differentiated by interrupting a turn versus releasing local output.
All names use snake_case with a consistent entity_action pattern: discussion_start, discussion_read, discussion_reply, discussion_cancel, discussion_forget, and models_list. The model catalog tool differs only in entity name, which reflects its distinct scope.
Six tools is a well-scoped set for managing Codex discussion turns plus fetching the model catalog. Every tool has a clear lifecycle role, with no redundant or filler tools.
The surface covers the core lifecycle: model discovery, starting a discussion, replying, reading output, canceling a turn, and forgetting local output. Minor gaps include no explicit tool to list existing discussions or to inspect saved history outside a known discussion/turn, but agents can work around this by tracking IDs.