# NavisCoord

Analyze Navisworks clashes, group related issues, and draft coordination plans through an MCP server. Useful when a model review needs a clear set of decisions.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed · ★ 20
- Author: HorizunGroup
- License: MIT · policy=link-only · description only; the file stays with the author
- Source: https://github.com/HorizunGroup/naviscoord-mcp
- Updated: 2026-10-20
- HTML: https://affpapa.org/en/nevibecode/mcp/naviscoord

## What it does

NavisCoord connects a native Autodesk Navisworks add-in to an MCP server running on a Windows workstation. It ranks coordination issues and gives reasons for their priority, groups related clashes, and compares saved snapshots. Live model work requires Windows and a licensed Autodesk Navisworks Manage 2024, 2025, or 2026.

The server can prepare work packages, assign trade ownership, and produce narrative reports with PDF images. It also creates handoff files for downstream tools and supports targeted writes after a plan has been reviewed. Document and revision checks run before writes, followed by read-back verification. Proposed changes still need engineering approval from the project team.

The packaged local server includes its Python dependencies, so a separate Python installation or API key is not needed for that setup. Install the Navisworks add-in separately: close Navisworks and run `Install-NavisCoord.ps1`. Missing discipline or level data must be mapped before relying on issue rankings.

## Install

### Claude Code (native platform)

**Install**
- The MCP registry has no launch command for it: see the repository README

## When to use it
- rank coordination issues by priority
- collapse duplicate clashes into traceable groups
- investigate possible root causes and affected occurrences
- compare model issues across saved snapshots
- prepare trade work packages and coordination reports

## Example prompts
- Check NavisCoord, identify the active document, and analyze its clashes.
- Rank the open coordination issues and explain the evidence behind their priority.
- Draft a coordination plan and show the proposed changes before applying them.

## Similar
- [REA](https://affpapa.org/en/nevibecode/mcp/rea.md) — MCP server · ★ 386989
- [GitHub](https://affpapa.org/en/nevibecode/mcp/github.md) — MCP server · ★ 33918
- [Netdata](https://affpapa.org/en/nevibecode/mcp/netdata.md) — MCP server · ★ 81115
- [browser-use](https://affpapa.org/en/nevibecode/mcp/browser-use.md) — MCP server · ★ 119160
- [Codebase Memory](https://affpapa.org/en/nevibecode/mcp/codebase-memory.md) — MCP server · ★ 47392
- [mcp-server](https://affpapa.org/en/nevibecode/mcp/mcp-server.md) — MCP server · ★ 43872

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md