🌱 mcp-origin

Name: 🌱 mcp-origin
Author: dstotijn

@dstotijn

Repository

About 🌱 mcp-origin

MCP server that manages MCP servers

#mcp #mcp-server #management

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

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

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

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.