MCP Manager Gateway vs Gateway
A side-by-side look at the MCP Manager Gateway and Gateway MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
M
MCP Manager GatewayAggregators · Local subprocess (stdio)MCP Manager Gateway - Make MCP discoverable and launchable on demand, just like Skills: the Agent only sees one stable entry point, and only when needed does it find and invoke the actual tools.49FairAuth: not declaredVerdict: choose MCP Manager Gateway for aggregators work as a local process; choose Gateway for aggregators over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
MChoose MCP Manager Gateway when
- You need dedicated capabilities in the Aggregators domain.
- You prefer a local stdio subprocess transport.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | M MCP Manager Gateway | |
|---|---|---|
| Category | Aggregators | Aggregators |
| Quality signal | 49/100 · Fair | 52/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 6 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 2 |
| Full listing | View MCP Manager Gateway | View Gateway |
Tools & capabilities
MCP Manager Gateway tools
No tool names declared yet. Check the project README from the listing page.
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.
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
{
"mcpServers": {
"mcp-manager-gateway": {
"command": "uvx",
"args": [
"mcp-manager-gateway"
]
}
}
}
Gateway
{
"mcpServers": {
"gateway-4": {
"url": "https://mcp.toolhail.com/mcp"
}
}
}
Frequently asked questions
MCP Manager Gateway is categorized under Aggregators and uses a local stdio subprocess. Gateway belongs to Aggregators and uses a remote HTTP/SSE transport. Pick MCP Manager Gateway for aggregators work and Gateway 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. Gateway 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 gateway-4 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. Gateway has 52/100 (Good) with 0 views, 0 installs and 0 GitHub stars.