Claude Parallel Tasks MCP Server
Related Servers
Alternatives to Claude Parallel Tasks MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables parallel execution of shell commands and AI coding agents (Claude, Gemini, Codex) across lists of items like files or URLs, with batched processing and real-time streaming output for batch operations.8172 npm6Apache 2.0
- AlicenseAqualityDmaintenanceEnables asynchronous and parallel execution of Gemini CLI tasks within Claude Code, allowing background task management and multi-instance parallelism.34MIT
- AlicenseNot gradedqualityAmaintenanceEnables multi-model LLM council reviews and parallel sidecar conversations within Claude, allowing Claude to orchestrate structured reviews from various AI models and fold their responses back into the session.924 npm2MIT
- AlicenseAqualityCmaintenanceEnables delegating tasks to up to four parallel Claude subagents from Codex or other stdio MCP clients, with workspace file access and per-agent model/effort configuration.8MIT
- AlicenseNot gradedqualityDmaintenanceShare context, detect file conflicts, and send messages across parallel Claude Code sessions55 npmMIT
- AlicenseCqualityBmaintenanceManages multiple AI CLI instances (Claude Code, Codex, Gemini, Cursor) in tmux sessions for parallel task execution, with optional git worktree support.90MIT
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap with other tools, making disambiguation perfect. The tool's purpose is clearly defined and distinct by default.
The single tool name follows a clear verb_noun pattern (run_parallel_claude_tasks), and with no other tools to compare, consistency is inherently perfect. There are no deviations or mixed conventions.
A single tool is too few for a server named 'Claude Parallel Tasks MCP Server', which suggests a broader scope for managing parallel tasks. This minimal set feels thin and underdeveloped for the implied functionality.
The server lacks essential operations for a parallel tasks domain, such as listing, monitoring, canceling, or retrieving results of tasks. With only a run tool, the surface is severely incomplete and will likely cause agent failures in managing task lifecycles.