Claude Code Subagent MCP
Related Servers
Alternatives to Claude Code Subagent MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceAn MCP server that lets host-side Claude Cowork dispatch work into Claude Code running inside your devcontainer over stdio.16MIT
- AlicenseAqualityBmaintenanceAn MCP server that lets Claude Code delegate durable background tasks, reasoning profiles, thread resumption, and native image generation to your local Codex CLI.101MIT
- AlicenseNot gradedqualityCmaintenanceA cross-platform desktop MCP server that allows Codex and other MCP clients to execute tasks via the Claude Agent SDK, providing tools for code generation, file editing, and task management with session continuation.14MIT
- AlicenseNot gradedqualityBmaintenanceMCP server that lets Claude Code or any MCP client delegate coding tasks to the local Cursor Agent CLI, with persistent per-workspace sessions and tools for diffing and pushing changes.12 npmMIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that bridges Claude Desktop with Claude Code, allowing users to delegate tasks to Claude Code directly from Claude Desktop conversations, supporting both synchronous and background execution with session reuse.2 npmMIT
- AlicenseAqualityCmaintenanceMCP server that lets Claude Code drive the local Codex CLI as a sub-agent for concurrent queries and optional file/shell actions, using the CLI's existing login and sessions.437 npm1MIT
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: one is a status/inspection tool, the other is an action/delegation tool. There is no overlap or ambiguity between them.
Both tools follow a consistent verb_noun snake_case pattern (get_ and delegate_to_). The naming is clear and predictable.
With only two tools, the server feels very minimal. While the narrow scope is somewhat defensible, a typical agent would likely expect additional management tools, making this borderline.
The server provides status checking and delegation, but lacks operations for managing subagents (e.g., listing active sessions, canceling tasks, retrieving historical results). This creates a significant gap for any non-trivial workflow.