
Mcp Orchestrator
io.github.rupinder2Published by GitHub account rupinder2v0.1.2Updated Oct 25, 2026
Aggregates tools from multiple MCP servers with unified BM25/regex search and deferred loading.
Overview
A local hub that connects to several MCP servers, indexes their tools, and lets an assistant search for and call them through one endpoint.
- What you can do
- Search indexed tools across all registered downstream servers with BM25 relevance ranking or regex patterns, with deferred loading to keep context small. Discover and index the tools of a registered downstream server. Call a downstream tool by its namespaced name, optionally overriding the configured auth header. Register downstream servers through a JSON config file, with stdio or HTTP transport and in-memory or Redis caching of tool definitions.
- When to use it
- Useful when you connect to many MCP servers and want one entry point whose tool list stays small, with search used to pull in only the tools a task needs. Also handy for routing calls to several downstream servers from a single configuration file.
- Requirements
- Python package installed locally (pip install mcp-orchestrator) and run as a stdio or HTTP process. A server_config.json listing downstream servers, located via SERVER_CONFIG_PATH. Optional Redis via REDIS_URL when STORAGE_BACKEND=redis; ORCHESTRATOR_PORT for HTTP transport. Network access to the downstream servers.
Installation
In SourceWeft
- Open Mcp Orchestrator in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
MCP Orchestrator
[PyPI Version] [Python Version] [License: MIT] [Tests] [Contributions Welcome]
A central hub that connects to multiple downstream MCP servers, aggregates their tools, and provides unified access with powerful tool search capabilities.
Built around deferred tool loading — search across all your servers without blowing Claude's context window.
Features
- Config-based Server Registration: Add downstream MCP servers via JSON config file
- Tool Namespacing: Automatic
server_name__tool_nameformat - Tool Search: Unified BM25/regex search with deferred loading support
- Flexible Authentication: Static saved headers or token forwarding
- Multiple Transports: stdio or HTTP
- Tool Definition Caching: Cached definitions, raw result passthrough
- Storage Backends: In-memory (development) or Redis (production)
Quick Start
Installation
Running the MCP Server
HTTP Transport:
This starts the server on http://localhost:8080/mcp with CORS enabled.
Configuring Servers
Add downstream MCP servers in server_config.json:
Searching for Tools
The orchestrator provides unified tool search (BM25 by default, regex optional):
Architecture
Configuration
Environment Variables
Claude Desktop Integration
Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json):
MCP Tools
tool_search
Search for tools using BM25 relevance ranking or regex pattern matching.
discover_tools
Discover tools from a registered downstream server.
call_remote_tool
Call a tool directly on a downstream MCP server.
Tool Search Results
The search tools return results in the format expected by Claude's tool search system:
Testing
Run the test suite:
Run with coverage:
Project Structure
License
MIT License
Contributing
Contributions are welcome! Please see CONTRIBUTING.md for guidelines.
Source: README.md at commit b44912b
Tools
0Version history
1- v0.1.2LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts