## Settings

The Settings page lets you configure the foundational properties of your Agen for Work environment, including the server name, MCP gateway URL, custom domain, and allowed origins. These settings control how AI agents connect to your Agen for Work instance and how your organization's branding is applied to the gateway endpoint.

To access the Settings page, click the **Settings** icon (gear) in the left sidebar.

![Settings page](/assets/agen-for-work-settings.12f2545fe221967cd6fc7c188b938a244be20bb91a394b9d1001cb29131d1035.1d3e9401.png)

br
### Basic configuration

The **Basic configuration** section is an expandable panel that contains the core settings for your Agen for Work environment.

| Field | Required | Description |
|  --- | --- | --- |
| **Server name** | Yes | The display name for your Agen for Work server (e.g., "Agen for Work"). This name identifies your instance across the platform. |
| **MCP Gateway URL** | — | The auto-generated URL for your MCP (Model Context Protocol) gateway endpoint (e.g., `xn7fc8n1bdriamc9usupz.mcp-gw.frontegg.com`). This is the endpoint that AI agents use to connect to your Agen for Work instance. Click the copy icon to copy the URL to your clipboard. This field is read-only. |
| **Custom domain** | No | An optional custom domain to replace the default MCP Gateway URL with your organization's branded domain. Displays "No domain configured" when not set. |


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

#### Configuring a custom domain

To set up a custom domain, click the **Configure** button below the Custom domain field. A two-step wizard opens:

![Configure custom domain](/assets/agen-for-work-settings-custom-domain.8272aafef924832f80a138fae7fa5260c8c23eca490b7716089ed44af599e26f.1d3e9401.png)

br
##### Step 1: Add domain

Enter your desired custom domain in the **Domain** field (e.g., `mcp.yourcompany.com`). Click **Next** to proceed to DNS configuration.

##### Step 2: DNS records

The wizard displays the DNS records you need to create with your domain registrar or DNS provider. These records verify domain ownership and route traffic to the Agen for Work MCP gateway. Follow the instructions to add the required records, then complete the configuration.

Click **Cancel** at any point to close the wizard without saving.

After adding DNS records, domain verification may take up to 24 hours depending on your DNS provider's propagation time. The custom domain becomes active once verification is complete.

#### Why use a custom domain

A custom domain provides several benefits:

- **Branding** — Present a professional, branded MCP gateway URL to your users and AI agent platforms (e.g., `mcp.yourcompany.com` instead of the auto-generated Frontegg URL)
- **Portability** — If you ever need to change infrastructure, your custom domain stays the same, avoiding the need to update AI agent configurations
- **Trust** — Users and security teams can easily verify that the MCP gateway belongs to your organization


### Allowed origins

The **Allowed origins** section is a collapsible panel below the Basic configuration section. It controls which web origins are permitted to make requests to your Agen for Work instance. This is a CORS (Cross-Origin Resource Sharing) configuration that restricts which domains can interact with your MCP gateway from browser-based applications.

Add origins that correspond to the web applications or AI agent platforms that need to communicate with your Agen for Work instance. Each origin should be a full URL including the protocol (e.g., `https://app.yourcompany.com`).

Only add origins that you trust. Misconfigured allowed origins can expose your MCP gateway to unauthorized cross-origin requests. If you are unsure which origins to add, consult your security team before making changes.

### Best practices

- **Copy the MCP Gateway URL early** — You will need the MCP Gateway URL when configuring AI agent platforms to connect to your Agen for Work instance. Copy it from the settings page during initial setup.
- **Set up a custom domain for production** — While the default Frontegg-generated URL works immediately, a custom domain improves branding and simplifies long-term management
- **Restrict allowed origins** — Only add the specific origins that need access to your MCP gateway. Avoid using wildcard patterns in production environments.
- **Keep the server name descriptive** — Use a name that clearly identifies the environment (e.g., "Acme Corp - Production" or "Agen for Work") so administrators can easily distinguish between instances


### Next steps

- [Getting started](/agen-for-work/getting-started/quickstart) — Return to the setup guide for a complete onboarding walkthrough
- [Connectors](/agen-for-work/sources/overview) — Configure the SaaS tools that connect through your MCP gateway
- [Monitoring](/agen-for-work/monitoring/overview) — Review audit logs for authentication and access events
- [Dashboard](/agen-for-work/overview/dashboard) — Monitor AI agent activity across your organization