MCP Gateway documentation

Beta — the MCP Gateway is open source and on npm: npx -y @mcp-rating/gateway. Source →

The MCP Gateway is a meta-server: a single MCP endpoint that discovers, connects, and proxies other MCP servers — starting each one with only the environment variables you allow, and recording what it did in an 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 with a scoped environment (and in a container, if you enable isolation); remote servers connect over the network.
3. Call their tools, resources, and prompts through one endpoint. Every tool call is checked against your permission policy and recorded in the audit trail; resource reads and prompts are not.

Prefer nothing to install? Use MCP Rating from Claude or ChatGPT: add our hosted endpoint as a connector and search the index from a chat.

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.