- 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
Feature availability depends on the cloud offering that you use. For details, refer to the Feature availability page.
Model Context Protocol (MCP) is an open standard for connecting AI assistants and agents to the systems where data lives, including content repositories, business tools, and development environments. It defines how context and tools are exposed to AI systems, so that models can discover and invoke capabilities without requiring custom, point-to-point integrations.
For more information about the protocol, check the Model Context Protocol documentation.
The UiPath Platform provides native support for MCP, enabling MCP Servers to be built, hosted, or connected as part of agentic workflows. Through MCP, UiPath artifacts (RPA workflows, agents, API workflows, agentic processes, and Integration Service activities) can be exposed as tools that AI models can consume securely.
MCP Server types
UiPath supports five MCP Server types, each suited to a different scenario. The following table compares the types at a glance. For details, see the dedicated page for each type.
| Server type | Hosting | Setup | Typical use case |
|---|---|---|---|
| UiPath MCP Server | UiPath Platform | Artifact selection in Orchestrator | Exposing UiPath artifacts as MCP tools |
| Remote MCP Server | External (public internet or on-prem via UiPath Relay) | Remote URL and headers in Orchestrator | Connecting to MCP Servers managed outside UiPath |
| Command MCP Server | UiPath Serverless | Command definition in Orchestrator | Running an existing MCP package without repackaging |
| Coded MCP Server | UiPath Serverless | .nupkg published to Orchestrator | Building a custom Python MCP Server on UiPath |
| Self-Hosted MCP Server | User-controlled infrastructure | Local registration via uipath run | Running a Coded or Command MCP Server on your own infrastructure |
Command, Coded, and Self-Hosted servers share a common runtime, configuration format, and transport. For details, check MCP Server shared foundation.
When connecting an MCP Server that is based on external code or commands, use a trusted provider.
MCP Servers page fields
The following table describes the fields available on the MCP Servers page in Orchestrator:
| Field | Description |
|---|---|
| Name | The display name of the MCP Server. |
| Type | The type of the MCP Server: UiPath, Remote, Command, Coded, or Self-Hosted. |
| Status | The current operational status of the MCP Server. |
| Description | A short description of the MCP Server. |