mcphub vs toolsdk-mcp-registry
MCP gateways and server discovery compared
mcphub centralizes connections, routing, access controls, and monitoring for MCP servers. toolsdk-mcp-registry combines a searchable catalog of MCP packages with a gateway for discovering and executing tools; its emphasis is registry data and package execution.
mcphub: Connect and Manage MCP Servers Through One Gateway
MCPHub is a self-hosted gateway and control plane for connecting MCP clients to local and remote MCP servers. It centralizes routing, access controls, credentials, logs, and health monitoring.
toolsdk-mcp-registry: Discover and Run MCP Servers
ToolSDK MCP Registry catalogs MCP servers and provides a self-hosted gateway for searching and executing them. It is aimed at teams building AI applications that need centralized tool discovery, protocol bridging, and controlled execution.
| mcphub | toolsdk-mcp-registry | |
|---|---|---|
| Language | TypeScript | TypeScript |
| License | Apache-2.0 | MIT |
| Stars | 2.5k | 188 |
| Forks | 330 | 330 |
| Last analyzed | Oct 3, 2026 | Oct 4, 2026 |
Key differences
- mcphub focuses on managing connections to local and remote servers, while toolsdk-mcp-registry adds a structured catalog of MCP packages and federated search.
- mcphub offers routing, per-user credentials, visibility controls, logs, and health checks; toolsdk-mcp-registry offers an HTTP API for searching and executing tools, plus optional sandbox execution.
- mcphub supports stdio, SSE, and Streamable HTTP connections, while toolsdk-mcp-registry exposes STDIO packages through Streamable HTTP.
- mcphub is licensed under Apache-2.0, while toolsdk-mcp-registry is licensed under MIT.
- Both projects use TypeScript and report 330 forks; mcphub reports 2.5k stars and toolsdk-mcp-registry reports 188.
- mcphub recommends Docker for a quick start and supports file-based or PostgreSQL-backed configuration; toolsdk-mcp-registry offers Docker deployment, an npm package for registry data, and public JSON indexes.
Choose mcphub if you…
- need centralized routing, access controls, and operational visibility across MCP servers.
- want per-user credentials or server and group visibility controls.
- prefer a gateway that supports local and remote connections over stdio, SSE, and Streamable HTTP.
Choose toolsdk-mcp-registry if you…
- want a catalog and federated search for MCP server packages alongside a gateway.
- need to expose STDIO-based tools through Streamable HTTP and an HTTP API.
- want registry data through an npm package or public JSON indexes, or need optional sandbox execution.
This comparison is generated with AI from the OSRepos analyses of both projects. Always check each project's repository and documentation before choosing.