Highlights
Aligned with the UiPath Python SDK v2.2.0 runtime architecture. This release adopts the new runtime protocol pattern introduced in the SDK, replacing the previous middleware-based approach.
What's changed
Runtime protocol adoption
- Implements
UiPathRuntimeProtocolandUiPathRuntimeFactoryProtocol— the standard execution model from the SDK v2.2.0 rewrite. MCP servers now plug into the same runtime lifecycle as agents and automations. - Server metadata (
mcp_server_id,mcp_server_slug) is now sourced fromUiPathRuntimeContextinstead of manual config parsing.
Simplified internals
- Removed the middleware hooks (
cli_run.py,cli_init.py) and thestream()/ event emitting path — unnecessary complexity for MCP servers. - Tracing setup (
LlmOpsHttpExporter) removed from the package; the CLI handles this automatically now. - Cleaned up the server template (dropped ~400 lines of boilerplate).
Import path changes
- Follows the SDK's import restructuring:
uipath._clipaths moved touipath.platformanduipath.runtime. If you have custom code referencing internal imports, update accordingly.
Dependencies
uipathbumped to>=2.8.23, <2.9.0- Added explicit
uipath-runtime >=0.8.0, <0.9.0 - MCP Python SDK stays on v1.x (
mcp >=1.25, <2) — picks up the v1.26.0 fix for HTTP 404 on unknown session IDs (was incorrectly returning 400) and the v1.25.0 URL elicitation fix.
Breaking changes
- Python 3.11+ required (inherited from the SDK).
- The old middleware-based extension points are gone. If you were hooking into
middlewares.py,cli_run.py, orcli_init.py, those no longer exist. - Server template regenerated — run
uipath initon existing projects to pick up the new structure.
References
- UiPath Python SDK v2.2.0 — runtime protocol, import restructuring, Python 3.11+ requirement
- MCP Python SDK v1.26.0 — HTTP 404 for unknown session IDs, resource metadata support
- MCP Python SDK v1.25.0 — URL elicitation fix, v1.x maintenance branch