# Creating a remote MCP Server

> 1. In the **MCP Servers** page, select **Add MCP Server**. The **Add MCP Server** window is displayed.
2. From the top of the page, select the **Remote** type.
3. In the **Name** field, enter a name for the MCP Server.
   :::note
   The name is used as the actual slug for the **Preview URL**. Because of this, make sure that the name you provide respects the following validation criteria:
   * The name must be in
   accordance with the Regex rule: `/^[a-zA-Z0-0]+(?:[-]+[a-zA-Z0-0+)*$/`.
   * The value must have a
   minimum of 3 characters and a maximum of 50 characters.
   :::
4. In the **Preview URL**, enter a name to preview the full URL.

1. In the **MCP Servers** page, select **Add MCP Server**. The **Add MCP Server** window is displayed.
2. From the top of the page, select the **Remote** type.
3. In the **Name** field, enter a name for the MCP Server.
   :::note
   The name is used as the actual slug for the **Preview URL**. Because of this, make sure that the name you provide respects the following validation criteria:
   * The name must be in
   accordance with the Regex rule: `/^[a-zA-Z0-0]+(?:[-]+[a-zA-Z0-0+)*$/`.
   * The value must have a
   minimum of 3 characters and a maximum of 50 characters.
   :::
4. In the **Preview URL**, enter a name to preview the full URL.

The **Preview URL** uses the following format: `https://cloud.uipath.com/<OrganizationName>/<TenantName>/agenthub_/mcp/<FolderID>/<MCPServerName>`.

Make sure that you have the appropriate permissions to access the folder and create an MCP Server in the folder.

5. Add a **Description** of the MCP Server.
6. Add the **Remote URL** for the remotely deployed MCP Server.
7. Add the **Headers** for the MCP Server.

You can use this field for custom HTTP request headers that Orchestrator sends when communicating with the remote MCP Server endpoint. These headers are often used for authentication, such as API keys, or for custom configuration that the MCP Server expects in its requests.

:::note
* Use headers only if your remote MCP Server endpoint expects them for
secure communication. Leave this section empty if no additional authentication headers are required.
* When you add a header including terms like
`secret`, `api_key`, or `token`, the value is automatically masked in after saving. This is also applicable for assets of type **Secret**. The value remains securely stored and is only accessible to serverless robots running the MCP Server job.
:::
8. Select **Add**. The MCP Server is created and displayed on the **MCP Servers** page.