SubMCP
Related Servers
Alternatives to SubMCP
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceAn 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.2 npm1MIT
- FlicenseNot gradedqualityAmaintenanceA local MCP server that lets a primary AI assistant delegate parts of a prompt to specialized sub-agent CLIs (Gemini, Claude, Codex, Cursor), which run in parallel against a shared context bundle. It then aggregates their findings into a single synthesized response, using existing CLI tools and subscriptions with no extra cost.-
- FlicenseNot gradedqualityAmaintenanceThis local MCP server lets a primary AI assistant delegate tasks in parallel to specialized sub-agent CLIs (Gemini, Claude, Codex, Cursor) that share the same project context, then aggregates and synthesizes their findings into one response. It uses existing CLI tools and API subscriptions with no markup, supporting 26+ MCP-compatible IDEs.-
- FlicenseNot gradedqualityAmaintenanceAn MCP server that lets Claude Code or any MCP client hand bounded work — code review, boilerplate, commit messages, format conversion, embeddings — to a local GPU model, an OpenAI-compatible endpoint, a router, or a cheap cloud API, so those files never enter the orchestrator's context window. This cuts token spend and quota use while providing a second model to sanity-check results.-
- 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.18-
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.