agy_subagents
Related Servers
Alternatives to agy_subagents
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceAn MCP server that lets OpenAI Codex delegate tasks to Google Gemini agents as isolated background workers, with Git worktree isolation, loop detection, and security boundary enforcement.72MIT
- AlicenseAqualityBmaintenanceAn MCP server that enables a supervising OpenAI Codex agent to delegate bounded implementation tasks to isolated worker threads with enforced file scopes and verification, optionally running in parallel git worktrees.59 npm7MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that uses Google Antigravity subagents as parallel workers for coding agents, enabling efficient task delegation with compact results.MIT
- 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
- AlicenseAqualityDmaintenanceLocal MCP server that exposes delegation tools for Codex, Claude, and Antigravity CLI, enabling an orchestrator agent to assign tasks to these sub-agents via non-interactive CLI commands.3MIT
- AlicenseNot gradedqualityCmaintenanceA local-first MCP orchestration server that uses Codex as lead planner and Antigravity as host to delegate and review bounded tasks with Git integration and persistent SQLite state.Apache 2.0
TDQS
Scored across 6 tools
Each tool maps to a distinct phase of the subagent lifecycle: spawn, wait, send_input, status, close, health. Descriptions explicitly delineate blocking vs non-blocking and clarify that agy_status is read-only inspection while agy_wait_agent blocks for results, so there is no realistic misselection.
All tools share a uniform agy_ snake_case prefix and readable names. The only inconsistency is style: most use verbs (spawn, wait, send, close) while agy_status and agy_health are noun-style inspection tools, a minor but noticeable deviation.
Six tools cover the complete subagent lifecycle without redundancy, matching the mirrored native Codex primitives almost one-to-one. Nothing feels padded or missing at this scope.
Spawn, wait, follow-up input, status, close, and health give full lifecycle coverage including worktree cleanup and pool diagnostics. Minor gaps: no explicit enumeration of individual agent IDs or metadata beyond the pool aggregate, and no dedicated result-retrieval tool once an agent has already been collected.