Table of Contents

MCP Servers

Learn how to register Model Context Protocol (MCP) servers so agent tools can call them.

Overview

An MCP server is an API endpoint configuration with the MCP Server category. It stores the server URL, timeout, authentication, and HTTP headers in one place. MCP tools in the Tool Library and on agents reference the MCP server by name instead of storing their own URL and secrets, so you can rotate a key or change a URL once for every tool that uses it.

The MCP Servers page shows only MCP server endpoints. The same resources also appear on Platform > API Endpoints with the MCP Server category.

To open the page, in the sidebar select Agents > MCP Servers.

MCP Server List

The list shows every MCP server endpoint, sorted by display name, with 10, 25, 50, or 100 rows per page.

Column Description
Name The display name (or the resource name when no display name is set)
Provider The endpoint provider. Use the column filter to show one provider.
Actions View JSON definition, edit, clone, and delete

Use Search MCP servers to filter by display name or resource name, and the refresh button to reload the list.

Icon Action
</> View JSON definition opens the endpoint resource JSON
Pencil Opens Edit MCP Server. Disabled without write permission on the endpoint.
Clone Opens Create MCP Server prefilled with the endpoint's settings and an empty name
Trash Deletes the MCP server after confirmation. Disabled without delete permission.

Creating an MCP Server

  1. On the MCP Servers page, select Create MCP Server.
  2. Complete the sections described below.
  3. Select Create MCP Server. The portal saves the endpoint and returns to the list.

To start from an existing server, select its clone icon instead. Cloning copies every setting except the name.

Identity

Field Description
Resource name Letters and numbers with dashes and underscores only. The portal checks availability (✔️ available, ❌ taken). Cannot be changed later.
Display name Shown in lists and pickers, including the tool editor's MCP Server Endpoint list. Defaults to the resource name.
Description Optional description of the server's purpose

Classification

Field Description
Provider The platform or service that hosts the server. Generic works for most MCP servers.

The category is fixed to MCP Server on this page, and there is no subcategory.

Connection

Field Description
Endpoint URL The MCP server URL, for example https://mcp.example.com/mcp. Required.
API version Optional. Not used by most MCP servers.
Timeout (seconds) Connection timeout used by MCP tools that reference this server. Defaults to 60.
Status endpoint Optional relative path to a health endpoint
Project, Location Optional provider-specific values. Leave blank for MCP servers.

Authentication

Authentication type What to configure
API Key Put the key in an HTTP header (see HTTP headers), for example x-api-key or Authorization.
Azure Identity Enter the Scope for the server, for example api://FoundationaLLM-Core/.default. Required for this type.
Google Service Account Available in the list, but MCP servers do not store authentication parameters other than the Azure Identity scope. Use HTTP headers for credentials.

With Azure Identity, the platform acquires a Microsoft Entra ID access token for the scope using its own identity (the LangChain API at runtime, and the Management API for tool discovery) and sends it as a bearer token. These calls use the sessionless 2026-07-28 MCP protocol revision, so the server must support it. The identity that runs the platform services must be allowed to call the server.

HTTP headers

Add headers that are sent with every request to the server. Select + Add Header, enter the Key, and choose a Source:

Source Value
New Value Enter the value. When the header name looks like a secret (it contains api-key, auth, authorization, token, secret, password, credential, or bearer), the value is stored in Key Vault through an App Configuration key when you save; the Configuration Key column shows "Auto-generated on save". Other values are stored on the endpoint.
Existing Config Search for and select an existing App Configuration key. The value is read at runtime.
System / runtime context Choose a value resolved per call: User identity (X-USER-IDENTITY), Session ID (X-FLLM-SESSION-ID), or Agent identity (X-AGENT-OBJECT-ID).

Use the eye icon to show or hide a value, and the × icon to remove a header.

Tip: Many first-party MCP servers, such as Genesis and memory servers, need X-USER-IDENTITY set to the User identity runtime value so they act on behalf of the signed-in user.

URL exceptions are not available for MCP servers.

Editing an MCP Server

  1. Select the pencil icon for the server.
  2. On Edit MCP Server, change the settings. The resource name is shown under the display name and cannot be changed.
  3. Select Save Changes. The page stays open and reloads the saved endpoint.

Changes apply to every agent tool that references the server the next time the tool runs.

Deleting an MCP Server

  1. Select the trash icon for the server.
  2. Confirm in the Delete MCP Server dialog.

Warning: Agent tools that reference a deleted MCP server fail at runtime. Point those tools at another server first.

How Agent Tools Use MCP Servers

  1. In the tool editor (on Agents > Tools or in the agent editor's Tools tab), under Connection, select Registered endpoint and choose the server in MCP Server Endpoint. Only MCP Server endpoints are listed.
  2. Under Tool Selection and Configuration, select List Tools. The Management API connects to the server with the server's URL, headers, and authentication and returns the server's tools.
  3. Pick a tool and select Configure to fill in the MCP tool name, description, and arguments, or enable Intelligent Execute.
  4. Save the tool and the agent. The agent stores a reference to the MCP server, not a copy of its URL or secrets.

At runtime, the MCP Client tool resolves the referenced server and uses its URL, headers, timeout, and authentication.

Tools configured with an Inline URL can be moved to a registered server with Convert to registered endpoint in the tool editor. See Tools.

Built-in MCP tools default to well-known server names. For example, the Perplexity tools reference Platform-MCP-Perplexity. Create a server with that resource name, or select a different server on each tool.

For developer-level details, such as running MCP servers locally and debugging the MCP Client tool, see Using MCP Servers via the MCP Client Tool.