# MCP connector authentication

> Connect UiPath to a remote MCP server by entering the server URL and the authentication credentials the server requires for the selected authentication type.

The MCP connector supports four authentication types. Select the one your
Model Context Protocol (MCP) server requires, and complete the steps below to create the connection.

## Prerequisites

To create an MCP connector connection, you need the remote MCP server URL and the credentials the server expects. The required fields depend on the Authentication Type you select:

* **OAuth 2.0 Authorization code**
  * **Base URL** — the base URL of your MCP server, for example `https://mcp.example.com/mcp`.
  * **Client ID** — the Client ID issued by the MCP server's OAuth provider when you registered your application.
  * **Client secret** — required for the Authorization code flow.
  * **Authorization URL** — the full authorization endpoint URL, for example `https://mcp.example.com/oauth/authorize`.
  * **Token URL** — the full token endpoint URL, for example `https://mcp.example.com/oauth/token`.
  * **Scope** — the OAuth scopes required for the MCP server's tools, matching what you registered with the provider.
* **OAuth 2.0 Authorization code with PKCE (Proof Key for Code Exchange)**
  * **Base URL** — the base URL of your MCP server, for example `https://mcp.example.com/mcp`.
  * **Client ID** — the Client ID issued by the MCP server's OAuth provider when you registered your application.
  * **Authorization URL** — the full authorization endpoint URL, for example `https://mcp.example.com/oauth/authorize`.
  * **Token URL** — the full token endpoint URL, for example `https://mcp.example.com/oauth/token`.
  * **OAuth2 PKCE code challenge method** — defaults to `S256`; use `plain` only when your MCP server does not support `S256`.
  * **Scope** — the OAuth scopes required for the MCP server's tools, matching what you registered with the provider.
* **OAuth 2.0 Client Credentials**
  * **Base URL** — the base URL of your MCP server, for example `https://mcp.example.com/mcp`.
  * **Client ID** — the Client ID issued by the MCP server's OAuth provider when you registered your application.
  * **Client secret** — required for the Client Credentials flow.
  * **Token URL** — the full token endpoint URL, for example `https://mcp.example.com/oauth/token`.
  * **Scope** — the OAuth scopes required for the MCP server's tools, matching what you registered with the provider.
* **Personal Access Token**
  * **Base URL** — the base URL of your MCP server, for example `https://mcp.example.com/mcp`.
  * **Personal access token** — paste the full Authorization header value, including any prefix the MCP server expects (typically `Bearer `), for example `Bearer mytoken`.

Refer to your MCP server provider's documentation for the exact values.

## Add the MCP connection

1. Select Orchestrator from the product launcher.
2. Select a folder.
3. Navigate to the **Connections** tab.
4. Select **Add connection**.
5. To open the connection creation page, select the MCP connector from the list. You can use the search bar to find the connector.
6. Under **Folder in which connection is stored**, confirm or change the folder where the connection is saved.
7. Select the **Authentication Type** (for example, Personal Access Token or one of the OAuth 2.0 flows).
8. Enter the required credentials for the selected authentication type.
   * For Personal Access Token, enter the **Base URL** of your MCP server (for example, `https://mcp.example.com/mcp`), then paste the full Authorization header value into **Personal access token**, including any prefix the MCP server expects (typically `Bearer `).
   * For the OAuth 2.0 flows, provide the client credentials and authorization/token endpoints, then complete the authorization prompt if required.
9. Select **Connect**.

Your MCP connection has now been added and is available for use in UiPath Studio or Studio Web.