Super Subagents
Related Servers
Alternatives to Super Subagents
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables any MCP host to delegate work to multiple coding-agent CLIs such as Codex, Claude Code, and Antigravity as subagents, preserving native sessions and supporting team-based supervision and agent-to-agent messaging.1713 npmApache 2.0
- FlicenseNot gradedqualityAmaintenanceEnables a primary AI assistant to delegate tasks in parallel to specialized local CLI-based AI sub-agents, share project context, and synthesize their responses through a single MCP interface.-
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible clients to delegate complex multi-step programming and research goals to coordinated teams of specialized subagents, with cross-session messaging, swarm and pipeline workflows, sandboxed workspace tools, persistent SQLite state, and a live dashboard.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables a lead AI agent to spawn and coordinate manager agents, which can in turn run child agents across Codex/ChatGPT, Google Antigravity, Claude Code, and local OpenAI-compatible models. Provides messaging, waiting, transcripts, file exchange, and saved-conversation adoption so multi-agent workflows can be orchestrated from MCP hosts.MIT
- AlicenseNot gradedqualityDmaintenanceEnables MCP hosts to spawn, send input to, wait for, resume, and close provider-backed child agent sessions across Codex, Claude, and Grok adapters with configurable role presets, though it is experimental and not production-ready.MIT
- AlicenseNot gradedqualityCmaintenanceRuns each MCP server once and lets any number of AI agents connect over HTTP with their own keys, per-tool grants and audit logging, plus a shared task list, shared memory and agent-to-agent requests. Enables agents to work as a coordinated team without duplicating processes, credentials or work.4 npmMIT
TDQS
Scored across 8 tools
Each agent role (researcher/planner/coder/tester/classic) and management action (message/cancel/answer) is clearly distinct. The only slight ambiguity is between message-agent and answer-agent, but their descriptions clearly separate follow-up instructions from responding to pending questions.
All tools follow a predictable verb_noun pattern with lowercase hyphenation, and the 'launch-super-X' series is highly consistent. The deviating 'launch-classic-agent' still fits the same verb_noun structure.
8 tools is well-scoped for an agent-orchestration server, covering launching, messaging, answering, and cancelling without unnecessary bloat. Each tool earns its place in the workflow.
The tool set covers the full agent lifecycle: launching each role (researcher, planner, coder, tester, classic), resuming via message, answering pending questions, and cancelling. Status monitoring is handled via task resources, so there are no obvious dead ends.