Revit MCP guide · Use it
Permissions and safety
What stops an assistant doing something to your model that you did not ask for, and how you prove what it did.
Every rule on this page is enforced by the add-in inside Revit. None of it depends on the assistant behaving, and nothing written in a model or in a prompt can widen what the assistant is allowed to do.
It runs on your computer
- The add-in and the small server program both run on your computer. They talk to each other only on that computer, as the Windows user who is signed in.
- lAvArt does not receive your model, your prompts or the answers. There is no lAvArt server in the middle.
- The assistant you chose (Claude, for example) sees what it asks Revit for, under your own account and that company’s terms. If a project must not be seen by an AI service at all, do not connect an assistant while it is open, or use Pause AI.
Permission, per document
Each document has its own setting, on the lAvArt MCP panel under Permission:
- Read only. How every document starts. The assistant can look and answer. It can change nothing in the model.
- Allow edits. It can change values, add elements and change how things are drawn, each through a preview.
- Allow edits and deletes. It can also make changes that affect every element of a type at once. Deleting elements needs this setting too, and arrives in the next release.
No tool can change this setting: only a person can, in Revit. Opening a different document does not carry the setting over. Allowing edits in one project says nothing about the next.
A preview before a change
- A change is first returned as a preview: how many elements, a sample of before and after, and anything it would skip and why. A preview changes nothing.
- Applying a change to more than 25 elements, and any change that needs Allow edits and deletes, is only accepted from a preview of exactly that change, on exactly those elements.
- A preview is good for 15 minutes and for one use. If any of the elements changed in between, it goes out of date and has to be run again.
One undo per change
- Everything one request changes becomes one entry in Revit’s undo list, named after what was done. Ctrl+Z takes back exactly that.
- The add-in keeps its own record of each change until you close Revit, so the assistant can revert one later, after the undo list has moved on.
- A revert only puts a value back if it is still the value the change wrote. If you have edited it since, it is yours and is left alone.
- Reverting something the assistant created removes only what that request made, and only if nobody has changed it since and nothing newer depends on it.
Pause AI
Pause AI on the lAvArt MCP panel refuses every new request at once, in every document, until you resume. It is answered immediately, even when Revit is busy. Use it before a deadline, during a review, or any time you would rather nothing touched the model.
The activity log
Every request is recorded with its time, which assistant made it, what it asked for and how it ended. Open Activity on the panel to read it. The record is kept on your computer, by month, and is not sent anywhere.
Workshared and central models
- A central model opened directly is never written to. Open a local copy, as you would for your own edits.
- Elements owned by another user are skipped, and the result says which.
- Linked models, family documents and read-only files are read, never written.
- Previews are worked out without touching the model, so a preview never borrows an element from a colleague.
Limits it keeps
- There is a ceiling on how many elements one request may touch.
- Changes are rate-limited, so a runaway conversation cannot hammer a model.
- If Revit rolls a change back, nothing is changed and the assistant is told Revit’s reason.
- A request that waits too long is dropped, not run late.
What each refusal looks like is listed on Troubleshooting.
Something here wrong, or missing? Write to info@lavart.ai.