Gateway vs MetaMCP
A side-by-side look at the Gateway and MetaMCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Gateway for aggregators work over a hosted endpoint; choose MetaMCP 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 Gateway when
- You need dedicated capabilities in the Aggregators domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
find_mcp_server, call_tool.
Choose MetaMCP when
- You need dedicated capabilities in the Aggregators domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Aggregators | Aggregators |
| Quality signal | 52/100 · Good | 47/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 18 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 2 | Not listed |
| Full listing | View Gateway | View MetaMCP |
Tools & capabilities
Gateway tools 2
find_mcp_servercall_toolProxy one tool call to a discovered remote MCP server (paid). Every call passes pre-execution guards before anything runs: tools on TOOLHAIL_BLOCKED_TOOLS are always refused; when TOOLHAIL_ALLOWED_TOOLS is set (non-empty, no "*") only listed tools may fire; write/mutating-looking tool names are refused unless allowWrite:true is passed or the tool is allowlisted; and TOOLHAIL_ARG_LIMITS can cap specific argument values per tool (e.g. daily_budget<=500) so an allowlisted broad tool still cannot push a value past its ceiling. Any refusal executes nothing and bills nothing, and every receipt records the gate decision.
MetaMCP 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.
Gateway
{
"mcpServers": {
"gateway-4": {
"url": "https://mcp.toolhail.com/mcp"
}
}
}
MetaMCP
{
"mcpServers": {
"metamcp": {
"command": "npx",
"args": [
"-y",
"@mentu/metamcp@latest"
]
}
}
}
Frequently asked questions
Gateway is categorized under Aggregators and uses a remote HTTP/SSE transport. MetaMCP belongs to Aggregators and uses a local stdio subprocess. Pick Gateway for aggregators work and MetaMCP 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.
Gateway has no declared pricing — check the project's own site. MetaMCP 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 gateway-4 and metamcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Gateway has a quality signal of 52/100 (Good) with 0 views, 0 installs and 0 GitHub stars. MetaMCP has 47/100 (Fair) with 0 views, 0 installs and 18 GitHub stars.