MCP Server types

Servidores MCP da UiPath

The UiPath MCP Server exposes UiPath artifacts (RPA workflows, agents, API workflows, agentic processes, and Integration Service activities) as MCP tools. Use it when automation logic already exists in UiPath and needs to be made available to AI models.

This server type is built and managed directly within the UiPath Platform, providing native integration, simplified deployment, and centralized governance through Orchestrator.

Como funciona

Configuration happens entirely in Orchestrator, in the folder-scoped MCP Servers tab. Users select the artifacts to expose as tools and save the server. No packaging, code, or external process is required.

Once configured, the server is reachable through the standard UiPath MCP Server URL. For the URL format, check Getting the MCP Server URL.

Autenticação

UiPath MCP Servers use the standard MCP Server authentication model. For details on the supported methods and required permissions, check MCP Server authentication.

One additional constraint applies: tools backed by Integration Service activities require user-context tokens. These tools work with Interactive Login or the MCP OAuth flow, but not with Personal Access Tokens or external application client credentials.

Configuração

For step-by-step instructions, check Creating UiPath MCP Servers.

Servidores MCP remotos

The Remote MCP Server lets UiPath connect to MCP Servers hosted outside the UiPath Platform. Orchestrator acts as a proxy, forwarding MCP requests to an external URL that you provide.

Remote MCP Server covers two scenarios:

• Third-party services managed externally: for example, Atlassian MCP or Stripe MCP, reached over the public internet.
• On-prem MCP Servers that must be reached from UiPath Cloud without opening inbound ports. In this scenario, UiPath Relay establishes a long-lived outbound tunnel from your network to UiPath Cloud, and the Remote MCP Server is configured against the Relay URL. No VPN, public exposure, or inbound connectivity is required.

In both scenarios, the remote endpoint must speak Streamable HTTP.

Como funciona

Configuration happens in Orchestrator by providing the remote URL and an optional set of custom HTTP headers. No UiPath package, code, or process is involved.

When a tool is invoked, Orchestrator forwards the call to the remote URL along with any custom headers that are configured. UiPath-specific headers, including the bearer token, are not forwarded to the remote server, so your UiPath identity never reaches it. Custom headers with values containing terms such as secret, api_key, or token are masked in the UI after saving.

Autenticação

Remote MCP Servers use the standard MCP Server authentication model. All four supported authentication methods work with this type. For details, check MCP Server authentication.

Configuração

For step-by-step instructions, check Creating a remote MCP Server.

Servidores MCP de comando

The Command MCP Server lets UiPath integrate an existing MCP Server from an external package feed, such as NPM (npx) or PyPI (uvx), using a platform-supported command. Use it to run pre-existing or third-party MCP Servers without repackaging them as UiPath artifacts.

Como funciona

Command MCP Servers run on UiPath Serverless and support both Python and JavaScript/Node.js MCP Servers. Each server maintains one session per job, with a maximum job duration of 15 minutes.

Configuration happens in Orchestrator by providing the command and its arguments. No UiPath package, code, or process definition is required. The configuration is stored as an entry in an mcp.json file. For example:

{
  "servers": {
    "filesystem-server": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-filesystem", "/tmp"]
    }
  }
}

A Command MCP Server shares the same runtime and configuration format as Coded and Self-Hosted MCP Servers. For details, check MCP Server shared foundation.

Environment variables and secrets

Environment variables are configured directly on the MCP Server in Orchestrator and are stored encrypted. Orchestrator Assets can be referenced for secrets management using the %ASSETS/AssetName% syntax. For details, check Using Orchestrator Assets in MCP Servers.

Autenticação

Command MCP Servers use the standard MCP Server authentication model. Each tool call starts a Serverless job, so callers need both the MCPServers.View and Jobs.Create permissions. For details, check MCP Server authentication.

Configuração

For step-by-step instructions, check Creating command MCP Servers.

Servidores MCP codificados

A Coded MCP Server is a Python MCP Server written using the FastMCP framework from the mcp Python package, then packaged and published to Orchestrator as a UiPath NuGet artifact (.nupkg). The uipath-mcp library provides the runtime layer that integrates the server with the UiPath Platform.

