McpOrchestrator
About
An MCP server... for your other MCP servers.
Details
- Author
- byggarepop
- Categories
- Developer Tools
Jump to
Setup
Install McpOrchestrator in your MCP client (Claude Desktop, Cursor, Windsurf, and others).
Repository: https://github.com/byggarepop/dotnet-mcp-orchestrator
Follow the installation instructions in the repository README, then restart your MCP client.
McpOrchestrator — a .NET-native MCP orchestrator
Every MCP server you connect costs context before the agent does anything — its tool manifests sit in the prompt on every turn.McpOrchestrator puts one server between your agent and all the others and loads downstream tool manifestson demand, so the agent's always-on context stays flat no matter how many servers you add. The agent sees three meta-tools —list_capabilities→discover_tools→route— and the orchestrator is apure relay: it forwards exactly what the agent sends, never interpreting it. It can also serveAgent Skillswith the same on-demand discipline.
https://github.com/user-attachments/assets/741c1afa-4bef-4870-9b84-e2c245b8117e
Against a real workplace MCP setup, measured with the Copilot CLI's/usage:
The savings scale with the number of servers. Measure your own setup first — one command, nothing installed, not a single file changed (needs the .NET SDK):
cd ~/my-project # a folder with a .mcp.json / .vscode/mcp.json / Cursor config dotnet tool execute McpOrchestrator profile
From an existing MCP setup,cdto the folder holding your host config (.mcp.json,.vscode/mcp.json, or a Cursor config) and run:
dotnet tool execute McpOrchestrator --yes init # dnx McpOrchestrator --yes init works too
It lifts your stdio servers into a generatedorchestrator.config.json, backs up the host config, and rewrites it to launch only the orchestrator. The generated catalog looks like this — one entry per downstream server:
{ "capabilities": [ { "name": "files", "summary": "Read and search files under the project root.", // auto-generated "transport": "stdio", "command": "npx", "args": ["-y", "@modelcontextprotocol/server-filesystem", "C:/projects"] } // …one entry per server init found ] }
Thesummaryline is what the agent routes on — refine any that read poorly. Restart your MCP host and you're done: the agent discovers everything on its own throughlist_capabilities→discover_tools→route, and every later edit to this filehot-reloadswithout a restart.
A skill is a folder with aSKILL.md— instructions the agent discovers and follows by itself when a task matches. Create one:
my-skills/ └── release-notes/ └── SKILL.md
--- name: release-notes description: Writes user-facing release notes from a git commit range. Use when asked for release notes or a changelog entry. --- 1. Collect the commits since the last release tag. 2. Group by user impact; drop internal-only changes. 3. One sentence per change, present tense.
Point the orchestrator at the folder inorchestrator.config.json:
"skills": { "sources": [{ "id": "local", "type": "directory", "path": "C:/my-skills" }] }
Save — it hot-reloads. The agent now sees the skill's name + one-line description vialist_skillsand loads the full instructions only when a task calls for it. Skills can also come from a shared git repo or an HTTP index, with allow/deny lists and integrity pinning — seedocs/skills.md.
Note: these skills arefor the agent only— the model discovers and follows them through tools. They do not become host-native skills (no/skillslisting or slash command in Claude Code, no IDE skill picker entry).
Everything else lives inMcpOrchestrator/README.mdanddocs/:
- How it works & the three tools— architecture and token scaling
- Profiling token economics— theprofilecommand in depth, trace mode, CI gating
- CLI reference— every command and flag: the server,init, andprofile, plus all environment variables
- Manual setup— the two config filesinitgenerates, written by hand
- Configuration reference— every field, placeholders,proactive capabilities,hot reload,central (team) configuration
- Agent Skills— sources (directory/git/HTTP), governance, delivery modes, how it works
- Packaging & Native AOT— install as a .NET tool or a self-contained binary fromReleases
- How it compares— vs. mcp-aggregator and gateways, and whennotto use this
- Troubleshooting
This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.
Create crafted UI components inspired by the best 21st.dev design engineers.
Bring agent evaluations, observability, and synthetic test set generation directly into your IDE for free with Galileo's new MCP server
An MCP server to help AI assistants to answer questions and generate AccelByte Extend SDK code more effectively .
MCP server for AI Diagram Maker — generate beautiful software engineering diagrams directly inside Cursor, Claude Desktop, Claude Code, or any MCP-compatible AI agent
ALAPI MCP Tools,Call hundreds of API interfaces via MCP
AI-powered SVG animation generator that transforms static files into animated SVG components using the Allyson platform
MCP server that gives AI assistants on-demand access to 1,500+ amCharts docs, ~300 code examples, and 1000+ class API references.
APIMatic MCP Server is used to validate OpenAPI specifications using APIMatic. The server processes OpenAPI files and returns validation summaries by leveraging APIMatic’s API.
One shared context layer for AI agents and humans — live API specs, DB schemas, and versioned contracts across repos so every agent and teammate works from the same source of truth.
Build and deploy full-stack Next.js apps with 98 tools for React, AWS, and MongoDB
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
