- Getting started
- Best practices
- Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Managing Robots
- Connecting Robots to Orchestrator
- Storing Robot Credentials in CyberArk
- Storing Unattended Robot Passwords in Azure Key Vault (read only)
- Storing Unattended Robot Credentials in HashiCorp Vault (read only)
- Storing Unattended Robot Credentials in AWS Secrets Manager (read only)
- Deleting Disconnected and Unresponsive Unattended Sessions
- Robot Authentication
- Robot Authentication With Client Credentials
- Configuring automation capabilities
- Solutions
- Audit
- Settings
- Registry
- Cloud robots
- Automation Suite Robots
- Folders Context
- Processes
- Jobs
- Apps
- Triggers
- Logs
- Monitoring
- Indexes
- Queues
- Assets
- Connections
- Business Rules
- Storage Buckets
- MCP Servers
- Orchestrator testing
- Resource Catalog Service
- Integrations
- Troubleshooting
Orchestrator user guide
- In the MCP Servers page, select Add MCP Server. The Add MCP Server window is displayed.
- From the top of the page, select the Remote type.
- 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.
- The name must be in
accordance with the Regex rule:
- 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.
- Add a Description of the MCP Server.
- Add the Remote URL for the remotely deployed MCP Server.
- 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.
To avoid hardcoding secrets in headers, reference Orchestrator assets using the %ASSETS/AssetName% syntax as the full header value. For example, use Authorization: %ASSETS/RemoteBearerToken% or X-Api-Key: %ASSETS/MyApiKey%.
If the remote endpoint expects a prefix such as Bearer, store the full header value in the asset. For example, store Bearer <token> in the RemoteBearerToken asset, then configure the header as Authorization: %ASSETS/RemoteBearerToken%.
Remote header asset references are resolved through Orchestrator using the caller's identity and the MCP Server folder context. This works without a robot or robot key. For details, check Using Orchestrator Assets in MCP Servers.
- 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, ortoken, the value is automatically masked after saving.
- Select Add. The MCP Server is created and displayed on the MCP Servers page.