orc-mcp
Reads other sessions' commits, diffs, and committed files directly from each repository's git, using HEAD at join time as the base commit and exposing tools like get_changes, get_diff, and read_file.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
orc-mcp
A local-only MCP orchestrator that coordinates multiple Claude Code sessions (one session = one repository).
The orchestrator itself is a resident program with no LLM inside. It has three jobs:
Ledger: stores the design decisions and task progress each session reports, in SQLite
git reader: reads other sessions' commits, diffs, and files directly from each repository's git
Signal: accepts "wait until that task is done", and when the condition is met, returns along with the changes
Requirements
Node.js 22.13 or later (uses the built-in
node:sqlite; on 22.x it prints an experimental-feature warning)git
Related MCP server: z-code-mcp
Starting
npm install
npm run build
ORC_TOKEN=$(openssl rand -hex 16) npm startEnvironment variable | Default | Description |
|
| Listening port (always bound to |
|
| SQLite file |
| none | When set, |
|
| A session that has not called in for longer than this is considered stalled |
|
| A connection used within this many seconds is considered "live", and joining under the same name is rejected |
Connecting from each repository
Copy mcp.json.example to .mcp.json in each repository. The content can be the same for every repository (session names are not written in the config file).
Joining a project
Tell each session the project name in chat.
Join the orchestrator with project name
shop
The session calls join_project and can then interact only with sessions that joined under the same project name. Tasks, design decisions, and repositories of sessions in other projects are completely invisible.
Project name: a name shared by all participants. Alphanumerics,
_, and-, up to 40 charactersYour name: what you are called within the project. Defaults to the repository name; can be changed with
name
worktrees
This also works as-is when a repository has multiple sessions (when a worktree is created per session).
The unit of registration is the worktree. Two worktrees of repository a can join different projects
fooandbarThe default name is the main repository's name (
ain this example), not the worktree's directory nameThe changes other sessions see are the commits on the branch checked out in that worktree
Example: when repositories a and b each have a session for foo and one for bar, only the a and b that joined foo see each other, and only the a and b that joined bar see each other.
Duplicate registration
The following are rejected as duplicate registrations.
Situation | Result |
In the same project, a different repository tries to use the same name | Rejected (specify a different |
A registered repository (worktree) is registered under a different name or a different project | Rejected ( |
A session that has already joined tries to join another project as well | Rejected ( |
The same name and repository are in use by another live session | Rejected (can be taken over with |
Rejoining with the same project name, name, and repository is treated as a reconnection and keeps the tasks and base commit. After restarting the orchestrator, rejoin from each session.
"Live" means the connection called the orchestrator within the last ORC_TAKEOVER_SEC seconds (120 by default).
Tools
Category | Tool | Description |
Join |
| Join by declaring a project name. HEAD at the first join becomes the base commit |
| Leave. The repository is released; tasks and design decisions left behind remain visible | |
Report |
| Record a design decision (topic, decision, rationale, scope of impact) |
| Create tasks and update progress. | |
Read |
| Roles, tasks, recent decisions, and wait status of every session in the project |
| List of design decisions | |
| Another session's commits and changed files | |
| Another session's diff | |
| Another session's committed files | |
Wait |
| Wait for a task to complete or a decision to be published |
| Cancel a wait |
wait_for waits up to 110 seconds (50 by default); if the condition is not met it returns pending and a wait_id. Calling again with the same wait_id continues the wait. A circular wait is rejected with an error at registration time.
Hooks (enforcing waits and guiding reconnection)
Calling wait_for again is only a request to the model, so Claude Code hooks reinforce it. After npm run build, put the contents of hooks.settings.example.json into each repository's .claude/settings.json (or ~/.claude/settings.json) and rewrite the paths. Set ORC_PORT and ORC_TOKEN in the environment Claude Code is started from.
Hook | Behavior |
Stop ( | When a turn ends with a wait still pending, it waits in the background. When the condition is met, it wakes Claude with the commits and design decisions. Uses no tokens while waiting |
SessionStart | If the worktree is registered, tells Claude how to rejoin and which waits remain. If the session started in a new process, allows rejoining without |
Hooks identify the session from the working directory (worktree). If the orchestrator is not running, they do nothing.
Tests
npm testCreates temporary repositories and worktrees, and checks end to end with clients for multiple sessions: joining, rejecting duplicate registration, isolation between projects, waits, cycle detection, completion notices, fetching diffs, takeover, leaving, joining from worktrees, and hooks.
License
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Git collaboration for AI agents and people: tasks, hand-offs, reviews, teams, shared memory.
One shared project for a team's coding agents: decisions, a task board and handoffs.
The team layer for AI coding agents: shared contracts, collision alerts, E2EE sessions.
Multiplayer for the coding agents your team already uses: shared tasks, decisions, skills and tools.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables multiple Claude Code sessions to communicate and share results automatically, with optional orchestration for hands-off workflow coordination.19 npmMIT
- AlicenseAqualityDmaintenanceEnables orchestration of multiple Claude Code sessions for complex multi-task coding projects with HEAD/SUB coordination and dependency-based task execution.18 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables multiple Claude Code sessions to communicate, share state, and coordinate tasks through session management, message passing, and task scheduling, supporting a three-role collaboration workflow.2MIT
- AlicenseNot gradedqualityAmaintenanceEnables coordinating Claude Code and Codex across separate Git worktrees with shared issue ownership, file reservations, messages, and explicit handoffs.213 PyPI3MIT