Skip to content
Last updated

Configuration

The Configuration tab in the Agen for SaaS control plane manages the core settings for your MCP server. It is divided into two collapsible sections: Basic configuration and Allowed origins.

basic-configuration


Basic configuration

The basic configuration section contains the following settings:

FieldDescriptionEditable
Server nameThe display name for your MCP server (e.g., "Expense Management App"). This is a required field.Yes
MCP Gateway URLThe auto-generated endpoint where AI agents connect to your MCP server (e.g., your-id.mcp-gw.frontegg.com). Includes a copy button for easy sharing.No (read-only)
Custom domainAn optional custom domain mapped to your MCP Gateway. Displays "No domain configured" when not set.Yes (via Configure button)

Click Save to apply changes to the server name, or Cancel to discard.


Custom domain setup

To configure a custom domain for your MCP Gateway:

  1. Click the Configure button below the Custom domain field.
  2. In the Configure custom domain dialog, a two-step wizard guides you through the process:

Step 1: Add domain

  • Enter your desired domain in the Domain field.
  • Click Next to proceed.

Step 2: DNS records

  • The wizard displays the DNS records (CNAME entries) you need to add to your domain's DNS configuration.
  • Add these records through your DNS provider.
  • Once DNS propagation completes, Agen for SaaS verifies the domain automatically.

Click Cancel at any point to exit the wizard without changes.


Verify connections by email

On the Configuration tab, the Verify connections by email card appears below the Basic configuration section. It has a single toggle, which is off by default. Turning it on or off saves immediately, and no other setting is changed. The toggle is disabled if you do not have permission to edit settings.

When the toggle is on, users connecting an app like GitHub or Slack from an agent's link must first enter a one-time code sent to their email, so only they can complete the connection.

The connection flow works as follows:

  1. A user of your app opens the connection link from an agent and signs in to the third-party app (for example, GitHub or Slack).
  2. After the sign-in, the gateway shows a Check your email page with a 6-digit code field. The page shows a masked version of the email address that the code was sent to (for example, a***@example.com).
  3. The code is emailed to the user who started the connection. The user enters the code and selects Verify and connect.
  4. The connection is saved only after the correct code is entered.

A code is valid for 5 minutes. After 5 incorrect attempts, the code is locked until it expires, and the user must start the connection again from the agent. Because the code goes only to the user who started the connection, a person who opens a forwarded link cannot complete the connection without access to that user's inbox.

The setting does not apply in these cases:

  • Customer-hosted (hybrid) gateways ignore the setting, because they cannot send the email.
  • Connections made with tenant machine tokens skip the code, because there is no user to email.
  • Integrations that use the implicit OAuth flow, such as Trello, skip the code.

Allowed origins

The Allowed origins section controls which web origins can access your Agen for SaaS application. Access is enforced by the Origin HTTP header.

By default, two origins are pre-configured:

  • {{APP_URL}} — Your application's URL.
  • {{LOGIN_URL}} — Your login page URL.

Each origin entry has a delete button (trash icon) to remove it.

To add an origin:

  1. Click + Add new origin.
  2. Enter the origin URL.
  3. Click Save.

Changes to allowed origins take up to 5 minutes to take effect.