orchestrator
latest
false
- 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
Last updated May 19, 2026
Once an MCP Server is configured in Orchestrator, it is accessible through a standard URL. This URL is used by both UiPath agents and external MCP clients to connect to the server.
URL format
The URL format is:
https://cloud.uipath.com/{org_name}/{tenant_name}/agenthub_/mcp/{folder_key}/{server_slug}
https://cloud.uipath.com/{org_name}/{tenant_name}/agenthub_/mcp/{folder_key}/{server_slug}
The placeholders represent the following values:
| Placeholder | Description |
|---|---|
{org_name} | The UiPath organization name. |
{tenant_name} | The Orchestrator tenant name. |
{folder_key} | The unique key of the Orchestrator folder where the MCP Server is configured. |
{server_slug} | The MCP Server slug, derived from the server name at creation time. |
Finding the URL for a configured server
The URL for a specific MCP Server is available in the server details panel on the MCP Servers tab of its Orchestrator folder.