/uipath-mcp-servers

name: uipath-mcp-servers
description: "UiPath Agent Gateway MCP servers (`uip agenthub mcp` / `uip agenthub mcp-tools`). Register, update, refresh tools, check connections, list, get, delete MCP servers: uipath (Orchestrator processes, agents, agentic processes, API workflows as tools), coded (published uipath-mcp Python server package), command (npx/uvx), remote (HTTP MCP URL, Relay), swagger (OpenAPI spec), platform (UiPath service operations, e.g. Test Manager); get the MCP URL a client connects to. For an agent that calls MCP tools→uipath-agents. For `uip mcp serve` (the uip CLI as an MCP server)→uipath-platform."
allowed-tools: Bash, Read, Write, Edit, Glob, Grep, AskUserQuestion

UiPath Agent Gateway MCP Servers

Agent Gateway is Orchestrator's hub for MCP servers and A2A agents: [about](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/about-agent-gateway), [MCP server types](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/mcp-server-types). This skill covers its MCP servers. The CLI group is named `agenthub`: `uip agenthub mcp` manages servers, `uip agenthub mcp-tools` manages their tools.

When to Use This Skill

**Servers — `uip agenthub mcp`, plus `uip agenthub platform-services` / `platform-tools` to look up `platform` names:**

• Create, update, delete, list or get an MCP server of any type ([Server Types](#server-types) says when to use each), and refresh its tools.
• Check whether a server works: its Integration Service connection and its tools ([Checking a Server](#checking-a-server)).
• Get the `McpUrl` an MCP client connects to.
• Find the UiPath services and tool names a `platform` server can expose.

**Tools — `uip agenthub mcp-tools`:**

• Bind Orchestrator processes, agents, agentic processes or API workflows as tools on a `uipath` server; edit or remove those tools.
• Add or remove tools on a `platform` server.
• List or get the tools of any server.

**Not this skill:** an agent that calls MCP tools → `uipath-agents`; running the `uip` CLI itself as an MCP server (`uip mcp serve`) → `uipath-platform`; A2A agents (`uip agenthub remote-a2a-agent --help`; no skill covers them). No skill covers writing the MCP server itself (`uipath-mcp` Python SDK, FastMCP, self-hosted runtime): see the [uipath-mcp quick start](https://uipath.github.io/uipath-python/mcp/quick_start/).

Critical Rules

These are the things the CLI does not advertise in `--help`.

1. **Pass slugs exactly as `mcp list` prints them.** On create the CLI does not validate the slug: without `--slug` it sends `--name` lowercased with other characters turned into `-`, which can still be under 3 or over 50 characters. The service requires `^[a-z0-9-]+$`, 3-50 characters (display name 3-100), so always pass `--slug`. The service reads a server by display name before slug, so `mcp get`, `mcp update`, `refresh-tools` and every `mcp-tools ... --mcp` refuse an argument that reads back another slug (`'<INPUT>' resolves to the MCP server '<SLUG>' …`). Never pass a display name or a GUID: `mcp delete` returns 404 for anything but the slug.

2. **Give every server command its folder.** Pass `--folder-key <FOLDER_KEY>` (a GUID) or `--folder-path <FOLDER_PATH>` (a name or `Parent/Child`), never both, as [Folder Context](#folder-context) lists per command. A 404 on a slug usually means the wrong folder: find the server with `mcp list --all-folders` and pass its `FolderKey`.

3. **Payloads are camelCase; everything else the CLI prints is PascalCase.** `--file` / `--body` keys must be the API's camelCase names (`name`, `slug`, `uri`, `headers`, `processKey`, `targetIdentifier`, …). `mcp create`, `mcp update` and the `mcp-tools` create / update verbs refuse a key that names a field in another case, also with `--dry-run` (``Payload keys differ from their fields only in case: `Name` should be `name`, …``): rename each key as listed. A key that names no field is dropped without an error. `mcp template` and `mcp-tools template` print a camelCase payload: edit it and send it as it is. `--print-schema` describes the payload in camelCase; it is not one. `mcp get`, `mcp list`, every create / update result, `mcp-tools list` and the `--dry-run` plan print PascalCase: put a copied value under the camelCase name `--print-schema` gives. `mcp get` also shows a remote server's URI as `Arguments` and remote / swagger headers as `EnvironmentVariables`.

4. **Set headers and environment variables with the flags.** Use `--header <NAME>=<VALUE>` on `remote` / `swagger` and `--env <KEY>=<VALUE>` on `command`, once per entry, on `create` and `update`. The CLI sends the newline-separated `Name:Value` / `KEY=VALUE` lines the service stores and refuses a repeated name or a value with a line break. A header value of exactly `%ASSETS/<ASSET_NAME>%` is replaced at call time by that Orchestrator asset's value, read from the server's folder. The asset must hold the whole value (e.g. `Bearer <TOKEN>`): `Bearer %ASSETS/<ASSET_NAME>%` is sent literally. Do NOT invent another syntax. Orchestrator gives the asset's value to Agent Gateway in the portal and to jobs, but not for a CLI login: `refresh-tools` from the CLI on such a server fails with 403 ([troubleshooting](references/troubleshooting-guide.md#refresh)). On `mcp update`, `--header` / `--env` replace every stored entry; keep a secret by passing `"<NAME>=****"` with the name spelled exactly as `mcp get` shows it with a `****` value.

5. **Confirm each mutation from its result.** `mcp create` / `mcp update` return the stored server, `mcp-tools create-resource` / `create-raw` / `update` the stored tool, and `delete` reports `Deleted: true` only after every delete succeeded. `mcp-tools enable` / `disable` return the server without its selection: confirm with `uip agenthub mcp-tools list --mcp <SLUG> --folder-path <FOLDER_PATH> --limit 1000 --output-filter "{Names: Items[].Name, Total: Total, Count: Count}" --output json` (unfiltered rows carry e