- 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
Command, Coded, and Self-Hosted MCP Servers all run code-based MCP Server implementations and share a common foundation. This page describes the runtime, transport, and configuration format that they have in common.
Runtime library
The shared runtime is built on uipath-mcp-python, an open-source Python library that provides the runtime, SDK, and CLI for building and running MCP Servers on the UiPath Platform. It is built on top of the uipath-python library.
Transport
Communication with the platform flows over Streamable HTTP. A single process handles multiple sessions concurrently, each on its own connection, and the same transport is exposed to external MCP clients. This is the recommended path for new MCP Servers.
The older stdio transport, which starts a new process per session, is deprecated and retained only for backwards compatibility with MCP Servers built before Streamable HTTP support was introduced.
Configuration format
Each MCP Server is described by an mcp.json configuration file, which defines the servers available in the runtime environment: their type, entry point, and arguments. The format is shared across Command, Coded, and Self-Hosted MCP Servers.