What is MCPHub?
MCPHub sits between AI clients and the MCP servers they use. You register local stdio servers and remote SSE or Streamable HTTP servers once, in a JSON file or a web dashboard, and clients such as Claude Code, Cursor or Open WebUI connect to stable URLs: /mcp for everything, /mcp/{group} for a group, /mcp/{server} for one server, or /mcp/$smart for smart routing, which picks tools by vector search instead of loading every tool definition into the model's context.
Around the gateway it adds the controls a shared deployment needs: bearer keys, OAuth 2.0 in both client and server roles, passkeys, GitHub and Google sign-in, per-user credentials bound to a shared server, activity logs, health checks and optional PostgreSQL storage for multiple replicas. It is written in TypeScript, Apache 2.0 licensed, and released v1.3.0 on 21 November 2026. The repository dates from 31 March 2025 and has about 2,742 stars.
How to install MCPHub
docker run -p 3000:3000 -v ./data:/app/data samanhappy/mcphubIs MCPHub worth it?
MCPHub solves a problem that grows with each MCP server a team adopts: every developer configures the same servers in every client, with their own copies of the keys. MCPHub centralises that. Servers are registered once and exposed through a few stable endpoints, grouped by team or task, and Smart Routing uses vector search over tool descriptions so a client can find the right tool among hundreds without loading them all into context. The MCP Apps proxy and tool-result compression are small touches that show the maintainer is following the protocol closely.
Security defaults are mostly sensible. MCP endpoints require a bearer key by default, and the README warns that turning that off is for trusted networks only. If no ADMIN_PASSWORD is set, the first launch generates a random admin password and prints it to the logs. Per-user credentials are stored encrypted and run in isolated stdio processes. Database mode now refuses to generate its own encryption key, and the README is blunt that a database backup without the MCPHUB_CREDENTIAL_ENCRYPTION_KEY cannot recover those credentials.
The risks follow from the design. The quick-start docker run publishes port 3000 on every network interface, not just localhost, and the stdio servers it launches run inside the MCPHub container with whatever access you give it; the latest-full image adds a Docker Engine for container-in-container use. A single compromised hub exposes every key behind it. Local development uses a fixed admin/admin123 login, which is fine on a laptop and dangerous anywhere else.
The project is active: 1,036 commits, releases three days apart (v1.2.6 on 18 November, v1.3.0 on 21 November 2026) and only 14 open issues. Docker's MCP Gateway is the closer rival for one developer on Docker Desktop; MCPHub fits better when several people share one hub and need their own logins and keys.
Where it earns its place
A platform engineer at a 50-developer company
Give everyone the same approved MCP servers without handing out the underlying API keys
Run MCPHub in database mode behind HTTPS, group servers by team, and issue scoped bearer keys; developers point Claude Code or Cursor at /mcp/{group}. Software cost is zero; the work is operating PostgreSQL and the encryption key.
A developer with 30 MCP servers configured
Stop tool definitions from filling the model's context
Point the client at /mcp/$smart, which searches tool descriptions by vector similarity and returns only the relevant ones. Needs PostgreSQL with pgvector and an embedding setup.
Before you commit
- Setup
- docker run -p 3000:3000 -v ./data:/app/data samanhappy/mcphub, then sign in as admin with the password printed in the logs (or set ADMIN_PASSWORD). Add servers in the dashboard or in data/mcp_settings.json. Minutes to a working endpoint.
- Integrations
- Any MCP client (Claude Code, Cursor, Cherry Studio, Open WebUI); stdio, SSE and Streamable HTTP servers; OAuth 2.0; GitHub and Google sign-in via Better Auth; PostgreSQL with pgvector; a CLI; Agent Skills published over MCP.
- Data and privacy
- Self-hosted: settings, users and credential bindings persist in ./data or PostgreSQL. Per-user credentials are encrypted at rest; database mode needs a persistent MCPHUB_CREDENTIAL_ENCRYPTION_KEY that you must back up. Tool calls pass through and are logged by the hub. No hosted service is offered.
- Cost at scale
- No licence cost for the open-source edition; you pay for the host, PostgreSQL and any embedding calls for Smart Routing. Enterprise pricing is not published.
- Limits
- Default image covers Node and Python servers; Rust, Docker and Playwright servers need the larger latest-full image (Playwright on amd64 only). Multiple replicas need explicit session affinity.
What’s good
- One endpoint per group or server, plus semantic Smart Routing
- Bearer auth on MCP endpoints by default; OAuth 2.0, passkeys and SSO
- Per-user credentials encrypted and isolated in their own stdio runtimes
- Logs, health checks and PostgreSQL mode for multiple replicas
What’s not
- Quick-start Docker command exposes port 3000 on all interfaces
- Concentrates every MCP credential in one service
- Losing the encryption key makes stored credentials unrecoverable
- Enterprise edition and its price not yet published
Best for
Platform or developer-experience teams that want to share a curated set of MCP servers across many users and clients with central auth and logging.
MCPHub alternatives
MCPHub: common questions
- Is MCPHub worth it?
- MCPHub is a capable, actively maintained way to give a team one authenticated front door to its MCP servers, as long as you treat the box it runs on as a vault for every credential behind that door. We rate it 4.0 out of 5.
- How much does MCPHub cost?
- Free and open source (Apache 2.0) to self-host, with unlimited servers, users and groups. An Enterprise edition sold for a one-time payment is listed as coming soon, price not published.
- What are the downsides of MCPHub?
- Quick-start Docker command exposes port 3000 on all interfaces; concentrates every MCP credential in one service; losing the encryption key makes stored credentials unrecoverable; enterprise edition and its price not yet published.
- Who is MCPHub best for?
- Platform or developer-experience teams that want to share a curated set of MCP servers across many users and clients with central auth and logging.
- How much does MCPHub cost for a team or in production?
- No licence cost for the open-source edition; you pay for the host, PostgreSQL and any embedding calls for Smart Routing. Enterprise pricing is not published.
- Is MCPHub safe for company data?
- Self-hosted: settings, users and credential bindings persist in ./data or PostgreSQL. Per-user credentials are encrypted at rest; database mode needs a persistent MCPHUB_CREDENTIAL_ENCRYPTION_KEY that you must back up. Tool calls pass through and are logged by the hub. No hosted service is offered.
- What are the best MCPHub alternatives?
- The closest alternatives we have reviewed are Docker MCP Gateway, Composio and Pipedream MCP and Connect.
Answers checked Nov 21, 2026.