mcprouter

mcprouter acts as an OpenRouter for MCP servers. It provides two main modes: a proxy server and an API server. The proxy server exposes an SSE endpoint that MCP clients can subscribe to and route MCP traffic through. The API server offers tooling endpoints (for example, a list-tools endpoint) to discover and interact with available MCP tools. To use it, first prepare your environment by copying the example TOML configuration to a working .env.toml and customizing mcp_server_commands.fetch (as indicated in the README). Start the proxy server to enable the Proxy URL consumption from MCP clients (for example, http://localhost:8025/sse/fetch). Then start the API server to access management endpoints like the tools list via curl (e.g., curl -X POST http://127.0.0.1:8027/v1/list-tools). Ensure the fetch command is enabled in your .env.toml so the proxy/api can surface the appropriate tool commands.

Prerequisites:

• Go installed (go version 1.18+ recommended)
• A Unix-like environment (Linux/macOS) or Windows with a compatible shell

Installation steps:

1. Obtain the source code (clone the repository or download the release).
2. In the project root, copy the example environment configuration: cp .env.example.toml .env.toml
3. Edit .env.toml to configure mcp_server_commands.fetch and other needed settings as described in the README.
4. Start the proxy server: go run main.go proxy
5. In another terminal, start the API server: go run main.go api
6. Verify operation:
   • Proxy: open the Proxy URL provided (e.g., http://localhost:8025/sse/fetch) from your MCP client.
   • API: test endpoints like curl -X POST http://127.0.0.1:8027/v1/list-tools -H 'Content-Type: application/json' -H 'Authorization: Bearer fetch'

Tips and common considerations:

• Ensure .env.toml is present and correctly configured before starting the servers; the fetch command flag mcp_server_commands.fetch must be enabled for the tools to be surfaced.
• The proxy URL is intended to be consumed by MCP clients as an SSE feed; ensure network accessibility to http://localhost:8025/sse/fetch from clients.
• If you encounter port conflicts, adjust the ports in your environment and reflect changes where needed in your client configuration.
• When restarting servers after config changes, give the process a moment to rebind and re-read the environment configuration.
• The API server exposes tooling endpoints; use curl or HTTP clients to discover available tools and their usage.