Two products · one sign-inInstall one or both; the same account works for each.
Let AI assistants read and work with the model open in Navisworks Manage — clashes, sets, viewpoints and QA reports — and learn, with your team, from every fix.
Run the clash tests and show me the 10 deepest clashes with their grid locations.
Illustrative session. The assistant works on the model already open in your Navisworks.
Navisworks MCP runs as a plug-in inside Navisworks Manage, so the assistant works on the live NWF or NWD — the same model your team reviews.
Browse the selection tree, read and compare properties, and find items by any property.
Create, edit, import and export search sets, selection sets and saved viewpoints.
Create and run tests, then review, assign, comment, group and summarise the clashes.
Check the model against a clash matrix, audit the NWF, and write HTML, Excel or CSV reports.
Colour, hide and isolate items, section the model, set the camera, measure and take screenshots.
Read and edit TimeLiner tasks and their data sources, and read Quantification.
Append and merge models, save and publish NWD, export DWF and run other exports and add-ins.
Lessons and playbooks from jobs that went well are shared, privacy-filtered, with the whole team.
When Navisworks starts, the plug-in starts by itself. Your AI assistant talks to the Navisworks MCP server on your PC, which passes each request to Navisworks over a private connection that only your Windows account can open.
With several Navisworks windows open, the assistant asks which one you mean — it never guesses. Long jobs such as clash runs and audits run in the background while you keep working.
One file, one sign-in, every Navisworks Manage on your PC. The same sign-in as Revit MCP.
Run Install-Navisworks-MCP.cmd. If Windows asks whether to run it, choose Run (or More info › Run anyway).
It checks your PC and installs Navisworks MCP for every Navisworks Manage 2025, 2026 and 2027 on it. No administrator rights needed. Navisworks Freedom has no plug-in support.
Choose Google or GitHub. Your browser opens; the code is already copied — click the box, press Ctrl+V and confirm. The window closes by itself.
Nothing to configure. Setup connects every AI assistant it finds on your PC, and every Navisworks start connects the ones installed since. Restart the assistant, or start a new chat, after it was connected.
Connected automatically:
Installed one later? AI Tools › MCP Server › Connect AI assistants now. The Claude app is connected after you quit it from its tray icon and open it again.
https://revit-mcp.pages.dev/mcp/navisworksSign in with the same Google or GitHub account as on your PC, and keep Navisworks open. Requests pass through the team gateway, which never stores or logs them. Needs a paid claude.ai plan or ChatGPT with Developer mode.
Navisworks MCP works on the Navisworks file only, and anything that removes work is shown to you first.
Deleting or resetting sets, viewpoints, clash tests or results is always previewed first, and needs your yes.
Each change made through Navisworks MCP is one Undo step named “MCP: …”, where Navisworks supports undo.
RVT, DWG, IFC and other source models are never changed — only the Navisworks file.
Switch it on in AI Tools › Settings and assistants can read but never change anything.
AI-written C# scripts and UI automation stay off unless you switch them on.
Reports and audits are written to Documents\DAR\Navisworks MCP reports on your PC.
If Navisworks MCP cannot do something you ask, your AI assistant tells you, and offers to report it to the developer. Missing capabilities are added in new versions, which install themselves.
Request anything in Navisworks. When no tool covers it, the assistant says so plainly instead of guessing.
It shows you what it would send: what is missing, a full description and your request, without project or client names. Nothing is sent unless you agree.
The developer receives it directly and adds the capability. The next version reaches every PC automatically.