Codex Delegate MCP
Related Servers
Alternatives to Codex Delegate MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP bridge for calling local coding-agent CLIs (Codex, Claude) from another agent, enabling bounded tasks like code review, verification, and bug hunting.MIT
- AlicenseAqualityBmaintenanceBridges Claude Code and OpenAI Codex through MCP, allowing cross-harness querying, code review, explanation, and implementation delegation.63 npm1MIT
- AlicenseAqualityDmaintenanceAn MCP server that splits coding work between ChatGPT web (planning, review) and Codex CLI (implementation), enabling agentic workflows over a local repo with risk-gated execution and safety rails.23MIT
- AlicenseBqualityBmaintenanceLocal-first multi-agent delegation and approval control for Codex via MCP, with persistent task DAG, isolated worktrees, and a web console.181MIT
- AlicenseAqualityCmaintenanceA local MCP bridge that connects existing Codex and Claude Code conversations with DSH Web, enabling delegation, result retrieval, and human-in-the-loop coordination without leaving native chat apps.111MIT
- AlicenseAqualityBmaintenanceBridges multiple CLI coding agents (Codex, Cursor, OpenCode, Claude, Antigravity) into any MCP client, enabling delegation of prompts, parallel execution, and code review workflows.671 npmMozilla Public 2.0
TDQS
Scored across 3 tools
The three tools map to clearly separate lifecycle phases: starting a run (delegate), stopping one (cancel), and diagnosing the environment (doctor). Their scopes are orthogonal, so an agent cannot reasonably misselect between them.
All three names are single lowercase verbs (delegate, cancel, doctor), giving a predictable, readable convention. It deviates from the classic verb_noun pattern only because the domain is a single resource type, so no noun is needed.
Three tools is on the lean side but each covers a genuinely distinct need for a focused delegation plugin. Nothing feels padded or redundant, though the surface is minimal.
The delegate description tells agents to 'check status before trusting result,' yet there is no explicit status, list, or result-retrieval tool — status appears only implicitly through delegate's return value. That leaves a notable gap for inspecting or enumerating runs, even though start/cancel/diagnose is covered.