MCPHubBETA

One gateway for all your
MCP servers.

Connect your MCP servers once. Control how clients and agents access them. Operate everything through one open-source, self-hosted gateway.

$ docker run -d --name mcphub -p 3000:3000 samanhappy/mcphub
localhost:3000
Overview
12 servers · 247 tools · 3 groups
CALLS / 24H
14.2k
+12%
ACTIVE SERVERS
11/12
healthy
P95 LATENCY
184ms
−8ms
TOOL INDEX
247
tools
Connected servers12 total
G
github
@modelcontextprotocol
stdio7 tools healthy⋯
P
postgres
@modelcontextprotocol
stdio11 tools healthy⋯
P
playwright
@microsoft
stdio15 tools healthy⋯
S
slack
@modelcontextprotocol
stdio19 tools healthy⋯
B
brave-search
@brave
http3 tools healthy⋯
POWERS AGENTS BUILT WITH
Claude DesktopCursorClineContinue.devWindsurfZedCustom Agents
Why MCPHub?

One control point for your MCP infrastructure.

Centralize connectivity, access, credentials, routing, and operations without changing your MCP clients or servers.

Connect

Connect local and remote MCP servers and expose them through stable, unified endpoints.

Read the docs

Control

Control who can access servers and capabilities with authentication, scoped keys, visibility, and per-user credentials.

Read the docs

Route

Organize servers into groups and route clients through aggregate, scoped, direct, or smart endpoints.

Read the docs

Operate

Monitor health, inspect activity and logs, and manage MCP infrastructure from one place.

Read the docs
Architecture

One control plane between agents and MCP servers.

Point MCP-compatible clients and agents at MCPHub. MCPHub centralizes authentication, credentials, routing, capability discovery, and operational visibility before requests reach backend MCP servers.

AI CLIENTS / AGENTS
Claude
Cursor
Cline
Custom
mcphub
CONTROL PLANE
healthy
/mcpaggregate
/mcp/{group}group
/mcp/{name}single
/mcp/$smartsemantic
Identity · Credentials · Access Control · Routing · Observability
MCP SERVERS
G
github
P
postgres
P
playwright
S
slack
B
brave-search
F
filesystem
N
notion
L
linear
+ 119 more in Registry
Built for developers

Tools that respect your workflow.

Manage from the terminal

Use the CLI to discover, install, configure, and inspect servers. It reads from the same Registry as the website.

See CLI docs
$ mcphub discover --keyword postgres

→ @modelcontextprotocol/postgres   ★ 8.1k
→ @neon/postgres                  ★ 1.2k
→ @supabase/postgres              ★ 980

$ mcphub install @modelcontextprotocol/postgres
✓ Added to mcp_settings.json
✓ Hot-reloaded — endpoint ready

Discover & install with one click

Browse community MCP servers from the Registry. Click install and MCPHub writes the client config.

Browse the Registry
postgres
P
postgres
@modelcontextprotocol
S
sqlite
@modelcontextprotocol

Let AI pick the right tool

Smart Routing indexes tool descriptions in a vector store. When the model asks for a capability, MCPHub returns a small matching set.

How smart routing works
“Find the last 5 issues mentioning database timeouts and create a tracking doc.”
SEMANTIC MATCH
github.search_issues0.94
linear.list_issues0.87
notion.create_page0.83
sentry.list_errors0.61
Flexible routing

One gateway, four routing modes.

Each routing mode is a stable URL. Use them per-client, per-project, or per-team.

/mcp
Aggregate
All tools from all servers, in one connection.Docs
/mcp/{group}
Group
Tools scoped to a named group (per-team, per-project).Docs
/mcp/{server}
Single server
Direct passthrough to one server. Useful for debugging.Docs
/mcp/$smart
Smart
Semantic tool discovery. The model gets a smaller tool list.Docs
GITHUB STARS
2,491
MCP SERVERS INDEXED
300+
DOCKER PULLS
100K+
COMMUNITY MEMBERS
400+

Run MCP servers
from one gateway.

Spin up MCPHub in under a minute. Connect Claude Desktop in five.

Running MCPHub in production?Get production support