A
licenseNot graded
qualityF
maintenanceArtifact-first sub-agent delegation for Codex CLI, enabling multi-step parallel work with durable logging via specialized sub-agents.
69
MIT
codex-subagents-mcp
Related Servers
Alternatives to codex-subagents-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables MCP-compatible coding agents to execute the local Codex CLI as a coding agent, including code reviews, session resume/fork, and CLI diagnostics.994 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables controlled delegation of tasks to local coding-agent CLIs and the Manus API, with strict sandboxing, approval tracking, and remote-egress safeguards.5 npmMIT
- AlicenseAqualityBmaintenanceDelegates work from MCP clients (like Claude Code) to the Codex CLI, allowing spawning of autonomous Codex subagents for tasks.2250 PyPI174MIT
- FlicenseAqualityCmaintenanceBridges Codex to external CLI coding agents for read-only code analysis and deterministic quality fixes.9-
- AlicenseNot gradedqualityBmaintenanceEnables Claude Code to offload bounded, read-heavy tasks to external agent CLIs (agy, opencode, copilot) with preflight validation, circuit breakers, and a local dashboard for monitoring delegation and subagent activity.19 npmApache 2.0
TDQS
A3.7/5.0
Scored across 4 tools
Disambiguation5/5
Each tool has a clearly distinct purpose: delegate runs one sub-agent, delegate_batch runs many, list_agents shows available agents, and validate_agents checks agent files. There is no meaningful overlap; even delegate and delegate_batch are distinguishable by scope.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern in snake_case: delegate, delegate_batch, list_agents, validate_agents. The pattern is uniform and predictable, making the set easy to navigate.
Tool Count5/5
Four tools is well-scoped for managing and running sub-agents. Each tool addresses a distinct part of the workflow (single run, batch run, discovery, validation), leaving no unnecessary bulk or sparseness.
Completeness4/5
The core delegation lifecycle is covered: listing available agents, validating configuration, running individually, and running in batches. Minor gaps exist such as no explicit tool to fetch agent details or stop/abort runs, but these do not block the primary use case.
Maintenance
ActivityInactive
ResponsivenessNo issues