MCP Gateway documentation

Preview — the MCP Gateway is in private beta. These docs describe how it works today; the public release is on the way. Join the waitlist →

The MCP Gateway is a meta-server: a single MCP endpoint that discovers, connects, and proxies other MCP servers — running untrusted ones in a sandbox and recording everything in a safety audit trail.

How it fits together

1. Discover servers from the MCP Rating registry — quality- and safety-scored.
2. Connect a server — local servers are spawned in a sandbox; remote servers connect over the network.
3. Call their tools, resources, and prompts through one endpoint — every call policy-checked and audited.

Core concepts

• Sandboxed execution — how untrusted servers are isolated (L1 / L2).
• Egress allowlist — controlling what a server can reach on the network.
• Safety audit trail — the forensic log of what ran and what was blocked.
• One endpoint, every server — discover, connect, and proxy from a single endpoint.
• Access types — how the Gateway handles local vs remote / web servers.
• Integrations — Cursor, Claude Desktop, and the API in TypeScript & Python.

Get started

See the Quickstart for a discover → connect → call walkthrough.