McpOrchestrator
Single MCP server that routes an agent to many others, loading tool lists on demand
- Pricing
- Open source
- Platforms
- CLI
- Runs
- Locally
- Version
- 0.7.6
- Listing updated
- today
Similar MCP servers
About McpOrchestrator
McpOrchestrator is an open-source MCP server for developer tools. It runs locally on your machine and is started by your AI client.
Every MCP server you connect puts its tool manifests into the prompt on every turn. McpOrchestrator is a .NET-built relay that sits between the agent and all those servers, so the agent only ever sees three meta-tools, list_capabilities, discover_tools and route, and downstream manifests load only when needed. It forwards what the agent sends without interpreting it.
The README reports one measurement on a real workplace setup using the Copilot CLI: 17,900 tokens in context with the MCP connected directly versus 1,400 behind the orchestrator, roughly 13 times less. A profile command measures your own setup without changing any files, and an init command lifts your existing stdio servers from .mcp.json, .vscode/mcp.json or a Cursor config into a generated orchestrator.config.json, backing up the host config.
It can also serve Agent Skills, folders containing a SKILL.md, from local directories, a git repository or an HTTP index, with the agent calling list_skills and loading full instructions only when a task needs them. Config edits hot-reload without a restart. It is distributed as a NuGet .NET tool and licensed MIT.
Install
Run in a terminal
claude mcp add dotnet-mcp-orchestrator -- dnx McpOrchestrator --yesAdd to claude_desktop_config.json
{
"mcpServers": {
"dotnet-mcp-orchestrator": {
"command": "dnx",
"args": [
"McpOrchestrator",
"--yes"
]
}
}
}Add to ~/.cursor/mcp.json
{
"mcpServers": {
"dotnet-mcp-orchestrator": {
"command": "dnx",
"args": [
"McpOrchestrator",
"--yes"
]
}
}
}Add to .vscode/mcp.json
{
"servers": {
"dotnet-mcp-orchestrator": {
"type": "stdio",
"command": "dnx",
"args": [
"McpOrchestrator",
"--yes"
]
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"dotnet-mcp-orchestrator": {
"command": "dnx",
"args": [
"McpOrchestrator",
"--yes"
]
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"dotnet-mcp-orchestrator": {
"command": "dnx",
"args": [
"McpOrchestrator",
"--yes"
]
}
}
}Using several servers? Build one config file with the MCP config generator.
Tools this server provides (4)
Taken from the project documentation; the running server may differ.
- list_capabilities
- Lists the downstream capabilities available through the orchestrator
- discover_tools
- Loads tool manifests for a chosen capability on demand
- route
- Forwards a tool call to the downstream server
- list_skills
- Lists available Agent Skills by name and one-line description
What it does
- Progressive discovery
- Exposes three meta-tools so tool manifests load only when the agent asks.
- Config migration
- The init command moves existing stdio servers behind the orchestrator and backs up the host config.
- Token profiling
- A profile command estimates the context cost of your current setup without changing it.
- Agent Skills serving
- Serves SKILL.md folders from directories, git or HTTP with on-demand loading.
- Hot reload
- Edits to the catalogue file apply without restarting the host.
- Pure relay
- Forwards requests unchanged rather than interpreting them.
Good for
- Cut the context cost of running many MCP servers at once
- Migrate a Claude Code, VS Code or Cursor MCP config behind one entry
- Measure how many tokens your MCP setup uses before changing it
- Share a set of agent skills from a git repository across a team
Pricing
Open source
MIT licence
McpOrchestrator FAQ
How much context does it save?
The README reports 17,900 tokens dropping to 1,400 on one real setup, about 13 times fewer, and says savings grow with the number of servers.
What tools does the agent see?
Three meta-tools: list_capabilities, discover_tools and route.
Does it work with remote MCP servers?
The init command lifts stdio servers into the catalogue; the README's quick start describes stdio configuration.
What does it need to run?
The .NET SDK; it is installed as a NuGet tool or run with dotnet tool execute.
Is McpOrchestrator free?
Yes. McpOrchestrator is open source, so you can use and self-host it for free.
How do I add McpOrchestrator to Claude Code?
Run this command in your terminal: claude mcp add dotnet-mcp-orchestrator -- dnx McpOrchestrator --yes
What are the best alternatives to McpOrchestrator?
The closest alternatives to McpOrchestrator are REA, Context7, Chrome DevTools MCP, Codebase Memory and GitHub.
Where this comes from
- Description: written from the project's README.
- Install steps: from the official MCP Registry entry.


