How to Set Up a Gateway
Connect a Gateway you've already created to Cursor, Claude, Claude Code, or any other MCP-compatible client.
Once you've created a Gateway, the next step is connecting it to the tools you actually work in, like Cursor, Claude Desktop, Claude Code, Windsurf, or any other MCP-compatible client.
This page covers connecting a Gateway you've already created. If you haven't set one up yet, start with Gateway/Deployment Creation.
Open Client Setup
Navigate to Secure → Gateway → MCP Gateway, find the Gateway you want to connect, and click Client Setup on its card.
Search for or select your client, for example Cursor, Claude Code, or Claude. Each one walks you through the exact steps for that client. If your client isn't listed, everything you need is still just the Gateway's URL. See Connect other clients below.
You don't need to open Client Setup just to grab the connection address. Click Copy URL on the Gateway's card to copy it directly. This is handy if you're following a client's own setup docs and only need the address.
Your Gateway's URL
The snippets on this page show the Airia US cloud host, mcp-gateway.airia.ai, with {your-gateway-id} standing in for your Gateway's ID. Rather than typing the address, copy it from Client Setup or with Copy URL on the Gateway's card: the host depends on the region your organization's Airia account runs in, and Client Setup already includes the right one for you. A copied address looks like this, with your region's host and your Gateway's ID filled in:
https://mcp-gateway.airia.ai/gateway/{your-gateway-id}/mcpConnecting to a Tenant-level Gateway is still something each person does individually. There's no single login or key shared between coworkers. Everyone who wants to use a Tenant Gateway from their own client opens Client Setup and authenticates with their own account.
Connect Cursor
Open Client Setup on your Gateway and select Cursor.
Cursor opens automatically with a prompt to install the connection. Confirm the install.
Cursor opens your browser to complete sign-in the first time it needs to connect.
Connect Claude
The Claude option in Client Setup adds your Gateway as a custom connector. A custom connector belongs to your Claude account rather than to one device, so once it's added it's available in claude.ai, Claude Desktop, Cowork, and the Claude mobile apps.
Claude connects to your Gateway from Anthropic's cloud, not from your own computer, so the Gateway's URL must be reachable over the public internet. If your Gateway sits on a private network, allowlist Anthropic's published IP ranges.
On Free, Pro, and Max plans, go to Customize → Connectors in Claude. On Team and Enterprise plans, an organization Owner first adds the connector under Organization settings → Connectors, and then each member connects individually from Customize → Connectors.
Click +, then Add custom connector, and enter the Name and URL shown in Client Setup. Team and Enterprise Owners click Add, hover Custom, and select Web instead.
Click Add, then complete the sign-in and consent prompt. To use the Gateway in a conversation, turn the connector on from the + button in the chat composer.
Connect Claude Code
Open Client Setup and select Claude Code, then run the command it shows you in your terminal:
claude mcp add --scope user --transport http my-gateway "https://mcp-gateway.airia.ai/gateway/{your-gateway-id}/mcp"Exit Claude Code completely and relaunch it. The new server won't show up until you do.
Inside Claude Code, run /mcp, select your Gateway, and complete the sign-in flow in your browser.
See Anthropic's MCP authentication documentation for more on how that flow works from Claude Code's side.
Connect other clients
This page walks through Cursor, Claude, and Claude Code because they're the most common clients Airia customers use. Client Setup also has setup screens for many other clients, and a Gateway's endpoint is standards-compliant, so it works with any MCP client that supports remote HTTP servers, including Windsurf, VS Code, and others.
Get it from Client Setup, or click Copy URL on the Gateway's card.
Add the URL as a remote MCP server, following that client's own instructions for doing so.
If your client prompts for authentication, choose OAuth. Your client walks you through a one-time sign-in in your browser and takes care of the rest automatically.
The exact wording and steps for signing in vary a bit from client to client, but every one of them is connecting to the same underlying Gateway the same way.
Gateways with Radar enabled
If a Gateway has Radar turned on, every step above still applies exactly as written. Client Setup automatically points your client at the right endpoint. If you're adding a client manually and building the URL yourself, use /radar instead of /mcp at the end.
About connection names
Airia generates a short name for the Gateway automatically wherever a client needs one to label the connection, based on the Gateway's own name. If that name looks abbreviated or unfamiliar once it shows up in your client, that's expected. You can rename the entry locally in your own configuration. Renaming it on your end never affects the Gateway itself or anyone else connected to it.