MCP-Origin: Centralized Management & Performance Optimization

mcp-origin: The centralized MCP server hub that streamlines management, optimizes performance, and unifies control across your entire server ecosystem.

Visit Repository

✨ Developer Tools

4.5(141 reviews)

211 saves

98 comments

86% of users reported increased productivity after just one week

About MCP-Origin

What is MCP-Origin: Centralized Management & Performance Optimization?

MCP-Origin acts as a centralized hub for managing multiple MCP servers through a unified interface. By consolidating configuration, discovery, and tool execution, it simplifies the orchestration of distributed microservices while enhancing performance through smart proxy routing. Think of it as the Swiss Army knife for MCP ecosystems—streamlining complexity without sacrificing flexibility.

How to Use MCP-Origin: Centralized Management & Performance Optimization?

Getting Started

Launch the proxy with:

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

Customize behavior via command-line flags like --http for HTTP endpoints or --config to override the default JSON configuration path.

Managing Servers

Install servers using install_mcp_server with parameters defining server ID, command, and arguments
Uninstall with uninstall_mcp_server specifying the server ID
Refresh tool listings globally or per-server using refresh_tools

Need to discover available servers first? The search_mcp_servers tool is coming soon!

MCP-Origin Features

Key Features of MCP-Origin: Centralized Management & Performance Optimization?

Intelligent Proxy Routing

Automatically routes requests to the correct server using standardized naming conventions, eliminating manual lookup hassles.

Unified Configuration

All server configurations stored in a single human-readable JSON file for easy editing and version control.

Dynamic Discovery

Automatically detects and registers tools from connected servers, keeping your environment up-to-date without manual intervention.

Multi-Transport Support

Currently supports stdio transport with SSE (Server-Sent Events) planned for real-time updates - see roadmap below.

Use Cases of MCP-Origin: Centralized Management & Performance Optimization?

Multi-Service Environments: Manage 10+ MCP instances across microservices with a single config
CI/CD Pipelines: Seamlessly integrate distributed tools into automated workflows
Development Workflows: Rapidly spin up/down test servers while maintaining consistent tool access
Legacy Modernization: Bridge new tooling with existing stdio-based systems

MCP-Origin FAQ

FAQ from MCP-Origin: Centralized Management & Performance Optimization?

Q: How do I specify server parameters?

Use JSON-formatted parameters during installation, including required fields like id, type, command, and args.

Q: Can I call tools from multiple servers?

Absolutely! Tools are namespaced with their server ID (e.g., foobar.search), making conflicts impossible even with identical tool names.

Q: Where's the configuration stored by default?

In ~/.config/mcp-origin/mcp_origin_config.json - override this with the --config flag.

Q: What's next for MCP-Origin?

External registry service for discovery (planned)
SSE support for real-time tool updates (planned)

Content

🌱 mcp-origin

One MCP server to rule (well... manage) them all.

Features

Connect to multiple MCP servers via a single MCP proxy
Proxy tool calls to the appropriate server using a consistent naming scheme
Store server configurations in a simple JSON configuration file
Automatic tool discovery and registration from connected MCP servers

TODO

Use external MCP registry service for discovery
Support SSE for proxied MCP servers

Usage

Use the following command and args for MCP over stdio:

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

Available Tools

mcp-origin provides the following built-in tools:

`search_mcp_servers`

Search for available MCP servers that can be installed.

[!IMPORTANT] This tool isn't implemented yet.

`install_mcp_server`

Install and connect to an MCP server. This tool requires the following parameters:

{
  "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
}

`uninstall_mcp_server`

Remove an MCP server from the configuration and disconnect from it. This tool requires the following parameter:

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

`refresh_tools`

Refresh the list of tools from connected MCP servers. This tool accepts an optional parameter:

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

Proxied Tools

All tools from connected MCP servers are available with the prefix serverID., where serverID is the unique identifier for the MCP server.

For example, if you have a server installed with ID foobar that provides a tool called search, the tool will be listed and is callable as foobar.search.

Command-line Options

--http: HTTP listen address (default: ":8080")
--stdio: Enable stdio transport (default: true)
--sse: Enable SSE transport (default: false)
--config: Path to configuration file (default: "~/.config/mcp-origin/mcp_origin_config.json")

License

Apache-2.0 license