Connect Existing MCP

Add a Gateway to a connected server

Front your existing MCP server with Agenetix Gateway for OAuth, logging, and rate limiting.

3 sections

A Gateway adds an auth and control layer in front of your connected MCP server without modifying the server itself.

What Gateway provides for connected servers#

  • OAuth 2.1 authentication — users authenticate through Agenetix before tool calls reach your server
  • Request logging — every tool call is logged with timing, success/failure, and user identity
  • Rate limiting — usage policies control how many calls can be made
  • Public URL — a stable Gateway URL that agents and SDKs use instead of your internal server URL

Attach a Gateway#

  1. Open the connected server's detail page
  2. Navigate to the Gateway section
  3. Select an existing Gateway profile or create a new one
  4. Optionally customize the public ID, resource, and scopes
  5. Save the attachment
MERMAID
flowchart LR
    SDK["Agent SDK"] --> GW["Gateway\nOAuth + logging"]
    GW --> MCP["Your MCP server"]
    MCP --> API["Your API"]

After attachment, agents and the SDK automatically route through the Gateway URL instead of connecting to your server directly.

Gateway does not imply tool editing#

Attaching a Gateway to a connected server does not make its tools editable. The tools remain observed and read-only. Gateway only controls the auth/transport layer between agents and your server.