About MCP Servers
note
Feature availability depends on the cloud offering that you use. For details, refer to the Feature availability page.
Model Context Protocol (MCP) is a protocol for communicating and sharing context between LLMs or agents and applications.
The UiPath Platform offers full MCP support, enabling you to build or bring an MCP Server into your automation workflows. You can choose between the following MCP Server types:
- UiPath: Expose UiPath artifacts as tools via MCP. You can build a UiPath MCP Server directly from the platform interface. Tools can include UiPath artifacts such as RPA workflows, agents, API workflows, and agentic processes.
- Coded (Preview): Host a custom-coded MCP Server. You can bring a coded MCP Server to the UiPath Platform in a similar way you can build and deploy coded agents. The code is stored, versioned, and distributed through the UiPath internal package management system. This allows tighter control, easier updates, and native integration with Orchestrator.
- Command (Preview): Bring an MCP Server from an external package feed via command. This allows you to integrate an existing MCP Server from an external package feed using a platform-supported command, such as NPM for Node.js or PyPI for Python. Instead of using a UiPath package, the command starts an external process that hosts the MCP Server.
- Remote: Connect to remote MCP Servers outside UiPath via secure tunneling. This setup allows the exposure of multiple MCP Servers, each authorized with different providers, through the UiPath Platform.
note
If you are using an external MCP Server, based on external code or commands, you need to make sure a trusted provider is used.
The following table describes the fields available on the MCP Servers page:
| Field | Description |
|---|---|
| Name | The display name of the MCP Server. |
| Type | The type of the MCP Server:
|
| Status | The current operational status of the MCP Server. |
| Description | A short description of the MCP Server. |