Orchestrator

Orchestrator MCP

one agent. second opinion. same terminal.

Make Claude Code ask Codex. Make Codex ask Claude Code.

Use the subscriptions already signed in on your computer.

No provider API keys to configure.

See it · Compare · Install · What you get · Reviews · Workflow · Security · Dashboard

Orchestrator MCP is a local Model Context Protocol server that lets one coding agent consult another. It launches the Codex, Claude Code, OpenCode, GitHub Copilot, or experimental Antigravity CLI already installed and authenticated on your machine, routes the request, and returns a structured answer.

It does not ask for a provider key, proxy provider traffic, or silently switch models. Authentication remains inside each vendor's CLI.

Quick start from Claude Code, with Codex already logged in (other hosts: Install):

uv tool install orchestrator-mcp-server              # or pipx, pip, or brew

orchestrator-mcp-server init --host claude # writes ~/.orchestrator-mcp/config.yaml claude mcp add orchestrator \ --env ORCHESTRATOR_CONFIG=$HOME/.orchestrator-mcp/config.yaml \ --env ORCHESTRATOR_HOST_RUNTIME=claude -- orchestrator-mcp-server

Then ask Claude Code for a second opinion from Codex.

Before / After

Without Orchestrator With Orchestrator

1. Copy the prompt, diff, and context.
2. Open another coding agent.
3. Recreate the task and paste everything.
4. Bring the answer back.
5. Repeat when you need a follow-up.

1. Call orchestrator_consult.
2. Get the other agent's structured answer.
3. Reuse consultation_id for follow-ups.

The conversation stays connected from the same client.

Same subscriptions. Less context shuffling.

 Claude Code host  ──►  Orchestrator MCP  ──►  Codex CLI

Codex host ──► Orchestrator MCP ──► Claude Code CLI Any host ──► Orchestrator MCP ──► OpenCode CLI (DeepSeek, Qwen, Kimi…) Any host ──► Orchestrator MCP ──► GitHub Copilot CLI Any host ──► Orchestrator MCP ──► Antigravity CLI (experimental)

local routing no provider API keys no same-execution-identity loops

Ordinary orchestrator_consult calls exclude the host's entire runtime: Claude Code cannot use that tool to consult Claude Code, and Codex cannot use it to consult Codex. Reviews and workflows use the narrower (runtime, model) execution identity; when consult.host.model names the host precisely, they may route to a provably different, versioned model on the same runtime. The host can never route work back to its own execution identity.

How it compares

If Claude Code asking Codex is all you need, OpenAI's codex-plugin-cc does that, with background jobs. PAL MCP reaches many models through provider API keys. Orchestrator is for the rest:

Calls block the turn that makes them, often for minutes. To keep working meanwhile in Claude Code, have a background subagent make the call.

Google's Gemini CLI stopped serving free and Google AI Pro/Ultra accounts on June 18, 2026; Google models are reached here through its successor, Antigravity CLI.

Install

Claude Code: install as a plugin. Needs uv on your PATH, and at least one of Codex, Antigravity, OpenCode or GitHub Copilot installed and logged in (step 1 below). What you consult them about — prompts, diffs, file contents — goes to those providers under your own logins, and the usage is billed to your accounts with them; see the privacy policy and the Security model. In Claude Code:

/plugin marketplace add crAK1644/orchestrator-mcp

/plugin install orchestrator-mcp@orchestrator-mcp /orchestrator-mcp:setup

/orchestrator-mcp:setup writes ~/.orchestrator-mcp/config.yaml from the agent CLIs it finds, then runs doctor on it. It finds Codex, Antigravity and GitHub Copilot; OpenCode goes into the config by hand, from its agent in config.example.yaml. Then reconnect plugin:orchestrator-mcp:orchestrator in /mcp, or restart Claude Code: /reload-plugins keeps the server that started without a config.

If you added the server earlier with claude mcp add orchestrator, remove that entry (claude mcp remove orchestrator -s , with the scope claude mcp get orchestrator shows), or two copies of the server run side by side.

Every other host, and Claude Code without the plugin, installs the server itself:

