
NavisCoord
io.github.HorizunGroupPublished by GitHub account HorizunGroupv1.1.1Updated Oct 24, 2026
Autodesk Navisworks coordination: clash triage, root causes, work plans and reports
Overview
Local MCP server plus Navisworks add-in that lets an assistant triage clashes, explain root causes, build work plans and reports, and apply reviewed changes.
- What you can do
- Analyze the open Navisworks model and rank coordination issues with scores and reasons
- Group and de-duplicate clashes, and form root-cause hypotheses with affected occurrences
- Compare saved snapshots to see what changed since the last delivery
- Prepare work packages, trade ownership, narrative reports and PDF images
- Export element IDs and handoff tables for Revit and Power BI
- Apply a reviewed plan with document/revision checks and read-back verification
- When to use it
- For BIM coordination teams running Autodesk Navisworks Manage who want an assistant to turn large clash sets into a prioritized, evidence-backed plan before a coordination meeting, or to process saved exports without Navisworks.
- Requirements
- Windows desktop only; runs as a local process. Live coordination needs a licensed Autodesk Navisworks Manage 2024, 2025 or 2026 plus the NavisCoord add-in installed via PowerShell script. The packaged runtime bundles its Python dependencies, so no Python, API key or build tools are needed. A supported AI client (ChatGPT Desktop Work, Claude Desktop, Claude Code or Codex) is required.
Installation
In SourceWeft
- Open NavisCoord in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
NavisCoord
Your next coordination meeting starts with a decision, not 10,000 clash rows.
Connect Autodesk Navisworks to ChatGPT Desktop Work, Claude Desktop, Claude Code and Codex. Ask what matters, inspect the evidence, and build a coordination plan.
[CI] [Release] [MIT] [Navisworks]
Get started · Release evidence · Report a problem
1.1.1 is public: stable download · official MCP Registry entry.
[From clashes to coordination decisions]
“Analyze the open model. Show the most important coordination issues, explain their priority, and prepare the work plan. Show me the proposed changes before applying them.”
NavisCoord pairs a native Navisworks add-in with an open-source MCP server. The engine runs on your Windows workstation. The desktop runtime includes its Python dependencies: no Python installation, API key or build tools are needed for the packaged local server. Your chosen AI client and Autodesk licence remain separate products.
What you can do
53 tools. One server. Four clients. Explore the tool guide.
Choose your client
All four connect to the local workstation. ChatGPT Desktop uses a local plugin; OpenAI Platform, a tunnel and a runtime API key are not part of this installation. See OpenAI’s desktop-plugin documentation.
Install the two pieces
- Navisworks add-in: close Navisworks and run
Install-NavisCoord.ps1. It detects your installed version, verifies the release checksums and backs up managed files. - Your AI client: install the desktop package or
.mcpbfrom Releases. Follow the client-specific instructions. - Open Navisworks Manage, load your federation and ask: “Check NavisCoord, identify the active document and analyze its clashes.”
Windows and a licensed Autodesk Navisworks Manage 2024, 2025 or 2026 are required for live coordination. The standalone analysis engine can also process saved exports without Navisworks.
Built to make the evidence inspectable
- Conservative filtering: a category name alone does not prove that a door, sleeve or slab overlap is intentional. Hosting/contact rules require relationship evidence.
- Freshness checks: changes to geometry, properties, saved selections or clash results invalidate the analysis used for derived writes.
- Complete execution: a folded decision retains its individual occurrences in write-back and Revit handoffs.
- Measured proposals: movement alternatives use element bounds. They are proposals to check against surrounding geometry and design constraints.
- Honest delivery comparisons: an issue missing from a later analysis is not automatically labelled “resolved.” Coverage, exclusions and source changes remain visible.
- Reproducible installation: pinned dependencies, artifact checksums, a standalone runtime and rollback-aware installation.
The release verification record distinguishes automated checks, Navisworks acceptance tests and client verification. A directory listing or a passing test suite is not a promise that software can never fail. External marketplace review is recorded separately from our tests.
Works with your coordination standard
Load a company profile to control disciplines, category/file mappings, tolerances, priorities and coordination rules. Start with the example profile. A model with missing discipline or level data is identified explicitly so the team can map it before relying on the ranking.
NavisCoord produces evidence and proposed coordination actions. Engineering approval and edits in the authoring application remain with the project team. Handoff files carry the IDs needed to continue with tools such as Horizun Revit MCP and Horizun PBI MCP.
Privacy Policy
NavisCoord does not upload the complete model or send telemetry to a Horizun service. Requested tool outputs can include model names, element properties, coordinates and images; your AI client receives those outputs. Read the privacy policy and security model.
Build and contribute
See Testing, Releasing and Contributing. Please report reproducible cases with sensitive project information removed.
If NavisCoord helps your team, share a reproducible coordination example and star the repository so other BIM coordinators can find it.
MIT · Built by HorizunGroup · Independent of Autodesk, OpenAI and Anthropic.
Source: README.md at commit 0d21758
Tools
0Version history
2- v1.1.1LatestOct 2, 2026
- v1.0.0Sep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts