mcprouter MCP Server
proxy for remote mcp servers.
Quick Start
- Get Remote MCP Server Key
go to MCP.so, select a hosting server,
click Connect to generate your exclusive server_key.
Power your agent
Install from the publisher. Not a PlugMCP endpoint.
Host a copy with our keys and logs.
No packaged release in the registry yet. Follow the repository README.
Remote URL or a command on your machine? How the two installs differ
Run on PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchFrom the publisher
proxy for remote mcp servers.
go to MCP.so, select a hosting server,
click Connect to generate your exclusive server_key.
mcprouter for remote mcp servers
take Claude Desktop for example:
{
"mcpServers": {
"fetch": {
"command": "npx",
"args": ["-y", "mcprouter"],
"env": {
"SERVER_KEY": "xxx"
}
}
}
}
Install dependencies:
npm install
Build the server:
npm run build
For development with auto-rebuild:
npm run watch
To use with Claude Desktop, add the server config:
On MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json
On Windows: %APPDATA%/Claude/claude_desktop_config.json
{
"mcpServers": {
"mcprouter": {
"command": "/path/to/mcprouter/build/index.js"
}
}
}
Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the MCP Inspector, which is available as a package script:
npm run inspector
The Inspector will provide a URL to access debugging tools in your browser.
mcprouter for remote mcp servers
Tools
No tool list yet. Remote servers get one after the first health check.
FAQ
Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
No required environment variable is listed on this record.
MCP Server Router runs locally over stdio.
Last checked 2026-10-28. mcprouter for remote mcp servers