- 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
MCP clients that implement the MCP Authorization specification can authenticate automatically through OAuth. The client handles the full discovery and authorization flow, so no manual token management is needed.
This authentication method is suitable for IDE-based MCP clients such as VS Code with GitHub Copilot.
Prerequisites
- You have an MCP client that supports the MCP Authorization specification.
- You have the UiPath MCP Server URL.
- You have an account with the Automation User, Automation Developer, or Folder Administrator role in the folder containing the MCP Server.
Configure VS Code or GitHub Copilot
-
Add the MCP Server to your VS Code settings or
mcp.jsonfile:{ "servers": { "my-server": { "type": "http", "url": "https://cloud.uipath.com/{org}/{tenant}/agenthub_/mcp/{folderKey}/{slug}" } } }{ "servers": { "my-server": { "type": "http", "url": "https://cloud.uipath.com/{org}/{tenant}/agenthub_/mcp/{folderKey}/{slug}" } } } -
Open Copilot Chat, select Configure tools, and select your server.
-
The browser opens. Log in to UiPath.
Result
The MCP client is authorized to call the MCP Server. Authorization persists across sessions because the IDE handles token refresh automatically.
Other MCP clients
Support for additional MCP clients (such as Claude Desktop or Cursor) is being progressively added. For clients that are not yet supported through OAuth, use a personal access token with a Bearer token header instead.