Manage & Operate

Manage Gateways

Create, configure, and attach Gateway profiles for auth, logging, and rate limiting.

5 sections

A Gateway is a reusable auth/control profile that can be attached to any MCP server (generated or connected).

Gateway capabilities#

  • OAuth 2.1 authentication for end users and agents
  • Request logging with timing, status, and user identity
  • Rate limiting via usage policies
  • Stable public URL for agents and SDKs to connect through

Create a Gateway#

  1. Go to Gateways > Create
  2. Name the Gateway and configure the OAuth provider
  3. Set the authorization server URL, client ID, resource, and scopes

Attach to a server#

A Gateway can be attached to either kind of MCP server:

  • Generated server: the worker runs behind the Gateway auth edge
  • Connected server: the Gateway proxies authenticated requests to your server
MERMAID
flowchart TB
    subgraph Generated["Generated server"]
        GW1["Gateway"] --> Worker["Hosted worker"]
    end
    subgraph Connected["Connected server"]
        GW2["Gateway"] --> Remote["Your MCP server"]
    end

Share across servers#

One Gateway profile can be attached to multiple MCP servers. Each attachment gets its own unique public URL, but they share the same OAuth configuration.

Detach a Gateway#

Detaching a Gateway removes the auth layer. The server's URL reverts to direct access. Existing agent configurations will need their MCP auth connections re-established.