codex-mcp-tool
Related Servers
Alternatives to codex-mcp-tool
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceAn MCP server wrapping the Cursor CLI agent, enabling Claude Code and other MCP clients to delegate tasks to Cursor's AI agent for file writing, bash commands, and codebase queries.-
- AlicenseBqualityDmaintenanceAn open-source MCP server that connects your IDE or AI assistant to the Codex CLI, enabling non-interactive automation with codex exec, safe sandboxed edits with approvals, and large-scale code analysis via @ file references.815 npmMIT
- AlicenseNot gradedqualityAmaintenanceAn MCP server that bridges CLI coding agents like Claude Code, Codex, opencode, and Antigravity into any MCP client, enabling synchronous and asynchronous task execution, follow-up input, and a structured code review tool.103 npm1MIT
- AlicenseAqualityCmaintenanceMCP 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.437 npm1MIT
- AlicenseNot gradedqualityBmaintenanceMCP server that lets Claude Code or any MCP client delegate coding tasks to the local Cursor Agent CLI, with persistent per-workspace sessions and tools for diffing and pushing changes.12 npmMIT
- AlicenseAqualityFmaintenanceAn MCP server that integrates Codex CLI into Claude Code workflows for code writing, execution, and review with session management. It features real-time progress monitoring via a local HTTP dashboard and supports detailed configuration for various coding tools.67 npm166MIT
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose: ping for echo, help for guidance, version for system info, brainstorm for idea generation, fetch-chunk for retrieving subsequent chunks, timeout-test for testing timeouts, list-skills for discovering skills, and do-act for task execution with verification. No overlapping purposes.
Tool names mix single words (ping, help, version, brainstorm) and hyphenated compounds (fetch-chunk, timeout-test, list-skills, do-act). While many follow a verb-noun pattern (fetch-chunk, list-skills, do-act), inconsistences like 'timeout-test' (noun-verb) and single-word names reduce overall coherence.
With 8 tools, the server is well-scoped for its purpose. Each tool earns its place by covering essential functionalities: basic info, brainstorming, workflow handling, testing, skill discovery, and task execution.
The tool set covers major areas: health check (ping), help, version, creativity (brainstorm), multi-step responses (fetch-chunk), timeout testing, skill discovery, and task execution (do-act). Minor gaps exist, such as a tool to list available modes or configure settings, but core workflows are supported.