Use this type when a custom MCP Server must be built and hosted on UiPath, with code stored, versioned, and distributed through the UiPath package management system.

Como funciona

Coded MCP Servers run on UiPath Serverless. Each server maintains one session per job, with a maximum job duration of 15 minutes. Active tool calls are subject to a connection timeout of approximately 3.5 minutes, and idle sessions are terminated after approximately 6–7 minutes of inactivity.

To deploy a Coded MCP Server, the server code is packed and published to Orchestrator using the uipath-mcp CLI, then the Coded MCP Server is configured in Orchestrator in the same folder where the package is deployed. The server is referenced by an mcp.json entry:

{
  "servers": {
    "math-server": {
      "type": "stdio",
      "command": "python",
      "args": ["server.py"]
    }
  }
}

Like a Command MCP Server, a Coded server is defined by an mcp.json entry. The difference is that a Coded server runs code from a UiPath NuGet artifact published to Orchestrator, instead of pulling a package from an external feed.

A Coded MCP Server shares the same runtime, configuration format, and transport as Command and Self-Hosted MCP Servers. For details, check MCP Server shared foundation.

Environment variables and secrets

For Coded MCP Servers, environment variables are not configured on the MCP Server entity itself. Instead, they are set on the process in Orchestrator, in Settings > Environment Variables, and are stored encrypted. Orchestrator Assets can be referenced for secrets management using the %ASSETS/AssetName% syntax. For details, check Using Orchestrator Assets in MCP Servers.

Autenticação

Coded MCP Servers use the standard MCP Server authentication model. Each tool call starts a Serverless job, so callers need both the MCPServers.View and Jobs.Create permissions. For details, check MCP Server authentication.

Configuração

For step-by-step instructions, see Creating coded MCP Servers. For implementation details and a getting-started guide, check the uipath-mcp quick start.

Self-hosted MCP Servers

The Self-Hosted MCP Server runs on infrastructure controlled by the user, local machines, on-premises servers, or private cloud environments, while connecting to UiPath for governance and discoverability. Use it when the MCP Server needs to access local resources that aren't reachable from cloud infrastructure, or when policy requires the runtime to live on customer-owned hardware.

Como funciona

A Self-Hosted MCP Server cannot be configured through the Orchestrator UI. Instead, it registers itself with UiPath when started locally. Unlike Coded and Command MCP Servers, a Self-Hosted runtime instance supports multiple concurrent sessions, with random distribution when several sessions connect to the same slug. The server lifecycle is fully controlled by you.

A Self-Hosted MCP Server shares the same runtime, configuration format, and transport as Command and Coded MCP Servers. For details, check MCP Server shared foundation.

Registering the server

Before starting the server, the runtime needs to know which Orchestrator folder to register it under. Two registration paths are supported, depending on the authentication method:

• With interactive authentication (uipath auth): UIPATH_FOLDER_PATH is set to the folder path. The runtime resolves it to a folder key automatically.
• With client-credential authentication: UIPATH_FOLDER_KEY is set directly to the folder GUID, since the folder-resolution API does not support client credentials.

Example registration commands:

# Interactive auth
export UIPATH_FOLDER_PATH=<your-folder-path>
uipath run my-mcp

# Client-credential auth
export UIPATH_FOLDER_KEY=<your-folder-key>
uipath run my-mcp

Once registered, the server appears in Orchestrator and is reachable through the standard MCP endpoint URL. For the URL format, check Getting the MCP Server URL.

Autenticação

Authentication operates on two layers for Self-Hosted MCP Servers:

• The developer's uipath auth token (or client credentials) registers the runtime.
• The caller's bearer token authenticates each tool call.

The caller's token never reaches the local runtime. UiPath validates it in the cloud and only forwards the MCP protocol message.

For details on the supported authentication methods and required permissions, check MCP Server authentication.

Configuração

For implementation details and a getting-started guide, check the uipath-mcp quick start.