Forge Orchestrator — Claude Code MCP server: how to install
Coordinates Claude Code alongside other AI CLI tools on a shared repository. Prevents file conflicts and overlaps using exclusive locks, shared state, and unified task graphs.
Open on GitHubWhat Forge Orchestrator does
The orchestrator ships as a standalone Rust binary with zero dependencies. It initializes a .forge/ directory inside your repository to store task dependencies, event logs, and an architectural knowledge base. Through an stdio MCP server with 12 tools, any attached AI coding assistant can query task state, claim items, or release file locks.
Its primary purpose is stopping simultaneous edits from clashing when Claude Code and runners like Codex CLI or Antigravity CLI (agy) touch the same repository. Exclusive file locks prevent one assistant from overwriting unfinished changes made by another. You can generate a task graph directly from SPEC.md using the CLI planner.
Specification drift detection is disabled under the default rule-based engine: scoring divergence requires an OpenAI API key. The project is currently in alpha, so public interfaces may shift between releases.
What it helps with
- prevent concurrent file edits across multiple AI coding tools
- generate a dependency-aware task plan from
SPEC.md - coordinate shared repository work between Claude Code and Codex CLI
- record architectural decisions into a local project knowledge base
Example prompts for the agent
- Build a dependency-aware task graph from
SPEC.mdusingforge plan --generate. - Inspect active assignments and file locks with
forge status. - Run pending repository tasks headlessly by invoking
forge run.
How to install Forge Orchestrator
Install
The MCP registry has no launch command for it: see the repository README
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about Forge Orchestrator
How do I install Forge Orchestrator for Claude Code?
Download the binary via curl -fsSL https://forge.nxtg.ai/install.sh | sh and initialize the project with forge init. When the claude executable is in your PATH, the installer automatically registers the nxtg-forge marketplace and installs the companion plugin nxtg-forge-orchestrator@nxtg-forge.
What does Forge Orchestrator do?
It provides a 12-tool MCP interface that synchronizes multiple AI tools working on a single repository. The orchestrator tracks tasks in a local .forge/ directory and locks active files to prevent merge collisions.
Is an API key required to use Forge Orchestrator?
No, the built-in rule-based brain works locally without any external account. You only need an API key if you switch to openai via forge config brain openai to evaluate drift against your specification.
