- 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
Agent Gateway, the hub in Orchestrator for registering and managing MCP Servers and A2A agents in both directions.
Agent Gateway is available in preview.
Agent Gateway is the area in Orchestrator where you register and manage the agents and servers that connect the UiPath Platform to the outside world, using two open protocols: Model Context Protocol (MCP) and Agent2Agent (A2A). It replaces the former standalone MCP Servers area, which now lives inside Agent Gateway alongside a new A2A Agents area.
Two directions of communication
Agent Gateway supports communication in both directions:
- Outbound (UiPath to external): lets you connect external MCP servers and A2A agents, so they can be orchestrated alongside UiPath automations and agents.
- Inbound (external to UiPath): exposes UiPath capabilities, such as automations, API workflows, and agents, to external AI assistants and agents.
Registered once, available everywhere
Every MCP server and A2A agent that you register in Agent Gateway, including ones hosted outside the UiPath Platform, becomes a resource on the platform. Once registered, you can use it in any orchestration or agentic layer, such as Maestro flows, Maestro BPMN processes, or agents built with Agent Builder, without additional setup for each consumer.
MCP and A2A
Agent Gateway is organized by protocol, because the protocol determines how discovery, registration, authentication, and communication work:
- MCP exposes capabilities as tools that agents can discover and call.
- A2A supports multi-turn conversations between agents.
For inbound scenarios, the setup differs between the two protocols:
- A2A: every UiPath conversational agent speaks A2A natively and already has an agent card. No setup is needed.
- MCP: exposing UiPath artifacts as tools requires creating a UiPath MCP Server, where each tool is linked to a process.
For details on MCP, check About MCP Servers. For details on A2A, check About A2A Agents. To register your first agent or server, check Outbound (UiPath to external) or Managing MCP Servers.