Hello everyone,
I’m building 𝚛𝚙𝚊𝚡 — an open-source parser + MCP server for a multi-project view of UiPath Studio code.
It parses project.json/.xaml across multiple projects (repos/lakes) into structured data (arguments, variables, activities, annotations).
Originally for my Workflow Analyzer custom rules; the core value proved to be the multi-project perspective.
Very early: v0.0.2 is public but not yet usable. (Pronounced “are-packs”, think RPA + X.)
What it does today
Expand to see current capabilities
- Parses
.xamlandproject.json - Works across multiple projects at once (not just single workflows)
- Exports structured outputs (JSON, pseudocode, diagrams)
- Can run standalone CLI or feed into an MCP server
My initial use cases
Expand to see examples I’ve tried
MCP integration — serve project data directly to AI clients, enabling “chat with your workflows” scenarios
Diagram generation (Mermaid, Graphviz)
Pseudocode views
Argument call graphs for SDD documentation
But these are only starting points. The real potential comes from the multi-project view: oversight, comparisons, governance, training.
What would you do with this?
Imagine you had structured, multi-project data from UiPath Studio projects.
That means: every Studio file, its dependencies, job start arguments, how arguments pass in and out of workflows, which activities are used (with their DisplayNames)… basically everything “static” that isn’t runtime.
-
What problems would this help you solve?
-
Which outputs (JSON, diagrams, pseudocode, …) would be most useful?
-
In your role (developer, CoE, partner, …), how could you apply it?
-
What blockers would prevent adoption in your environment?
Why this matters
“Studio shows me one tree at a time — I need the whole forest.”
This project is about enabling that whole-forest, multi-project view.
Further reading
Repo with changelog and ADRs: GitHub – rpax (best place to track early releases — and
if you want to follow progress)
Progress log with screenshots: LinkedIn Post