navisworks-mcp
MCP serverCommunity
A token-protected bridge to a live Navisworks 2026 or 2027 session: 32 tools for the selection tree, clash review, viewpoints and Roslyn C#. By nhantruong96.
1 starsUpdated 2 months agoGitHub data from 5 Nov 2026
At a glance
- Type
- MCP server
- Works with
- Navisworks
- How it connects
- Drives a running copy of the tool
- Access
- Can modify models
- Tool versions
- Navisworks Manage / Simulate 2026 (API 23.x) and 2027 (API 24.x)
- Operating systems
- Windows
- Needs a Navisworks licence
- Yes
- Transport
- Local (stdio)
- AI clients documented
- Claude Code
- Licence
- Not stated in its documentation
- Language
- C#
What it can do
- Opens and appends models, browses the selection tree and builds a property catalogue before searching, since property names differ between Revit, IFC and DWG sources.
- Creates and runs clash tests, walks results through the review workflow and writes its own HTML, CSV or JSON clash reports.
- Saves and applies viewpoints, sets the camera, overrides colours and renders images.
- Compiles and runs C# on the Navisworks main thread, with an API index generated from your install.
Limitations
- TimeLiner, Quantification, redlines and headless batch work have no named tools yet (C# can reach TimeLiner and Quantification).
- The installed add-in needs administrator rights once; the launcher route avoids that but can return blank images if the window opens off-screen.
- Long clash runs leave Navisworks unresponsive until they finish.
Install
pwsh -File scripts/build.ps1
pwsh -File scripts/install.ps1claude mcp add navisworks -- python C:\Tools\navisworks-mcp\server\run_server.pySource: github.com/nhantruong96/navisworks-mcp#4-register-the-mcp-server
MCP servers and skills run code on your computer. Review the source before installing.
AI-generated models, drawings and results must be checked by a qualified engineer before use.