A
licenseA
qualityD
maintenanceAn MCP server that enables Claude to orchestrate multiple autonomous Claude Code agents working in parallel across different projects, with tools to dispatch, monitor, and manage their progress.
6
54 npm
1
MIT
central-mcp
by andy5090
Related Servers
Alternatives to central-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA shared MCP hub that enables multiple coding-agent CLIs to register, discover, and communicate asynchronously via a standalone daemon. It provides MCP tools for agent registration, session management, non-blocking messaging, and cursor-based event reading.3 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP-capable AI coding tools to dispatch tasks in parallel to multiple installed AI CLIs with automatic failover, plus run multi-AI discussions and cross-reviews, hand code off between tools, manage shared workspaces, and inspect token usage, traffic, clients, and task memory. Also exposes image recognition (OCR/vision), tool and client administration, and log access through a single local hub.14 npmMIT
- AlicenseNot gradedqualityBmaintenanceA vendor-neutral MCP server that enables coding agents to delegate tasks, share context, and work as a team through a shared blackboard and task queue.2 npmMIT
- AlicenseNot gradedqualityDmaintenanceAn MCP orchestration server that coordinates multiple AI coding agents using Copilot CLI for parallel task execution with dependency management, file locking, and observability.1ISC
- FlicenseNot gradedqualityAmaintenanceEnables a primary AI assistant in an IDE to delegate tasks to multiple specialized AI coding assistants in parallel, share project context, and synthesize their responses through one standardized MCP interface.-
TDQS
A3.8/5.0
Scored across 20 tools
Disambiguation4/5
Most tools have clearly distinct purposes (dispatch vs check_dispatch vs tail_dispatch vs cancel_dispatch are well separated), and project_status vs project_pulse is explicitly contrasted. However, the read-side portfolio tools overlap: portfolio_digest, orchestration_history, dispatch_history, and list_dispatches all report on dispatch/activity state and could be misselected without careful reading of the long descriptions.
Naming Consistency3/5
There is a mix of conventions: verb_noun tools (list_projects, update_project, cancel_dispatch, add_project) alongside noun-only tools (project_status, project_pulse, token_usage, portfolio_digest, orchestration_history) and bare 'dispatch'. The names remain readable, but the inconsistent verb/noun framing means the pattern isn't predictable.
Tool Count4/5
20 tools is on the heavy side, but the domain is broad (registry CRUD, dispatch lifecycle, sessions, user preferences, and portfolio/token analytics), so most tools earn their place. A few analytics/read tools could plausibly be consolidated, keeping it just short of ideal.
Completeness4/5
Coverage is strong: full registry CRUD (list/get/add/update/remove/reorder), the full dispatch lifecycle (dispatch/check/tail/cancel/list/history), session listing, preference read/write, and multiple analytics views. Minor gaps exist around per-dispatch detail retrieval and note management, but core workflows have no dead ends.
Maintenance
ActivitySlowing
ResponsivenessLimited data