- Démarrage
- Meilleures pratiques
- Modélisation de l'organisation dans Orchestrator
- Meilleures pratiques d'automatisation
- Optimisation de l'infrastructure Unattended à l'aide de modèles de machine
- Organisation des ressources avec des balises
- Exportation des grilles dans l'arrière-plan
- Appliquer la gouvernance de la connexion Integration Service au niveau de l'utilisateur
- Locataire
- À propos du contexte du locataire
- Recherche de ressources dans un locataire
- Gestion des Robots
- Connexion des Robots à Orchestrator
- Enregistrement des identifiants du Robot dans CyberArk
- Stockage des mots de passe de l’Unattended Robot dans Azure Key Vault (lecture seule)
- Stockage des informations d’identification de l’Unattended Robot dans HashiCorp Vault (lecture seule)
- Stockage des informations d'identification du robot Unattended dans AWS Secrets Manager (lecture seule)
- Suppression des sessions Unattended déconnectées et qui ne répondent pas
- Authentification du Robot
- Authentification du Robot avec les informations d'identification du client
- Configurer les capacités d’automatisation
- Solutions
- Audit
- Paramètres
- Registre
- Notifications
- Contexte des dossiers
- Processus (Processes)
- Tâches (Jobs)
- Apps
- Déclencheurs (Triggers)
- Journaux (Logs)
- Surveillance
- Index
- Files d'attente (Queues)
- Actifs
- À propos des actifs
- Gestion des actifs dans Orchestrator
- Gestion des actifs dans Studio
- Stockage des ressources dans Azure Key Vault (lecture seule)
- Stockage des ressources dans HashiCorp Vault (lecture seule)
- Stockage des ressources dans AWS Secrets Manager (lecture seule)
- Stocker des ressources dans Google Secret Manager (lecture seule)
- Connexions
- Règles métier
- Compartiments de stockage
- Agent Gateway
- Tests d'Orchestrator
- Service de catalogue de ressources
- Intégrations
- Résolution des problèmes
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.
Prérequis
- 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.
Remarque :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.
Remarque :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.
Remarque :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.
-
Sélectionnez Ajouter.
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.