Orchestrator — Claude Code MCP server: ask another agent
A local MCP server that lets one coding agent consult another — Codex, Claude, OpenCode, GitHub Copilot or Antigravity. Handy when a diff needs a second pair of eyes.
claude mcp add orchestrator-mcp -e ORCHESTRATOR_HOST_RUNTIME=<ORCHESTRATOR_HOST_RUNTIME> -e ORCHESTRATOR_CONFIG=<ORCHESTRATOR_CONFIG> -- uvx orchestrator-mcp-serverWhat Orchestrator does
Orchestrator starts a CLI agent that is already installed and signed in on your machine, hands it the request and brings back a structured answer. No provider keys are involved: each vendor's CLI keeps its own login, and usage is billed to your accounts. A plain orchestrator_consult call excludes the host runtime entirely, so Claude cannot use the tool to reach Claude, and Codex cannot reach Codex. The reply carries a consultation_id you can reuse for follow-ups.
In Claude the install goes through the plugin: /plugin marketplace add crAK1644/orchestrator-mcp, then /plugin install orchestrator-mcp@orchestrator-mcp, then /orchestrator-mcp:setup. Setup builds ~/.orchestrator-mcp/config.yaml from the CLIs it detects and runs doctor against it. You need uv on your PATH, and OpenCode has to be added to the config by hand from the example. Afterwards reconnect plugin:orchestrator-mcp:orchestrator in /mcp or restart Claude.
Calls block the turn that makes them, sometimes for minutes. In Claude, hand the call to a background subagent and keep working. Google models are reached through Antigravity CLI.
What it helps with
- get a second opinion on a diff without pasting it elsewhere
- continue a consultation via the same
consultation_id - compare answers from agents of different vendors on one task
- ask Codex from inside Claude
- keep a local record of calls and cost estimates
Example prompts for the agent
- Ask Codex whether this diff has a bug
- Have OpenCode walk through
parse_configand bring its answer back - Continue the last consultation using its
consultation_id
How to install Orchestrator
Platform CLI
claude mcp add orchestrator-mcp -e ORCHESTRATOR_HOST_RUNTIME=<ORCHESTRATOR_HOST_RUNTIME> -e ORCHESTRATOR_CONFIG=<ORCHESTRATOR_CONFIG> -- uvx orchestrator-mcp-serverReplace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from orchestrator-mcp-server <command>
Platform CLI
codex mcp add orchestrator --env ORCHESTRATOR_HOST_RUNTIME=<ORCHESTRATOR_HOST_RUNTIME> --env ORCHESTRATOR_CONFIG=<ORCHESTRATOR_CONFIG> -- uvx orchestrator-mcp-serverReplace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from orchestrator-mcp-server <command>
Config file
{
"mcpServers": {
"orchestrator": {
"command": "uvx",
"args": [
"orchestrator-mcp-server"
],
"env": {
"ORCHESTRATOR_HOST_RUNTIME": "<ORCHESTRATOR_HOST_RUNTIME>",
"ORCHESTRATOR_CONFIG": "<ORCHESTRATOR_CONFIG>"
}
}
}
}Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from orchestrator-mcp-server <command>
Config file
{
"servers": {
"orchestrator": {
"type": "stdio",
"command": "uvx",
"args": [
"orchestrator-mcp-server"
],
"env": {
"ORCHESTRATOR_HOST_RUNTIME": "<ORCHESTRATOR_HOST_RUNTIME>",
"ORCHESTRATOR_CONFIG": "<ORCHESTRATOR_CONFIG>"
}
}
}
}Replace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from orchestrator-mcp-server <command>
Platform CLI
gemini mcp add -e ORCHESTRATOR_HOST_RUNTIME=<ORCHESTRATOR_HOST_RUNTIME> -e ORCHESTRATOR_CONFIG=<ORCHESTRATOR_CONFIG> orchestrator uvx orchestrator-mcp-serverReplace <…> with your own values. uvx runs the command named after the package; if the README names another one, use uvx --from orchestrator-mcp-server <command>
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 Orchestrator
How do I install Orchestrator in Claude Code?
Add the marketplace with /plugin marketplace add crAK1644/orchestrator-mcp, then install the plugin: /plugin install orchestrator-mcp@orchestrator-mcp. Run /orchestrator-mcp:setup afterwards.
What does Orchestrator do?
It lets one coding agent call another CLI agent and return that answer to the current client. Requests travel through the logins those CLIs already have.
Do I need API keys?
No. The server asks for no provider key and does not proxy provider traffic: authentication stays inside each CLI, and usage is billed to your subscriptions.
