
Mcp Gateway
io.github.rupinder2Published by GitHub account rupinder2v0.1.1Updated Oct 24, 2026
Aggregates tools from multiple MCP servers with unified BM25/regex search and deferred loading.
Overview
A local MCP gateway that connects to several downstream MCP servers, indexes their tools, and lets an assistant search and call them through one endpoint.
- What you can do
- Search across all registered downstream servers' tools with BM25 natural-language ranking or regex patterns
- Discover and index the tools exposed by a registered downstream server
- Call a namespaced downstream tool (server_name__tool_name) with arguments, optionally overriding its auth header
- Register downstream servers via a JSON config file, using stdio or HTTP transports
- Cache tool definitions in memory or Redis to keep context usage low
- When to use it
- Useful when you run many MCP servers and want one connection instead of adding each separately, or when the combined tool list would otherwise crowd the assistant's context window. It suits setups that need deferred tool loading and a single searchable index over several servers.
- Requirements
- Runs locally as a Python package (pip install mcp-orchestrator) over stdio, or over HTTP with ORCHESTRATOR_TRANSPORT and ORCHESTRATOR_PORT. Needs a server_config.json listing downstream servers, given by SERVER_CONFIG_PATH. STORAGE_BACKEND selects memory or redis; REDIS_URL is required only for the redis backend. Downstream servers may need their own tokens or commands.
Installation
In SourceWeft
- Open Mcp Gateway 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.1LatestSep 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