mcphub
MCPHub manages several MCP servers in one place and exposes them as Streamable HTTP (SSE) endpoints: all servers together, a single server, or a logical group. A web dashboard shows and controls the servers, and servers can be added, removed or updated without downtime. The README also lists smart routing, which uses vector semantic search to discover the right tool, OAuth 2.0 in both client and server modes, GitHub and Google social login through Better Auth (this needs database mode), and a PostgreSQL database mode for storing configuration in production.
Setup is a `mcp_settings.json` file in the familiar `mcpServers` format plus one Docker command that maps port 3000 and mounts the config. The dashboard is at `http://localhost:3000` with a default `admin` / `admin123` login that you should change. Clients connect to `/mcp` for all servers, `/mcp/{group}` or `/mcp/{server}` for a subset, and `/mcp/$smart` for smart routing. The README notes that MCP endpoints require authentication by default and that disabling bearer authentication should only be done in trusted environments. The stack is Node.js, Express and TypeScript with a React front end, and it is Apache-2.0 licensed with documentation at docs.mcphubx.com.
Features
Why choose it
Trade-offs
Compatibility
Quick start
Use cases
Alternatives
Featured in these lists
Comments
No comments yet. Be the first!