Skip to main content

Roll out gateway clients

After you deploy the gateways, direct users to the setup instructions in the console. The console supplies the endpoints and client-specific configuration for your deployment.

Choose the gateway endpoints​

Clients can use either or both gateways:

  • Send OpenAI-compatible model traffic to the AI Gateway.
  • Send MCP tool calls to the Connector Gateway.

Each gateway has a Clients tab in the console's User experience with the endpoint and setup guides for your deployment. Direct users there instead of copying endpoint details into rollout documentation. To open it, users choose User under Experience in the account menu, select Connectors or AI Gateway under Gateways, and open the Clients tab.

Connector Gateway clients​

The Clients tab under Connectors has three parts:

  • Ask your AI assistant copies a prompt that users paste into Claude Code, Cursor, or another AI coding client. The assistant then configures the gateway connection itself.
  • Manual setup shows the gateway endpoint URL. Clients connect over Streamable HTTP and sign in with OAuth using dynamic client registration, so there is no token or client ID to copy.
  • Setup guides has step-by-step instructions for Claude Code, Claude (web and desktop), Codex, Cursor, and VS Code. Other clients lists the endpoint, transport, authentication method, and OAuth discovery URL to enter in any other MCP client.

Claude on the web and Claude Desktop connect to the gateway from Anthropic's cloud, so they work only when the gateway endpoint is reachable from the public internet. A gateway on a private network, behind a VPN, or behind a firewall won't connect. Use a locally running client such as Claude Code instead.

A client exposes only the tools from connectors the user has connected to. Each user connects to their connectors on the Tools tab first. See Manage your connections.

AI Gateway clients​

The Clients tab under AI Gateway shows the Model gateway URL for OpenAI-compatible clients, a Get an API key shortcut to the API Keys tab, and setup guides for routing popular clients' model traffic through the gateway.

Choose an authentication method​

  • Use browser-based sign-in for interactive clients. The session identifies the caller through your corporate identity provider.
  • Use a virtual API key for scripts, scheduled jobs, continuous integration, and other clients without a browser flow. Requests remain attributed to the key owner.

Prepare access before rollout​

Before distributing the setup instructions:

  • Assign an AI Gateway budget to each user or group that will send model traffic.
  • Grant directory groups access to the required connectors.
  • Tell users to connect to their connectors in the console before using them, and to sign in when a connector requires OAuth.

Next steps​