- Primeros pasos
- Mejores prácticas
- Tenant
- Acerca del contexto de tenant
- Buscar recursos en un tenant
- Gestionar robots
- Conexión de los robots a Orchestrator
- Almacenar credenciales de robots en CyberArk
- Almacenar contraseñas de robots desatendidos en Azure Key Vault (solo lectura)
- Almacenar las credenciales de robots desatendidos en HashiCorp Vault (solo lectura)
- Almacenamiento de credenciales de Unattended Robot en AWS Secrets Manager (solo lectura)
- Eliminar sesiones desconectadas y sin respuesta no atendidas
- Autenticación de Robot
- Autenticación de robots con credenciales de cliente
- Configurar las capacidades de automatización
- Soluciones
- Auditoría
- Configuración
- Registro
- Notificaciones
- Contexto de carpetas
- Procesos
- Trabajos
- Apps
- Desencadenadores
- Registros
- Supervisión
- Índices
- Colas
- Activos
- Sobre los activos
- Gestión de Activos en Orchestrator
- Gestión de Activos en Studio
- Almacenar activos en Azure Key Vault (solo lectura)
- Almacenamiento de activos en HashiCorp Vault (solo lectura)
- Almacenamiento de activos en AWS Secrets Manager (solo lectura)
- Almacenamiento de activos en Google Secret Manager (solo lectura)
- Conexiones
- Reglas empresariales
- Depósitos de almacenamiento
- Agent Gateway
- Pruebas de Orchestrator
- Servicio de catálogo de recursos
- Integraciones
- Solución de problemas
Create a Platform MCP Server in Orchestrator by selecting a UiPath service and the operations to expose as tools.
This functionality is in preview.
A Platform MCP Server exposes a first-party UiPath service as a curated set of MCP tools. Instead of exposing every operation the service's API offers, you choose which ones become tools, and that choice is saved with the server.
Requisitos previos
- The folder-level Create permission for MCP Servers.
Create a Platform MCP Server
-
In Agent Gateway > MCP Servers, select the Add MCP Server menu.
-
Under UiPath hosted, select Platform.
-
From Type, select the UiPath service to expose.
Nota:The service can't be changed after the server is created. To expose a different service, create another server.
-
Enter a Name. This is the display name shown in the server list.
-
Enter a Slug.
Nota:The slug accepts lowercase letters, numbers, and hyphens only, and must be between 3 and 50 characters. It becomes the last segment of the server URL and can't change after the server is created.
Preview URL fills in on its own once you have entered a name, shows the full address the server will have, and is read-only.
-
Optionally, enter a Description of up to 500 characters.
-
Select the operations to expose as tools. The list appears once you have chosen a service, and is grouped by the categories that the service's API declares, so related operations appear together.
Nota:To expose every operation the service offers, including ones added later, enable All tools. Your earlier selection is kept but ignored while the toggle is on, and turning it off restores it. Select Refresh to re-read the service's API and rebuild the list.
-
Optionally, expand Guardrails and configure them.
-
Selecciona Añadir.
Result: The server is created and reachable immediately; no package, code, or process is involved. Select Copy URL on the server's row to get its address:
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 request UiPath makes to the service has a 30-second timeout, and the tool call is held open until it returns. Operations that take longer aren't a good fit for this server type.
Calls appear in the Runs tab on the server, and the trace context carries through to the service, so the service's own spans appear nested under the call.
For how callers authenticate and which permissions they need, check MCP Server authentication. For what this server type is and how it compares with the others, check MCP Server types.