🌱 mcp-origin

What is mcp-origin?

mcp-origin is an MCP server that acts as a proxy, allowing you to connect to and manage multiple MCP servers through a single interface. It stores server configurations in a simple JSON file, automatically discovers tools from connected servers, and proxies tool calls using a consistent naming scheme.

How to use mcp-origin?

Run the server via stdio using npx binrun github.com/dstotijn/mcp-origin@latest. It provides built-in tools for installing, uninstalling, and refreshing MCP servers. Tools from connected servers are available with the prefix serverID. (e.g., foobar.search). Command-line options include --http, --stdio, --sse, and --config.

Key features of mcp-origin

• Connect to multiple MCP servers via a single proxy
• Proxy tool calls with a consistent naming scheme
• Store server configurations in a JSON file
• Automatic tool discovery and registration
• Built-in tools to install, uninstall, and refresh servers

Use cases of mcp-origin

• Manage multiple MCP servers from one client application
• Dynamically install and uninstall MCP servers at runtime
• Refresh the tool list from connected servers without restarting
• Proxy tools from different servers under a unified namespace

FAQ from mcp-origin

What is mcp-origin?

mcp-origin is an MCP server that acts as a proxy to connect to and manage multiple MCP servers through a single interface, with automatic tool discovery and a consistent naming scheme.

How do I install and run mcp-origin?

Use the command npx binrun github.com/dstotijn/mcp-origin@latest over stdio. It supports optional HTTP, SSE, and custom config file paths.

What connection types are supported for proxied servers?

Currently only stdio is supported for connecting to proxied MCP servers.

How are tools from connected servers accessed?

Tools from connected servers are prefixed with the server’s unique ID followed by a dot (e.g., foobar.search).

Is the search_mcp_servers tool implemented?

No, it is not implemented yet. The README marks it as a TODO.