claude-codex-mcp
Related Servers
Alternatives to claude-codex-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables an MCP client to delegate coding work to independently configured sub-agent sessions with any connected model, agents, skills, parallel execution, permission controls, and full API access, returning answers, changed files, and costs.15MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients like Claude Code to delegate coding tasks to the local Cursor Agent CLI, with persistent per-workspace sessions that resume across calls.12 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables ChatGPT (or any MCP client) to delegate coding tasks to a local Hermes-backed agent with async job management, supporting read-only investigation, implementation, and continuation of sessions via secure MCP tunnel.1MIT
- AlicenseAqualityBmaintenanceEnables MCP clients such as Claude Code, Codex, and Cursor to dispatch background subagent jobs to the Antigravity IDE's local agent engine and collect results asynchronously. Jobs run through the IDE's authenticated session without an API key, with optional Gemini REST fallback and on-disk job history.63MIT
- AlicenseNot gradedqualityAmaintenanceConnects MCP clients such as Claude, Cursor, and VS Code to an OpenCode server's headless API, enabling users to ask questions, delegate and run coding tasks, monitor background jobs, answer prompts and permission requests, and review resulting changes across multiple projects. Sessions accept absolute server-side project directories, support both blocking and asynchronous workflows, and expose persisted job records for recovering or cancelling work.23,789 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to spawn and manage headless opencode sessions as sub-agents for coding work, including parallel jobs, session continuation or forking, transcripts, and cleanup. It returns structured results such as final messages, tool-call summaries, errors, token usage, and cost.230 npm158 PyPI3MIT
TDQS
Scored across 5 tools
codex_task, codex_image, and codex_models target clearly distinct purposes (delegation, image generation, model discovery). The one hazard is codex_job vs codex_jobs, whose near-identical names differ only by number; descriptions do clarify (single-job wait/fetch/cancel vs listing recent jobs), so the overlap is minor rather than fatal.
Every tool shares the predictable `codex_` prefix plus a noun (task, job, image, jobs, models), which reads consistently. The only blemish is the singular/plural pair codex_job/codex_jobs, a small deviation from an otherwise clean scheme.
Five tools is well-scoped for a Codex-delegation server: one per core action (task, image, job polling, job listing, model listing). Each tool earns its place with no redundancy or padding.
The surface covers the full lifecycle: model discovery before choosing, task/image execution, and job wait/fetch/cancel plus listing for async runs. Cancellation being folded into codex_job rather than a dedicated tool is a minor gap an agent can work around.