Register an MCP server

Connect an MCP server to your tenant, select tools, and configure sync behavior using the New MCP Server wizard.

Registering an MCP server connects it to your tenant and makes its tools available to add to AiseraGPT applications. Registration is a three-step wizard: connect and authenticate, select tools, then configure the server name and sync behavior.

Before you begin

• You need the endpoint URL of the MCP server you want to connect.

• If authenticating with Bearer Token or OAuth, have your credentials ready before starting the wizard.

• You must be an administrator for your tenant.

Open the New MCP Server wizard

1. Go to Settings > MCP Servers.

2. Select + New MCP Server in the top right.

The New MCP Server wizard opens at Step 1 of 3: Connect.

Step 1: Connect

Configure the connection and authentication for the MCP server.

1. Enter the Endpoint URL of your MCP server.

2. Select the Authentication Type. The fields that appear depend on your selection.

None

No additional fields appear. The Aisera Platform connects to the server URL directly without sending tokens or credentials. Use this only for public or non-sensitive endpoints. Do not use this authentication type for servers that access private data or perform write operations.

Bearer Token

A static API key or token is passed with every request. This is the simplest authenticated mode and is well-suited for service accounts because a single token is shared across all calls.

Enter your Bearer Token. This is the API key or secret token issued by the MCP server provider. Treat this value as a secret: store it securely and rotate it if it is compromised.

OAuth

OAuth is the standard authorization framework used by most production MCP servers. The OAuth flow is completed once and the Aisera Platform reuses the resulting access token for all requests from your tenant.

Select an OAuth Client Registration method:

Manual (pre-registered client) Use this when you have registered an OAuth application with the MCP server provider in advance and received a client ID and secret. Configure the following fields:

• OAuth Client ID (required): The client_id issued by the provider at app registration.

• OAuth Client Secret (required): The client_secret paired with the client ID. Leave blank for public clients using Proof Key for Code Exchange (PKCE) only.

• Authorization URL (required): The provider's authorization endpoint (for example, https://provider.com/oauth/authorize). Must be provided together with Access Token URL.

• Access Token URL (required): The provider's token endpoint (for example, https://provider.com/oauth/token). Must be provided together with Authorization URL.

• Well-known URL (optional): The /.well-known/openid-configuration URL of the authorization server. Used only when Authorization URL and Access Token URL are not both provided. If both explicit endpoint URLs are present, this field is ignored.

Auto (DCR) Use this when the MCP server supports Dynamic Client Registration (DCR, RFC 7591) and you do not have pre-registered credentials. The Aisera Platform registers itself with the authorization server at connection time and receives credentials dynamically. You do not need a client ID or secret in advance.

• Well-known URL (optional): A custom discovery URL if the server uses a non-standard path for its OAuth metadata. If left blank, the Aisera Platform attempts to discover the authorization server from the MCP server's base URL.

Authorization URL and Access Token URL must both be provided or both be omitted. Providing only one is a validation error. If only one endpoint is known, use the Well-known URL field and let the Aisera Platform discover the other.

1. Confirm the Mode and Transport Type selections. These fields are pre-set. See the configuration reference for details on the available options.

2. If your server requires custom headers, enter a JSON object in the Customer Headers field (for example, {"X-API-Key": "your-key"}). The reserved headers Authorization and Proxy-Authorization are not permitted as keys.

3. Select Verify Connection.

   • If the connection succeeds, the Next button becomes active.

   • If the connection fails, an error message appears and the button changes to Retry. Correct the connection details and select Retry before proceeding.

Step 2: Select tools

After connecting, the Aisera Platform discovers the tools available on the MCP server. While discovery runs, a Connecting and discovering tools message appears.

When discovery completes, a list of available tools is displayed. Each row shows the tool name and its discovered description.

1. Select the checkbox next to each tool you want to make available for your tenant.

2. Use the search bar to filter tools by name if needed.

3. Select Next when you have made your selections.

Step 3: Details and sync

Configure the server name and how the Aisera Platform keeps its tool list in sync with the upstream server.

1. Confirm or edit the Server Name. This is the name the server appears under in the Aisera UI. It is auto-filled from the connected server.

2. Optionally, enter a Description to document what the server is for.

3. Configure sync behavior: Auto Re-sync Tools (on by default) When enabled, the Aisera Platform automatically re-syncs the tool list from the server on a schedule. Toggle on to reveal the Re-sync Frequency field.

   • Re-sync Frequency (required when Auto Re-sync is on): Select the interval (Hourly, Daily, Weekly, or Monthly) and the time of day for the sync.

4. Optionally, enable Pause the server after 3 consecutive sync failures. When enabled, the server is automatically paused if three consecutive syncs fail. This is off by default.

5. Select Finish to complete registration.

The server now appears on the MCP Servers page and its tools are available to add to AiseraGPT applications.