mcp-codex-dev
Related Servers
Alternatives to mcp-codex-dev
No user-submitted related servers found.
Related Servers
- FlicenseBqualityNot gradedmaintenanceAn MCP server for the OpenAI Codex CLI that provides coding assistance with multi-turn session management and reasoning depth control. It enables users to perform code analysis, generation, and refactoring through Claude with native resume support for conversational context.4577 npm1-
- AlicenseAqualityBmaintenanceAn MCP server for running Claude Code and the Codex CLI as a pair: Claude drives, and hands self-contained tasks to Codex as background jobs.8MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that enables Claude Code to delegate tasks to Codex for real-time collaborative code generation and execution.4 npmMIT
- AlicenseNot gradedqualityCmaintenanceA cross-platform desktop MCP server that allows Codex and other MCP clients to execute tasks via the Claude Agent SDK, providing tools for code generation, file editing, and task management with session continuation.14MIT
- AlicenseBqualityBmaintenanceMCP server connecting Claude/Cursor to Codex CLI, enabling code analysis via @ file references, multi-turn conversations, sandboxed edits, and structured change mode.13282 npm24MIT
- AlicenseAqualityDmaintenanceMCP server that lets Claude Code ask GPT Codex for adversarial planning, code review, debugging, research, and risk triage without leaving your project workflow.96 npm1MIT
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: exec for raw CLI execution, health for environment checks, review for code reviews, session_discard and session_list for session management, and tdd for TDD-based implementation. There is no overlap or ambiguity in functionality, making tool selection straightforward for an agent.
Most tools follow a consistent verb-based naming pattern (exec, health, review, tdd), but session_discard and session_list deviate with a noun_verb structure. This minor inconsistency is still readable and does not severely impact usability, though it breaks the overall pattern slightly.
With 6 tools, the server is well-scoped for its purpose of interacting with Codex CLI. Each tool serves a specific, necessary function (execution, health checks, reviews, session management, TDD), and none feel redundant or out of place, making the count appropriate.
The tool set covers core workflows for Codex CLI interaction, including execution, health, reviews, and session management. However, there are minor gaps, such as no explicit tool for creating or updating sessions beyond resume capabilities, which agents might need to work around using exec or other tools.