UiPath MCP Python SDK
A Python SDK that enables hosting local MCP servers on UiPath Platform.
Check out our samples directory to explore various MCP server implementations. You can also learn how to pack and host binary servers written in languages like Go within UiPath.
Installation
pip install uipath-mcp
using uv:
uv add uipath-mcp
Configuration
Servers Definition
Create the mcp.json file:
{
"servers": {
"my-python-server": {
"type": "stdio",
"command": "python",
"args": ["server.py"]
},
}
}
Command Line Interface (CLI)
The SDK also provides a command-line interface for creating, packaging, and deploying Python-based MCP servers:
Authentication
uipath auth
This command opens a browser for authentication and creates/updates your .env file with the proper credentials.
Initialize a Project
uipath init [SERVER]
Creates a uipath.json configuration file for your project. If [SERVER] is not provided, it will create an entrypoint for each MCP server defined in the mcp.json file.
Debug a Project
uipath run [SERVER]
Starts the local MCP Server
Package a Project
uipath pack
Packages your MCP Server into a .nupkg file that can be deployed to UiPath.
Note: Your pyproject.toml must include:
- A description field (avoid characters: &, <, >, ", ', ;)
- Author information
Example:
description = "Your package description"
authors = [{name = "Your Name", email = "your.email@example.com"}]
Publish a Package
uipath publish
Publishes the most recently created package to your UiPath Orchestrator.
Project Structure
To properly use the CLI for packaging and publishing, your project should include:
- A
pyproject.tomlfile with project metadata - A
mcp.jsonfile with servers metadata - A
uipath.jsonfile (generated byuipath init) - Any Python files needed for your automation
Development
Setting Up a Development Environment
Please read our contribution guidelines before submitting a pull request.
2 maintainers
Metadata
2 maintainers
Release files for uipath-mcp 0.3.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| uipath_mcp-0.3.1.tar.gz | 933.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| uipath_mcp-0.3.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 963.3 kB
Release files / uipath_mcp-0.3.1.tar.gz
| Download URL | uipath_mcp-0.3.1.tar.gz |
|---|---|
| Size | 933.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
62f984b0da9213e4cf7acc4715a31040b20436863034809c5b3dcd171a0d0d85
|
|
BLAKE2b-256 checksum How to use checksums |
f22f9b702ed077fd043d688c7c2c2558dd9961150c8e0f89f79c5b3de9f1c1c7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 15, 2026.
Transparency logRelease files / uipath_mcp-0.3.1-py3-none-any.whl
| Download URL | uipath_mcp-0.3.1-py3-none-any.whl |
|---|---|
| Size | 30.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3509700cd3bcb0e576fd35cb7e9285f71ecdd53020bff862b7966705160c8238
|
|
BLAKE2b-256 checksum How to use checksums |
6f7918b5c6e6d7f38f694329c3e3378a0adf401e44116272d2b56ba6dcc84916
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 15, 2026.
Transparency log
