AI Gateway

MCP servers

Overview

The Servers page is where you register the backend MCP servers that your AI agents will call through the gateway. Each server exposes one or more tools (database queries, search, file operations, etc.) that agents can discover and invoke.

You'll find it at AI Gateway > MCP Gateway > Servers.

Server list

The main view shows all registered servers as a list. Each row displays:

Server name: The display name you gave the server.
Health status: A color-coded chip: green for "Healthy", red for "Unhealthy", or gray for "Unknown".
Tool count: How many tools have been discovered on this server.
URL: The server's endpoint URL.
Auth type: Shows "no auth", "bearer", or "api_key".
Slug: The URL-safe identifier, shown as a path segment (e.g., /my-server).
Created by: The user who registered the server and the date.

Click any row to open the edit modal. Use the toggle on the right to enable or disable a server without deleting it.

Adding a server

Click Add server in the top-right corner. The modal has these fields:

Field	Required	Description
Server name	Yes	A human-readable name (e.g., "Production Search Server").
Slug	Yes	Auto-generated from the name. Lowercase letters, digits and hyphens only. Must start with a letter or digit. Can't be changed after creation.
URL	Yes	The full URL of the MCP server (e.g., https://mcp-server.example.com).
Description	No	A short note about what this server does (e.g., "Exposes search and retrieval tools").
Authentication	No	How the gateway authenticates with this server. Options: None (default), Bearer token, or API key.

Authentication options

The gateway supports three authentication methods when connecting to your backend MCP servers:

None: No authentication header is sent. Use this for servers on a private network or behind a VPN.
Bearer token: The gateway sends an Authorization: Bearer <token> header with each request. Enter the token in the modal.
API key: The gateway sends a custom header with an API key value. You choose the header name (defaults to X-API-Key) and enter the key value.

Auth credentials are stored encrypted

Bearer tokens and API keys are encrypted at rest. They're only decrypted when the gateway forwards a request to the server. You won't see the full credential after saving.

Editing a server

Click a server row or the pencil icon to open the edit modal. You can change the name, URL, description and auth configuration. The slug can't be changed after creation because agent keys and audit logs reference it.

To update auth credentials, select the auth type and enter new values. Leave the credential fields empty to keep the existing values.

Enabling and disabling servers

Each server has an active/inactive toggle. When you disable a server:

Its tools stop appearing in tools/list responses to agents.
Any tools/call requests targeting its tools are rejected.
The server's configuration is preserved. Toggle it back on at any time.

This is useful during maintenance windows or when you need to quickly cut off access to a server without deleting it.

Health monitoring

The gateway tracks each server's health status. The health chip next to the server name shows one of three states:

Healthy: (green) The server responded successfully to the last health check or tool discovery.
Unhealthy: (red) The server failed to respond or returned an error. The gateway will still attempt to route requests, but they'll likely fail.
Unknown: (gray) No health check has run yet. This is normal for newly registered servers.

Health status updates automatically when tool discovery runs. Unhealthy servers aren't automatically bypassed, but you can disable them manually.

Tool discovery

After registering a server, the gateway can discover its tools automatically. The discover endpoint (POST /mcp/servers/{id}/discover) connects to the server, lists its tools and stores them in the tool catalog.

The discovery button in the UI is currently marked as "Coming soon". In the meantime, discovery runs through the API or when the gateway first routes a request to a server.

Manual discovery via API

You can trigger discovery programmatically: POST /api/ai-gateway/mcp/servers/{server_id}/discover. This calls the server's tools/list method and stores the results.

Deleting a server

Click the trash icon on a server row to open the delete confirmation modal. Deleting a server:

Permanently removes the server and all its registered tools from the catalog.
Agents referencing those tools will receive errors on their next call.
Existing audit log entries for tools from this server are preserved.

This can't be undone

Deleting a server removes it permanently. If you just want to stop routing traffic, disable the server with the toggle instead.

Slug format rules

Slugs must follow these rules:

Start with a lowercase letter or digit.
Contain only lowercase letters, digits and hyphens.
Be unique across all servers in your organization.
Can't be changed after the server is created.

The slug is auto-generated from the server name when you create a new server. For example, "Production Search Server" becomes production-search-server.

Permissions

Creating, editing and deleting servers requires the Admin role. All authenticated users can view the server list.

Tool catalog

View and manage discovered tools across your servers.

Agent keys

Create API keys that agents use to access servers through the gateway.

MCP Gateway overview

Understand how the gateway proxies agent-to-server communication.

PreviousMCP Gateway overview

NextMCP tool catalog