MCP Server Copilot
Click on "Deploy 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., "@MCP Server Copilot Route my request to find the latest stock prices."
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.
MCP Server Copilot
A meta Model Context Protocol (MCP) server that seamlessly scales LLMs to 1000+ MCP servers through automatic routing without expose all servers and tools to LLMs directly.
Components
Tools
router-servers: Route user query to appropriate MCP servers.query(string, required): User's query to find relevant servers.top_k(integer, optional): Maximum number of servers to return (default: 5).
route-tools: Route user query to appropriate MCP tools across all servers.query(string, required): User's query to find relevant tools.top_k(integer, optional): Maximum number of tools to return (default: 5).
execute-tool: Execute a specific tool on a specific server based on previous routing results.server_name(string, required): Name of the server hosting the tool.tool_name(string, required): Name of the tool to execute.params(object, optional): Parameters to pass to the tool, as a key-value dictionary (default: null or empty object).
Related MCP server: Magg
Installation
Using uv (recommended)
When using uv no specific installation is needed. We will
use uvx to directly run mcp-server-copilot.
Using PIP
Alternatively you can install mcp-server-copilot via pip:
pip install mcp-server-copilotAfter installation, you can run it as a script using:
python -m mcp_server_copilotConfiguration
Copy config/config.sample.json to ~/.config/mcp-server-copilot
Add to your MCP Client settings:
{
"mcpServers": {
"copilot": {
"command": "uvx",
"args": ["mcp-server-copilot", "--config", "~/.config/mcp-server-copilot/config.json"]
}
}
}{
"mcpServers": {
"copilot": {
"command": "python",
"args": ["-m", "mcp_server_copilot", "--config", "~/.config/mcp-server-copilot/config.json"]
}
}
}TODOs
Add Dockerfile
Tune prompt and add show cases
Manage Servers more easily
Add Semantic Routing
Add Planning Capabilities
Resources & Prompts
Available Tools
3 toolsexecute-toolA
Execute a specific tool on a specific server based on previous routing results. Use this after you've identified the appropriate server and tool using the routing tools. This actually performs the requested operation.
Inputs: server_name (required), tool_name (required), params (required).
router-serversB
Route user query to appropriate servers. Use this when you need to find suitable servers that can handle the user's query. This should be your first step when processing a new query to determine which specialized servers are most relevant.
Inputs: query (required), top_k (required).
route-toolsB
Route user query to appropriate tools across all servers. Use this when you need to find specific tools that can address the user's request, regardless of which server hosts them. This is helpful when you know the task type but not which server handles it.
Inputs: query (required), top_k (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool has a distinctly different purpose: one for finding servers, one for finding tools, and one for executing a tool. No overlap or ambiguity.
All names use lowercase with hyphens, but 'router-servers' uses a noun (router) while 'route-tools' uses a verb (route), introducing minor inconsistency.
Three tools is well-scoped for a routing/coordinating server, covering the essential functions without being too few or excessive.
Covers the core routing and execution workflow. A minor gap is the lack of a direct listing tool, but the routing tools subsume that functionality.
Maintenance
Related MCP Connectors
MCP server for building and testing AI agents with multi-model experimentation and insights.
Single-connection meta-router indexing 500+ MCP servers & A2A tools with 85% token compression and
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA proxy server that unifies multiple MCP servers, enabling seamless tool, prompt, and resource management via the MetaMCP App.67 npm155Apache 2.0
- AlicenseBqualityCmaintenanceA meta-MCP server that manages and aggregates other MCP servers, enabling LLMs to dynamically extend their own capabilities by searching for, adding, and configuring tool servers.16242 PyPI143AGPL 3.0
- FlicenseCqualityDmaintenanceAn MCP server that routes LLM requests across multiple providers and orchestrates other MCP servers, with a focus on local privacy for embeddings and memory.283-
- FlicenseNot gradedqualityAmaintenanceA meta-MCP server that manages, aggregates, and proxies other MCP servers, letting LLMs search for, add, configure, enable, disable, and bundle servers at runtime. Tools from connected servers are exposed under unified prefixes, with persistent configuration and health monitoring.-