Claude Orchestrator MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| register_sessionA | Register this Claude Code session with the orchestrator. Call this when starting work on a project to enable cross-project coordination. |
| unregister_sessionA | Unregister this session from the orchestrator when done working. |
| heartbeatA | Send a heartbeat to keep the session active and optionally update current task. |
| get_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. |
| notify_related_sessionsA | Broadcast a notification to all related sessions in your project group. Use this when you make significant changes that others should know about. |
| query_project_stateB | Query the current state of a related project. Use this to check what another service is working on or its recent changes. |
| list_group_sessionsB | List all active sessions in a project group. |
| request_sync_pointB | Request a synchronization point with related sessions. Use this when you need to coordinate a change across multiple services. |
| acknowledge_sync_pointC | Acknowledge a sync point request from another session. |
| get_pending_sync_pointsB | Get all pending sync point requests that involve your session. |
| get_topologyC | Get the project topology configuration. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.