MCP Origin

Proxy multiple MCP servers through a single configurable endpoint and auto-discover tools across connected servers.

javascript

4

GitHub Stars

javascript

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "dstotijn-mcp-origin": {
      "command": "npx",
      "args": [
        "binrun",
        "github.com/dstotijn/mcp-origin@latest"
      ]
    }
  }
}

You can manage multiple MCP servers through a single, centralized MCP proxy. This server-oriented approach simplifies connecting to diverse MCP endpoints, routing tool calls consistently, and discovering tools automatically from connected MCP servers.

How to use

You execute the MCP proxy to connect to one or more MCP servers and then call tools using a prefixed naming scheme. When you install a server, its tools become available with the prefix of the server’s identifier, enabling you to call tools as if they were local. This makes it easy to manage several MCP endpoints from one place and route calls to the correct server without changing your client logic.

How to install

Prerequisites: you need Node.js and npm (or a compatible runtime that can run npm-based commands). Ensure you have access to the internet to fetch MCP-origin and its dependencies.

Start the MCP proxy with stdio transport by running the following command.

npx binrun github.com/dstotijn/mcp-origin@latest

If you want to explicitly connect to a specific MCP server using a configuration, you can use the install tool with a JSON configuration block. Use the exact snippet shown here to specify the server you want to install and connect to. This config runs the MCP server as a stdio process.

{
  "id": "foobar",                          // Unique identifier for the MCP server
  "type": "stdio",                         // Connection type (currently only "stdio" is supported)
  "command": "npx",                        // Command to execute to start the MCP server
  "args": ["-y", "@acme/mcp-foobar", ...]  // Arguments to pass to the command
}

If you later want to remove a server from the configuration and disconnect, you can use the uninstall tool with the following parameter.

{
  "id": "foobar" // The ID of the server to uninstall
}

Additional notes

You can refresh the list of tools from connected MCP servers at any time. The refresh command accepts an optional server_id to target a single server.

{
  "server_id": "foobar" // Optional: Only refresh tools for this specific server
}

Transport options and configuration

The proxy supports multiple transport options. By default, stdio transport is enabled, and HTTP listening is available if you choose to expose an HTTP endpoint. You can customize the HTTP address, enable or disable SSE for proxied MCP servers, and specify the path to the configuration file.

Command-line flags you can use include specifying the HTTP listen address, enabling or disabling stdio and SSE transports, and providing the path to the configuration file.

--http address
--stdio
--sse
--config path/to/config.json

Available tools

search_mcp_servers

Search for available MCP servers that can be installed. This tool isn’t implemented yet.

install_mcp_server

Install and connect to an MCP server. Requires id, type, command, and args to start the server.

uninstall_mcp_server

Remove an MCP server from the configuration and disconnect from it.

refresh_tools

Refresh the list of tools from connected MCP servers. Can target a specific server with server_id.