A side-by-side look at the MCP Manager Gateway and MCP Hub MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Manager Gateway for aggregators work as a local process; choose MCP Hub for aggregators as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
M
Choose MCP Manager Gateway when
You need dedicated capabilities in the Aggregators domain.
No tool names declared yet. Check the project README from the listing page.
MCP Hub tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
MCP Manager Gateway is categorized under Aggregators and uses a local stdio subprocess. MCP Hub belongs to Aggregators and uses a local stdio subprocess. Pick MCP Manager Gateway for aggregators work and MCP Hub for aggregators.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
MCP Manager Gateway is listed as free. MCP Hub has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add mcp-manager-gateway and mcp-hub as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Manager Gateway has a quality signal of 49/100 (Fair) with 0 views, 0 installs and 6 GitHub stars. MCP Hub has 45/100 (Fair) with 1 views, 0 installs and 3 GitHub stars.