SubMCP
Related Servers
Alternatives to SubMCP
No user-submitted related servers found.
Related Servers
- FlicenseAqualityBmaintenanceAn MCP server that lets Claude spawn Cursor subagents as async, bounded workers, enabling non-blocking task delegation with asynchronous completion notifications.8-
- AlicenseNot gradedqualityFmaintenanceAn MCP server that enables Cursor to delegate complex, multi-step tasks to specialized subagents, including general-purpose and explore agents, with automatic discovery of existing Claude subagents.4 npm1MIT
- FlicenseNot gradedqualityAmaintenanceA local MCP server that connects AI coding agents like Claude, Codex, and Gemini, enabling task routing, cross-model debates, and token-efficient context sharing without external APIs.14-
- AlicenseAqualityFmaintenanceMCP server for running external coding agents as background tasks inside Claude Code. Supports multiple backends including Codex, Grok, GLM, DeepSeek, and more.7MIT
- AlicenseAqualityDmaintenanceMCP server that spawns autonomous Claude Code agents in GitHub repos, enabling task delegation with persistent state, multi-step workflows, and job monitoring.47187 npm2Apache 2.0
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that turns multiple AI coding agents into a coordinated team that chats, debates, remembers, audits security, and works in parallel on the same project.MIT
TDQS
Scored across 3 tools
Each tool has a clearly distinct role: delegate runs one sub-agent, delegate_parallel runs multiple independent ones concurrently, and list_agents inspects capabilities. The descriptions explicitly delineate when to use each, with delegate_parallel contrasted against delegate for independent vs. sequential work, leaving no ambiguity.
All tool names follow a consistent snake_case verb-based pattern: delegate, delegate_parallel, list_agents. The shared 'delegate' prefix in the first two creates an obvious family, and list_agents follows a verb_noun structure, making the naming predictable and readable.
Three tools is a well-scoped count for a sub-agent delegation server. Each tool covers a necessary function—single execution, parallel execution, and environment introspection—without redundancy or missing core operations.
The tool surface fully covers the delegation workflow: run one task, run several tasks concurrently, and check the server's current capabilities and limits. No obvious gaps exist; the delegate and delegate_parallel return final reports directly, making the workflow self-contained.