Hive Gateway vs MCPDiscovery
A side-by-side look at the Hive Gateway and MCPDiscovery MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Hive Gateway for aggregators work over a hosted endpoint; choose MCPDiscovery 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 Hive Gateway when
- You need dedicated capabilities in the Aggregators domain.
- You prefer a remote HTTP/SSE transport.
Choose MCPDiscovery when
- You need dedicated capabilities in the Aggregators domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Aggregators | Aggregators |
| Quality signal | 36/100 · Fair | 43/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 53 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Hive Gateway | View MCPDiscovery |
Tools & capabilities
Hive Gateway tools
No tool names declared yet. Check the project README from the listing page.
MCPDiscovery 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.
Hive Gateway
{
"mcpServers": {
"hive-gateway": {
"url": "http://localhost:3000/morph/mcp"
}
}
}
MCPDiscovery
{
"mcpServers": {
"particlefuture-mcpdiscovery": {
"command": "npx",
"args": [
"-y",
"@1mcpserver/1mcpserver"
]
}
}
}
Frequently asked questions
Hive Gateway is categorized under Aggregators and uses a remote HTTP/SSE transport. MCPDiscovery belongs to Aggregators and uses a local stdio subprocess. Pick Hive Gateway for aggregators work and MCPDiscovery 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.
Hive Gateway has no declared pricing — check the project's own site. MCPDiscovery is listed as free. Auth: no auth required. 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 hive-gateway and particlefuture-mcpdiscovery as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Hive Gateway has a quality signal of 36/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. MCPDiscovery has 43/100 (Fair) with 2 views, 0 installs and 53 GitHub stars.