A side-by-side look at the Hatago MCP Hub and MCP Launcher MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Hatago MCP Hub for aggregators work as a local process; choose MCP Launcher for aggregators as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Hatago MCP Hub when
You need dedicated capabilities in the Aggregators domain.
No tool names declared yet. Check the project README from the listing page.
MCP Launcher 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.
Hatago MCP Hub is categorized under Aggregators and uses a local stdio subprocess. MCP Launcher belongs to Aggregators and uses a local stdio subprocess. Pick Hatago MCP Hub for aggregators work and MCP Launcher 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.
Hatago MCP Hub has no declared pricing — check the project's own site. MCP Launcher 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 hatago-mcp-hub and mcp-launcher as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Hatago MCP Hub has a quality signal of 40/100 (Fair) with 1 views, 0 installs and 27 GitHub stars. MCP Launcher has 41/100 (Fair) with 0 views, 0 installs and 1 GitHub stars.