Claude Code Orchestrator MCP
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Claude Code Orchestrator MCPRefactor auth module, route planning to best model and review to cheap model."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
GPT-class models are excellent.
But Plus-level quotas are not infinite.
If you spawn many internal subagents directly inside Codex, your best-model quota can disappear fast.
A deep repo audit, a parallel multi-agent review, or one ambitious refactor can burn through the budget you wanted to save for judgment.
That is why this Skill exists.
The mission:
Make Plus feel like Pro.
This Skill turns that constraint into an engineering system:
Let the best model act as the brain.
Let Claude Code plus your CCSwitch models act as hands.
Let Codex stay in control.
In other words:
Codex does not need to do every low-level subtask itself.
Codex plans, routes, supervises, and verifies.
Claude Code executes through external worker models.
This is a miniature cost-management operating system for multi-agent coding.
claude-code-orchestrator-skill is a Codex Skill with a bundled MCP server and CLI.
It lets Codex:
discover local Claude Code
read CCSwitch profiles
find all configured Claude-compatible models
score models by role
route agents to the best local model
launch Claude Code as an external worker
keep runs read-only by default
save run metadata and logs
expose everything through MCP tools
handle Windows UTF-8 output safely
write a project
CLAUDE.mdso Claude Code workers receive stable role/persona instructions
You need:
Codex
Claude Code
CCSwitch
Multiple models configured inside CCSwitch
Python 3.10+
The Skill is most powerful when CCSwitch has several models with different strengths:
strong reasoning model
strong code model
fast cheap model
review/security model
fallback model
Paste this into Codex:
Install the Codex Skill and MCP server from https://github.com/chu459/claude-code-orchestrator-skill. Put the Skill at ~/.codex/skills/claude-code-orchestrator, wire the bundled MCP server into Codex config.toml, run selftest, healthcheck, score-models, and show me the selected multi-agent routing plan. Do not print secrets.Windows PowerShell:
$tmp = Join-Path $env:TEMP "claude-code-orchestrator-skill.zip"; `
iwr -UseBasicParsing "https://github.com/chu459/claude-code-orchestrator-skill/archive/refs/heads/main.zip" -OutFile $tmp; `
$dir = Join-Path $env:TEMP "claude-code-orchestrator-skill"; `
if (Test-Path $dir) { Remove-Item $dir -Recurse -Force }; `
Expand-Archive $tmp -DestinationPath $dir -Force; `
& (Get-ChildItem $dir -Recurse -Filter install.ps1 | Select-Object -First 1).FullNamemacOS / Linux:
tmp="$(mktemp -d)" && \
curl -L "https://github.com/chu459/claude-code-orchestrator-skill/archive/refs/heads/main.zip" -o "$tmp/skill.zip" && \
unzip -q "$tmp/skill.zip" -d "$tmp" && \
bash "$tmp"/claude-code-orchestrator-skill-main/install/install.shAdd this to Codex config.toml:
[mcp_servers.claude-code-orchestrator]
command = "python"
args = [
"-c",
"import os,sys,runpy; home=os.environ.get('CODEX_HOME') or os.path.join(os.environ.get('USERPROFILE') or os.path.expanduser('~'), '.codex'); root=os.environ.get('CC_ORCHESTRATOR_HOME') or os.path.join(home, 'skills', 'claude-code-orchestrator', 'scripts', 'cc-orchestrator'); sys.path.insert(0, root); runpy.run_path(os.path.join(root, 'server.py'), run_name='__main__')"
]
[mcp_servers.claude-code-orchestrator.env]
PYTHONIOENCODING = "utf-8"
PYTHONUTF8 = "1"export CC_ORCHESTRATOR_HOME="$HOME/.codex/skills/claude-code-orchestrator/scripts/cc-orchestrator"
python "$CC_ORCHESTRATOR_HOME/cc_orchestrator.py" selftest
python "$CC_ORCHESTRATOR_HOME/cc_orchestrator.py" healthcheck
python "$CC_ORCHESTRATOR_HOME/cc_orchestrator.py" score-modelsHealthcheck:
python "$CC_ORCHESTRATOR_HOME/cc_orchestrator.py" healthcheckList CCSwitch profiles:
python "$CC_ORCHESTRATOR_HOME/cc_orchestrator.py" list-profilesScore local models:
python "$CC_ORCHESTRATOR_HOME/cc_orchestrator.py" score-modelsWrite strategy reports:
python "$CC_ORCHESTRATOR_HOME/cc_orchestrator.py" write-reportsWrite a CLAUDE.md worker persona into a project:
python "$CC_ORCHESTRATOR_HOME/cc_orchestrator.py" write-claude-md --cwd /path/to/project --role implementationRun a read-only architecture worker:
python "$CC_ORCHESTRATOR_HOME/cc_orchestrator.py" run "Map this repository architecture" --role architectureOpen a visible Claude Code worker window:
python "$CC_ORCHESTRATOR_HOME/cc_orchestrator.py" run-visible "Inspect this repository" --role architectureInspect the latest run:
python "$CC_ORCHESTRATOR_HOME/cc_orchestrator.py" last-runTool | Purpose |
| Check Claude Code, CCSwitch, config |
| List CCSwitch profiles |
| Pick a profile/model for a role |
| Run a Claude Code worker |
| Open a visible Claude Code worker |
| Inspect last run |
| Inspect git diff |
| Build a multi-agent workflow plan |
| Write a project |
| Score local models |
| Write score and routing reports |
Claude Code can read a project-level CLAUDE.md file.
This is extremely useful for orchestration, because Codex can set the worker's persona before launching it.
The generated CLAUDE.md tells Claude Code:
Codex is the controller, planner, reviewer, and final decision maker
Claude Code is an external worker process
the assigned role, such as
architecture,implementation, orreviewsafety rules about secrets, destructive commands, and unrelated changes
progress-reporting rules for long-running work
Create one:
python "$CC_ORCHESTRATOR_HOME/cc_orchestrator.py" write-claude-md --cwd /path/to/project --role reviewIf the project already has CLAUDE.md, the command is conservative:
default: do not overwrite
--append: append the orchestrator-managed section--force: replace after writing a timestamped backup
Through MCP, Codex can call:
cc_write_claude_mdRecommended flow:
1. Codex plans the work
2. Codex writes CLAUDE.md for the selected worker role
3. Codex launches Claude Code through this Skill
4. Claude Code follows the project persona and role rules
5. Codex reviews logs, diffs, and final outputRole | Purpose |
| Requirements, scope, non-goals, acceptance criteria |
| Repository map, likely files, implementation strategy, risks |
| Secrets, permissions, command risk, supply-chain risk |
| Validation commands, expected signals, residual risk |
| Scoped edits when write access is explicitly allowed |
| Findings ordered by severity, file references, open questions |
| Deployment, logs, rollback, runtime risk |
This project is not just “spawn more agents”.
It is:
Brain: best model for judgment
Hands: cheaper/faster worker models for execution
Ledger: every run saved
Manager: Codex controls the flowThat is why it is a cost-management harness.
flowchart TD
User["User"] --> Codex["Codex Controller"]
Codex --> Skill["Claude Code Orchestrator Skill"]
Skill --> MCP["Bundled MCP Server"]
Skill --> CLI["cc_orchestrator.py CLI"]
MCP --> Router["Role + Model Router"]
CLI --> Router
Router --> CCSwitch["CCSwitch Profiles"]
CCSwitch --> Models["Qwen / GLM / Claude-compatible Models"]
Router --> ClaudeMD["Project CLAUDE.md"]
ClaudeMD --> ClaudeCode["Claude Code Worker Process"]
Router --> ClaudeCode
ClaudeCode --> Runs["runs/<run_id> logs"]
Runs --> CodexThe default posture is intentionally conservative:
read-only planning by default
permission_mode = planunless write access is explicitly enabledallow_write=truerequired for scoped implementation workno global CCSwitch mutation
secrets are redacted from tool output and persisted logs
UTF-8-safe output on Windows
timeout output is preserved when Python exposes partial stdout/stderr
existing
CLAUDE.mdfiles are not overwritten unless--appendor--forceis used
What works today:
use
run-visibleto watch Claude Code in a real terminal windowuse
last-runto inspect the latest run metadata and tailstail the saved stdout/stderr files
Windows:
Get-Content "$env:CC_ORCHESTRATOR_HOME\runs\<run_id>\stdout.txt" -WaitmacOS / Linux:
tail -f "$CC_ORCHESTRATOR_HOME/runs/<run_id>/stdout.txt"The next serious upgrade is an event stream:
events.jsonl
cc_watch_runs
cc_run_status
terminal dashboard
Codex live pollingFull design notes:
docs/realtime-progress.mdThe goal is intentionally ambitious:
Become one of the world's top multi-agent collaboration harnesses: strong models as the brain, cheaper models as hands, Codex as controller, and MCP as the nervous system.
This is not about spectacle.
It is about bringing model cost, context cost, worker cost, and human attention cost into one auditable engineering loop.
Codex Skill
Bundled MCP Server
CCSwitch profile discovery
Local model scoring
Role-based model routing
Claude Code subprocess launching
Visible Claude Code window
UTF-8 safe Windows output
Run logs and
last-runCLAUDE.mdworker persona writerLive event stream
Terminal dashboard
Web dashboard
Cost budget policy
Parallel run coordinator
Agent result voting
Automatic cross-review
MIT.
Not affiliated with OpenAI, Anthropic, Claude, Claude Code, or CCSwitch.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/chu459/claude-code-orchestrator-skill'
If you have feedback or need assistance with the MCP directory API, please join our Discord server