Claude Orchestrator MCP
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Claude Orchestrator MCP Register my auth service session"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Claude Orchestrator MCP
An MCP server for coordinating multiple Claude Code sessions across related projects. When you're working on a multi-service system with separate repos (e.g., auth service, API gateway, frontend), this orchestrator enables sessions to communicate changes, request sync points, and stay aware of what's happening in related services.
The Problem
You have 6 repos for a platform, each with its own Claude Code session. When the auth service session modifies the User schema:
The API gateway session has no idea
The frontend session keeps using old types
Someone has to manually copy/paste context between terminals
Changes get out of sync, causing integration issues
Related MCP server: session-coord-mcp
The Solution
Claude Orchestrator acts as a coordination layer:
┌─────────────────────────────────────────────────────────────┐
│ claude-orchestrator-mcp │
│ │
│ Sessions register → Changes detected → Updates routed │
│ │
└─────────────────────────────────────────────────────────────┘
│ │ │ │
┌────┴───┐ ┌────┴───┐ ┌────┴───┐ ┌────┴───┐
│ Auth │ │ API │ │ Catalog│ │Frontend│
│Session │ │Session │ │Session │ │Session │
└────────┘ └────────┘ └────────┘ └────────┘Installation
# Clone and build
git clone <repo>
cd claude-orchestrator-mcp
npm install
npm run build
# Or install globally
npm install -g claude-orchestrator-mcpQuick Start
1. Initialize configuration
# Create example topology
npx claude-orchestrator init
# Or manually create your topology
npx claude-orchestrator group create my-platform
npx claude-orchestrator member add my-platform ~/repos/auth-service --role auth
npx claude-orchestrator member add my-platform ~/repos/api-gateway --role gateway --depends-on auth
npx claude-orchestrator member add my-platform ~/repos/frontend --role frontend --depends-on gateway2. Add to Claude Code MCP configuration
Add to your ~/.claude.json:
{
"mcpServers": {
"claude-orchestrator": {
"command": "node",
"args": ["/path/to/claude-orchestrator-mcp/dist/index.js"]
}
}
}Or if installed globally:
{
"mcpServers": {
"claude-orchestrator": {
"command": "npx",
"args": ["-y", "claude-orchestrator-mcp"]
}
}
}3. Use in your Claude Code sessions
When starting work in a repo:
> Use the register_session tool with repoPath="/Users/me/repos/auth-service",
projectGroup="my-platform", role="auth"Check for updates from other sessions:
> Use get_cross_project_updates with my session IDNotify others about a change:
> Use notify_related_sessions to broadcast that I modified the User schemaConfiguration
The topology configuration lives at ~/.config/claude-orchestrator/topology.yml:
version: "1.0"
groups:
my-platform:
name: my-platform
description: "My multi-service platform"
members:
- path: ~/repos/auth-service
role: auth
exports: [UserToken, AuthContext]
- path: ~/repos/api-gateway
role: gateway
dependsOn: [auth]
- path: ~/repos/frontend
role: frontend
dependsOn: [gateway]
communicationRules:
- when: schema_change
from: "*"
notify: dependents
priority: high
- when: breaking_change
from: "*"
notify: all
priority: criticalChange Types
schema_change- Database/GraphQL/Protobuf schema changesapi_endpoint_change- Route/controller/API changestype_definition_change- TypeScript/interface changesconfig_change- Configuration file changesdependency_update- package.json/requirements.txt changesbreaking_change- Detected via commit message patternsany_change- Catch-all for any file change
Notification Targets
"all"- Notify all members in the group"dependents"- Notify only members that depend on the source["role1", "role2"]- Notify specific roles
MCP Tools
Session Management
Tool | Description |
| Register this session with the orchestrator |
| Unregister when done |
| Keep session active, update current task |
Cross-Project Updates
Tool | Description |
| Check for updates from related sessions |
| Broadcast a change to related sessions |
State Queries
Tool | Description |
| Query another project's status/changes |
| List all sessions in a project group |
Sync Points
Tool | Description |
| Request coordination barrier |
| Acknowledge a sync request |
| Get pending sync requests |
Topology
Tool | Description |
| Get project topology configuration |
CLI Commands
# Group management
claude-orchestrator group create <name>
claude-orchestrator group list
claude-orchestrator group show <name>
claude-orchestrator group delete <name>
# Member management
claude-orchestrator member add <group> <path> --role <role> --depends-on <roles>
claude-orchestrator member remove <group> <path>
# Rule management
claude-orchestrator rule add <group> --when <type> --from <roles> --notify <targets>
# Utilities
claude-orchestrator validate
claude-orchestrator init
claude-orchestrator config-pathHow It Works
Session Registration: Each Claude Code session registers with the orchestrator, providing its repo path, project group, and role.
Change Detection: The orchestrator watches registered repos for file changes (via chokidar) and git commits (via polling). Changes are classified by type based on file patterns.
Event Routing: When changes are detected, the topology manager determines which sessions should be notified based on communication rules and dependency relationships.
Update Queuing: Updates are queued for target sessions. When a session calls
get_cross_project_updates, it receives all pending notifications.Sync Points: Sessions can request sync points for coordinated changes. Other sessions are notified and can acknowledge before the requester proceeds.
Example Workflow
Terminal 1 (auth-service):
> Register session for auth-service in my-platform group
> [Working on User schema changes...]
> Notify related sessions: "Modified User schema, added refreshToken field"
Terminal 2 (api-gateway):
> Register session for api-gateway in my-platform group
> Check for cross-project updates
> [Receives notification about User schema change]
> "Update UserToken type to include refreshToken"
Terminal 3 (frontend):
> Register session for frontend in my-platform group
> Check for cross-project updates
> [Receives notification via gateway dependency chain]
> "Update auth context to handle new token field"Development
# Install dependencies
npm install
# Build
npm run build
# Run in development mode
npm run dev
# Run CLI
npm run cli -- group list
# Type check
npm run typecheck
# Run tests
npm testLicense
MIT
Available Tools
11 toolsacknowledge_sync_pointAcknowledge Sync PointC
Acknowledge a sync point request from another session.
Inputs: sessionId (required), syncPointId (required). Returns: acknowledged, syncPointStatus
get_cross_project_updatesGet Cross-Project UpdatesA
Check for updates from other sessions in related projects. Call this periodically or when you need to know about changes in dependent services.
Inputs: sessionId (required), since, acknowledgeAll. Returns: updates, totalPending
get_pending_sync_pointsGet Pending Sync PointsB
Get all pending sync point requests that involve your session.
Inputs: sessionId (required). Returns: syncPoints
get_topologyGet TopologyC
Get the project topology configuration.
Inputs: groupName. Returns: groups
heartbeatSession HeartbeatA
Send a heartbeat to keep the session active and optionally update current task.
Inputs: sessionId (required), currentTask. Returns: acknowledged, pendingUpdates
list_group_sessionsList Group SessionsB
List all active sessions in a project group.
Inputs: groupName (required). Returns: sessions, groupName, activeCount, totalMembers
query_project_stateQuery Project StateB
Query the current state of a related project. Use this to check what another service is working on or its recent changes.
Inputs: query (required), projectPath (required). Returns: role, found, status, repoPath, +3 more
register_sessionRegister SessionA
Register this Claude Code session with the orchestrator. Call this when starting work on a project to enable cross-project coordination.
Inputs: repoPath (required), role, projectGroup. Returns: role, status, sessionId, projectGroup, +1 more
request_sync_pointRequest Sync PointB
Request a synchronization point with related sessions. Use this when you need to coordinate a change across multiple services.
Inputs: reason (required), sessionId (required), blocking, timeoutMinutes, +1 more. Returns: status, expiresAt, syncPointId, notifiedSessions
unregister_sessionUnregister SessionA
Unregister this session from the orchestrator when done working.
Inputs: sessionId (required). Returns: message, success
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 11 tools
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.
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.
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.
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
Related MCP Connectors
Shared memory MCP server for Claude Code, Codex, Gemini CLI and Cursor. Cited, editable.
Augments MCP Server - A comprehensive framework documentation provider for Claude Code
MCP server for generating rough-draft project plans from natural-language prompts.
Shared memory and mail for your AI agents. Verified with Claude Code; other MCP clients in testing.
Related MCP Servers
- AlicenseBqualityDmaintenanceMCP server for managing Claude Code conversation sessions1237 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
- AlicenseNot gradedqualityDmaintenanceA flexible MCP server enabling multiple Claude AI sessions to coordinate work across machines through shared state management.1MIT
- 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.654 npm1MIT