Conduct your Galaxy with a sentence.
mAesTRo is an MCP server for AVEVA System Platform. Connect it to Claude Desktop, Cursor, or any AI client that speaks the Model Context Protocol, and build, edit, audit, and deploy ArchestrA objects in plain English — without leaving the tools you already use.
AVEVA System Platform was built for engineers. The tooling around it wasn't.
If you work in a Galaxy every day, you already know:
Repetitive object work eats your week.
Rolling out 200 templated instances, fixing UDAs across a hierarchy, normalizing scripts — click by click, host by host, hour by hour.
Change is invisible until something breaks.
There's no clean way to see what changed between Tuesday and Friday — let alone who did it, or why a deploy started failing.
Knowledge lives in three engineers' heads.
New hires learn the IDE the slow way. Tribal lookup tables and "ask Steve" don't scale — and they walk out the door with the senior who built them.
You don't need a new GUI. You need a faster way to run the platform you already trust.
mAesTRo speaks Galaxy
Not a general-purpose chatbot pointed at a database. Every tool call maps to a real ArchestrA operation.
Natural-language Galaxy operations
Query objects, edit attributes, create instances, deploy templates in plain English. Tool calls execute against your live Galaxy through AVEVA's official COM interface (GRAccess) — no UI scraping, no screen automation.
Change management with snapshots
Capture Galaxy state before a change, run it, and diff the result. Roll back to any snapshot. Every change-managed operation is logged.
Graphic export and import
Export ArchestrA Toolbox graphics for diffing, editing, or external version control — and import them back into a Galaxy.
Bulk and batch operations
Apply the same change across hundreds of objects in one pass — UDAs, extensions, scripts, choice groups, linked symbols. What used to be an afternoon is now a sentence.
Fast search across the Galaxy
Find every object using a given UDA. List every script that mentions a tag. Ask "which objects still reference $LegacyMotor?" and get an answer in seconds.
Galaxy data never leaves your network
mAesTRo runs on your engineering host and binds to localhost. Your AI client decides which LLM provider receives context — and you control what context it sees.
From a sentence to a deployed change
You talk to your AI client
Describe what you want on your engineering host: "create 30 Pump instances from $Pump_Centrifugal under Area_05, set MotorHP to 25, and stage them for deployment."
mAesTRo plans and confirms
Your client translates intent into structured tool calls. mAesTRo previews exactly what's about to happen — objects, attributes, parents — and waits for your confirmation.
mAesTRo executes
Operations run through AVEVA's official COM interface (GRAccess) — the same path the IDE uses. Results stream back with object IDs, statuses, and any errors.
Everything is logged and reversible
Snapshots, diffs, and audit logs are captured automatically, so you can review, share, or undo any session.
Value at every level of the plant
Stop click-farming through the IDE
Bulk-edit attributes, refactor templates, validate UDAs across a hierarchy, or stage a coordinated deployment in plain English — with preview and snapshot-based rollback. Same COM surface as the IDE, so anything mAesTRo does, you could have done by hand. Minutes instead of days.
Visibility and standards
See what your team is changing in the Galaxy, who changed it, and when. Every change-managed operation becomes a logged, diffable, reversible event — so code-review patterns finally apply to System Platform work. Onboard new engineers in days, not months.
A safety net for change
Most unplanned downtime starts with a Galaxy change. Change-managed operations are snapshotted before they run, previewable before they apply, and logged with a human-readable diff. When something goes wrong, roll back with one command.
Real situations, handled in minutes
Bulk per-instance updates
An asset spreadsheet lands on your desk — serial numbers, locations, and motor sizes for 400 pump instances, each row a unique value. Hand it to your AI client; mAesTRo maps rows to objects, previews the writes, and deploys. Hours of click-work done in minutes.
Find what changed
A script on your $TankLevel template started throwing errors after this week's changes, and nobody remembers what shifted. Ask mAesTRo for the diff between last week's snapshot and the current Galaxy, isolate the edit, review it, fix or revert.
Search the whole Galaxy
You need to retire the $LegacyMotor template but don't know which instances still derive from it. Ask mAesTRo. Get a clean list with parent paths and last-touched dates. Refactor with confidence instead of grep-and-prayer.
Roll back under pressure
It's 2 AM and a Galaxy change from last week is flooding the control room with alarms. Pull the snapshot, diff against current state, roll back with one command, restore stable operations. Every action is captured in the change log for the incident review.
For individuals, teams, and air-gapped sites
Tiered plans at launch
mAesTRo will be available in tiers for individual engineers, engineering teams, and multi-site enterprises — including an offline-licensed option for air-gapped environments.
Final pricing and tier details will be shared with the waitlist before public launch.
Join the waitlist for pricingQuestions, answered
Does mAesTRo send my Galaxy data to the cloud?+
Which versions of AVEVA System Platform are supported?+
Which LLM providers can I use?+
How does mAesTRo actually execute changes against the Galaxy?+
What happens if a Galaxy operation fails midway?+
How do I install mAesTRo?+
Does mAesTRo work with redundant Galaxies?+
Is mAesTRo a replacement for the AVEVA IDE?+
Can I try mAesTRo before launch?+
Ready to conduct your Galaxy?
mAesTRo is launching to the waitlist first. Sign up for early-access invites, pricing details, and pilot opportunities before public launch.
Join the waitlist