MCPHub
A self-hosted gateway and control plane for MCP servers that connects local and remote servers once, exposes their tools through stable routed endpoints, and adds authentication, per-user credentials, logging and health monitoring on top.
MCPHub is a self-hosted control point between AI clients and MCP servers. It connects to local and remote MCP servers over SSE, Streamable HTTP or stdio, then organizes and routes their tools, prompts and resources through stable endpoints, including routes for a whole group of servers, a single server, or an AI-driven vector-search router that picks the right tool automatically. Servers can be added, removed or updated without downtime.
Access is controlled with OAuth 2.0 in either client or server mode, bearer keys, GitHub and Google social login, and per-server or per-group visibility; per-user credentials let several people share one underlying server while each keeps their own key in encrypted storage and an isolated session. A web dashboard shows tool-call activity, request status, latency and server logs, runs health checks across connected servers, and can compress large tool outputs before returning them.
It works with MCP clients such as Claude Code, Cursor, Cherry Studio and OpenWebUI.