MCPHub logo

MCPHub

Self-hosted gateway for routing, securing, and monitoring multiple local or remote MCP servers through unified endpoints.

Install MCPHub

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "mcphub-2": {
      "command": "npx",
      "args": [
        "-y",
        "time-mcp"
      ],
      "env": {
        "ADMIN_PASSWORD": "YOUR_VALUE_HERE",
        "DISABLE_WEB": "YOUR_VALUE_HERE",
        "SMART_ROUTING_PATH": "YOUR_VALUE_HERE",
        "BASE_PATH": "YOUR_VALUE_HERE",
        "MCPHUB_CREDENTIAL_ENCRYPTION_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

MCPHub MCP server provides a centralized gateway between AI clients and multiple local or remote MCP servers. It exposes combined, grouped, individual, or smart-routed MCP endpoints over supported transports, while managing authentication, credentials, visibility, logs, and health checks. A browser dashboard handles configuration and runtime operations, with headless operation available through an environment setting. Reach for MCPHub when clients need one stable connection to a changing collection of MCP servers.

Use cases

  • Aggregate local and remote MCP servers behind one client connection
  • Route requests to selected server groups or individual servers
  • Give users isolated credentials for shared MCP servers
  • Monitor MCP request activity and connection health
  • Manage MCP server configuration from a browser dashboard

Key features

  • Unified MCP gateway with smart routing
  • stdio, SSE, and Streamable HTTP connectivity
  • OAuth 2.0, bearer authentication, and access controls
  • Per-user encrypted credentials and isolated stdio runtimes
  • Dashboard, logs, health checks, and hot-swappable configuration
  • Docker and PostgreSQL deployment modes

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

26/26 checks healthy over the last 17d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 2h ago via OSV.dev · time-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars2.6kStargazers on the source repository.
npm downloads6.2kPackage downloads in the last 30 days.
Last commitTodayMost recent push to the default branch.
Directory activity10 viewsConfig copies, upvotes, and views on AllMCPs.

How MCPHub works

What MCPHub does

MCPHub centralizes access to multiple MCP servers behind one gateway. It can connect to local and remote servers, then expose their capabilities through stable endpoints for all connected servers, selected groups, individual servers, or semantic smart-routing paths. Server aliases help direct clients to particular targets without changing the underlying server setup.

The gateway also provides operational controls around the connected servers. Administrators can organize servers into groups, control whether users can see particular servers or groups, and manage exposure of tools, prompts, and resources. Logs show tool-call activity, request status, latency, and server output, while health checks provide a central view of connection status.

How it works

MCPHub accepts connections from MCP-compatible clients and forwards requests to configured upstream servers. Supported upstream transports include stdio, SSE, and Streamable HTTP, allowing one deployment to combine local processes with remote services. Clients can use routes for the complete server collection, a group, a single server, or smart routing. Smart routing uses vector-based semantic search to select relevant tools.

Configuration can be changed while the gateway is running, so servers may be added, removed, or updated without downtime. MCPHub can also proxy interactive MCP Apps on single-server routes and compress large text results before returning them to clients.

Authentication supports OAuth 2.0 and bearer keys. OAuth can operate in both client and server roles, while per-user credentials allow personal keys to be bound to a shared server. Credentials are encrypted, and isolated stdio runtimes are used for per-user operation.

Setup and configuration

Docker is the recommended installation method. A basic deployment publishes port 3000 and mounts a host data directory at /app/data:

Terminal
docker run -p 3000:3000 -v ./data:/app/data samanhappy/mcphub

The dashboard is available at http://localhost:3000. On the first launch, MCPHub uses ADMIN_PASSWORD if set; otherwise, it generates a password and prints it in the server logs. Keep the data directory mounted so settings, users, and credential bindings persist across container replacement.

Before the first launch, upstream servers can be declared in data/mcp_settings.json. Each entry can specify a command and arguments for a local MCP process, with configuration also supporting options such as OAuth and environment variables. Servers can subsequently be managed from the dashboard or by editing the settings file and restarting the gateway.

The default Docker image includes Node.js, pnpm, Python, uv/uvx, Git, and build tools. The latest-full image additionally includes Rust tooling, Docker Engine, and Playwright browsers for workloads that need them. Running from source requires Node.js 22 or newer and pnpm 10.12.4.

Tools and capabilities

  • Unified MCP routes for all servers, groups, individual servers, and smart routing
  • Connections over stdio, SSE, and Streamable HTTP
  • Server aliases, grouping, visibility controls, and hot-swappable configuration
  • OAuth 2.0, bearer authentication, scoped credentials, and per-user credential bindings
  • Browser dashboard plus headless backend/API operation
  • Tool-call logs, latency and status tracking, server logs, and health monitoring
  • PostgreSQL database mode and multi-replica deployment with session affinity
  • MCP Apps proxying and large text-result compression

Limitations and notes

MCP endpoints require authentication by default. Unauthenticated access can be enabled by disabling bearer authentication, but this is intended only for trusted environments. The dashboard's skip-authentication option is separate and does not remove MCP endpoint authentication.

Database mode requires a persistent MCPHUB_CREDENTIAL_ENCRYPTION_KEY, or an existing key file. Losing the encryption key prevents recovery of encrypted credentials even when a PostgreSQL backup is available. Multi-replica deployments use PostgreSQL configuration together with explicit session affinity and reconnect boundaries.

The custom smart-routing path must not conflict with an existing server name, group name, or group ID. The default $smart route remains available even when a custom segment is configured.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about MCPHub

MCPHub is an MCP server that connects AI clients to local and remote MCP servers through a unified gateway. Its main tools include routes for all servers, groups, individual servers, and smart routing, along with authentication, credential management, logs, health monitoring, and browser-based administration.

Install MCPHub with Docker by publishing port 3000 and mounting a persistent `./data` directory to `/app/data`. The container starts the dashboard and backend; configure upstream servers in `data/mcp_settings.json` before launch or add them through the dashboard.

MCPHub works with Claude Code, Cursor, Claude Desktop, Cherry Studio, OpenWebUI, and other MCP-compatible applications. Clients connect to the gateway's MCP endpoint, such as `/mcp`, a group route, an individual server route, or a smart-routing route.

Connect the client to an MCP endpoint on the MCPHub host, such as `http://localhost:3000/mcp`. Use `/mcp/{group}` or `/mcp/{server}` for narrower access, or `/mcp/$smart` for semantic smart routing. Authentication is enabled on MCP endpoints by default.

Configure servers in `data/mcp_settings.json` using entries with commands and arguments for local processes, or manage them from the web dashboard. MCPHub also supports remote connections, OAuth settings, environment variables, groups, aliases, and runtime updates without downtime.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMCPHub AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/mcphub-2?style=directory)](https://allmcps.com/mcp/mcphub-2)
HTML Embed
<a href="https://allmcps.com/mcp/mcphub-2"><img src="https://allmcps.com/api/badge/mcphub-2?style=directory" alt="MCPHub on AllMCPs" /></a>