Homebrew:

brew tap crAK1644/tap

brew install orchestrator-mcp-server

Apple Silicon uses a prebuilt package. Intel macOS and Linux build dependencies from source; use the uvx option if you want a faster, temporary install.

uv, pipx or pip: uv tool install orchestrator-mcp-server, pipx install orchestrator-mcp-server, or pip install orchestrator-mcp-server into a virtualenv. Python 3.11 or newer.

1. Sign in to the agent CLIs

Sign in to each agent you want Orchestrator to use:

codex login

claude auth login

These are the normal Codex and Claude Code login flows. Orchestrator checks readiness, but never reads or stores their credentials.

For OpenCode, sign in once with opencode auth login for whichever provider you plan to consult. Hosted providers only — this server does not run a model on your machine. See the OpenCode runtime section below.

For GitHub Copilot, sign in to the copy of its state that Orchestrator runs it under, not to your own: COPILOT_HOME=$HOME/.orchestrator-mcp/copilot/home copilot login. init prints that command when it writes a Copilot agent, and a consultation that finds it signed out returns it in required_action. It needs a Copilot plan; see the GitHub Copilot runtime section below.

2. Write a starter config

orchestrator-mcp-server init --host claude   # or codex: the client you run it under

init finds the Codex, Claude Code, GitHub Copilot and Antigravity CLIs installed here, writes ~/.orchestrator-mcp/config.yaml (mode 0600, never over an existing file; --path picks another), and prints the exact line for step 3. It picks the best reviewer that is not the host. Copilot is scored below the others, so it is the reviewer only when it is the only CLI beside the host, and it comes last under deep_reviewers. Its agent is written on model: auto, the one model every plan serves, so the name cannot go stale, and init prints the sign-in command from step 1. It writes no workflow: block, because only you can choose the directories a workflow may work in, and no OpenCode agent, because its model names change too often for a template; add one by hand from config.example.yaml.

Or write it by hand

consult:

database_path: ~/.orchestrator-mcp/consultations.sqlite3 timeout_s: 180

agents: codex: runtime: codex command: codex model: gpt-5.6-sol priority: 10 web_search: true scores: { coding: 95, research: 90, reasoning: 95, review: 90 }

claude: runtime: claude command: claude model: claude-opus-5-5 priority: 10 web_search: true scores: { coding: 90, research: 95, writing: 95, review: 95 }

The key each agent is filed under is its id -- the name callers pass as target_agent, and the name the dashboard writes into URLs. It has to be lowercase, start with a letter or digit, and use only letters, digits, dots, dashes and underscores, up to 64 characters. Anything else is refused at startup with a message naming the key.

See config.example.yaml for a broader annotated configuration, an OpenCode agent, a GitHub Copilot agent, and an experimental Antigravity example.

3. Add the server to your MCP client

init printed this with your paths filled in.

Claude Code

claude mcp add orchestrator \

--env ORCHESTRATOR_CONFIG=$HOME/.orchestrator-mcp/config.yaml \ --env ORCHESTRATOR_HOST_RUNTIME=claude \ -- orchestrator-mcp-server

Codex

Add this to ~/.codex/config.toml:

[mcp_servers.orchestrator]

command = "orchestrator-mcp-server" env = { ORCHESTRATOR_CONFIG = "~/.orchestrator-mcp/config.yaml", ORCHESTRATOR_HOST_RUNTIME = "codex" }

Claude Desktop

Add this to claude_desktop_config.json (Settings → Developer → Edit Config), with the command that which orchestrator-mcp-server prints: Desktop does not read your shell's PATH.

{

"mcpServers": { "orchestrator": { "command": "/opt/homebrew/bin/orchestrator-mcp-server", "env": { "ORCHESTRATOR_CONFIG": "~/.orchestrator-mcp/config.yaml", "ORCHESTRATOR_HOST_RUNTIME": "claude" } } } }

VS Code, Cursor

VS Code reads .vscode/mcp.json in the workspace; Cursor reads ~/.cursor/mcp.json with the same entry under "mcpServers" instead of "servers".

{

"serv