F
licenseNot graded
qualityD
maintenanceA flexible MCP server enabling multiple Claude AI sessions to coordinate work across machines through shared state management.
1
-
Claude Orchestrator MCP
Related Servers
Alternatives to Claude Orchestrator MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceMCP server for managing Claude Code conversation sessions1268 npmMIT
- AlicenseNot gradedqualityBmaintenanceMCP server that provides cross-session awareness for Claude Code, tracking active sessions, file conflicts, and shared todos to enable agent coordination without blocking tool calls.860 npmMIT
- AlicenseNot gradedqualityDmaintenanceA local-first MCP server for coordinating parallel AI coding sessions with tools like Claude Code and Codex in a single repository.2MIT
- AlicenseAqualityDmaintenanceAn 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.627 npm1MIT
- FlicenseNot gradedqualityCmaintenanceA remote MCP server enabling multiple Claude Code sessions to collaborate via shared presence, project-scoped notes, tasks, and memory, with owner-approved access control.-
TDQS
A3.5/5.0
Scored across 11 tools
Disambiguation4/5
Each tool targets a distinct action: session lifecycle (register/unregister/heartbeat), sync coordination (request/acknowledge/get_pending), and communication (notify/get_updates/query_state/list_group/get_topology). The read-oriented cluster (get_cross_project_updates, query_project_state, get_pending_sync_points) has some conceptual overlap, but descriptions clarify when to use each.
Naming Consistency4/5
Nearly all tools follow a predictable verb_noun snake_case pattern (register_session, request_sync_point, get_topology). The lone deviation is 'heartbeat', which is a bare noun rather than a verb phrase, though it reads clearly as a keepalive action.
Tool Count5/5
11 tools is well-scoped for a cross-session orchestration server, with each tool covering a needed capability (lifecycle, sync, messaging, discovery). No obvious redundancy or filler.
Completeness4/5
The surface covers the full orchestration lifecycle: registration, heartbeat, unregistration, sync request/acknowledge/pending, notifications, state queries, and topology discovery. Minor gaps like session detail lookup or topology mutation are not essential for coordination workflows.
Maintenance
ActivityInactive
ResponsivenessNo issues