One endpoint, every server
Preview — part of the MCP Gateway private beta. Join the waitlist →
Point your MCP client at the Gateway once. From then on it's a single endpoint that can discover, connect, and proxy every other MCP server — so you don't wire up each server by hand.
Meta-tools
Once connected, the Gateway exposes these tools to your agent. (This is the full reference — the same set listed on the Gateway page.)
Discover & connect
| Tool | What it does |
|---|---|
mcp_discover |
Search the MCP Rating registry for servers |
mcp_connect |
Connect a server — by slug, command, or URL — spawned in a sandbox |
mcp_disconnect |
Disconnect a connected server |
mcp_list_active |
List currently connected servers |
mcp_server_info |
Inspect a connected server's tools, resources, and prompts |
mcp_call_tool |
Call a downstream tool explicitly by name |
Run safely
| Tool | What it does |
|---|---|
mcp_sandbox |
Inspect or adjust a server's sandbox manifest (env scope, egress allowlist) |
mcp_audit |
Query the safety audit trail — what ran, what was blocked |
mcp_gateway_health |
Gateway and downstream connection health |
Manage & optimize
| Tool | What it does |
|---|---|
mcp_profiles |
Manage named connection presets (work, personal…) |
mcp_groups |
Connect / disconnect groups of servers atomically |
mcp_usage |
Call analytics — latency, error rates |
mcp_recommend |
Suggest servers based on your usage patterns |
One more, mcp_ad_status, is registered only on ad-supported deployments (when a partner key is configured).
Connected servers' own tools appear namespaced — e.g. github-mcp-server__search_repositories — and are proxied through the one endpoint, including their resources and prompts.
Example
See the Quickstart for a full discover → connect → call walkthrough in code, or Integrations for client-specific setup.