MCPHub Server

A unified hub for centrally managing and dynamically orchestrating multiple MCP servers/APIs into separate endpoints with flexible routing strategies

typescript

1.9k

GitHub Stars

typescript

Language

4 months ago

First Indexed

3 weeks 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": {
    "samanhappy-mcphub": {
      "command": "npx",
      "args": [
        "-y",
        "time-mcp"
      ]
    }
  }
}

MCPHub is a centralized platform that organizes multiple MCP servers behind flexible streaming endpoints, enabling you to manage, route, and scale your MCP deployments with ease. It supports accessing all servers, specific groups, or individual servers via HTTP/SSE, with optional smart routing, authentication, and containerized deployment for production use.

How to use

You can connect MCP clients to MCPHub to access all MCP servers or target specific groups or servers. Use the smart routing endpoints to discover the best available server for your task, or route directly to a named server or group. Authentication protects endpoints by default, and you can adjust authentication in trusted environments.

How to install

Prerequisites: install Node.js (recommended LTS) and an active container runtime if you plan to run via Docker. You will also use a package manager to install dependencies.

Create a configuration file for MCPHub to define your MCP servers.
Run MCPHub using Docker or a local development setup according to your preference.

Configuration

Create a file named mcp_settings.json to list your MCP servers. You can define local (stdio) MCP servers using commands such as npx or uvx that start the specific MCP services you want MCPHub to manage.

{
  "mcpServers": {
    "time": {
      "command": "npx",
      "args": ["-y", "time-mcp"]
    },
    "fetch": {
      "command": "uvx",
      "args": ["mcp-server-fetch"]
    }
  }
}

Security and access

MCP endpoints require authentication by default to prevent accidental exposure. To allow unauthenticated MCP access, disable the Bearer Authentication setting in the Keys section. Skip Authentication only affects dashboard login. Use these options only in trusted environments.

Examples and quick references

To connect AI clients, use the following endpoints to access MCPHub routed servers:

http://localhost:3000/mcp           # All servers
http://localhost:3000/mcp/{group}   # Specific group
http://localhost:3000/mcp/{server}  # Specific server
http://localhost:3000/mcp/$smart    # Smart routing
http://localhost:3000/mcp/$smart/{group}  # Smart routing within group

Notes on deployment

MCPHub supports Docker for quick deployment. You can mount your configuration file and data directory to the container for persistent configuration and state.

Available tools

central_dashboard

Unified dashboard to monitor and control MCP servers.

http_sse_routing

Routing access to all servers, groups, or individuals via HTTP/SSE.

smart_routing

AI-powered tool discovery using vector semantic search.

oauth2

OAuth 2.0 authentication for client and server modes.

database_mode

Store configuration in PostgreSQL for production.

docker_support

Docker-ready deployment for quick setup.