proxy for remote mcp servers.
proxy for remote mcp servers. Exposed over MCP by the mcprouter mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
On MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json On Windows: %APPDATA%/Claude/claude_desktop_config.json
Everything the assistant can do here goes through one of these:
Debugging — Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the [MCPYou will need one environment variable: SERVER_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Mcprouter's toolset — Debugging — is a fair guide to whether it matches your workflow. It is maintained by idoubi; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Mcprouter's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Debugging | Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the [MCP Inspector](https://github.com/modelcontextprotocol/inspector), which is available as a package script: |
{
"mcpServers": {
"fetch": {
"command": "npx",
"args": ["-y", "mcprouter"],
"env": {
"SERVER_KEY": "xxx"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| SERVER_KEY | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.