naviscoord-mcp

<!-- mcp-name: io.github.HorizunGroup/naviscoord-mcp -->

# 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.**

[English](README.md) · [Español](README.es.md)

[![CI](https://github.com/HorizunGroup/naviscoord-mcp/actions/workflows/ci.yml/badge.svg)](https://github.com/HorizunGroup/naviscoord-mcp/actions/workflows/ci.yml)
[![Release](https://img.shields.io/github/v/release/HorizunGroup/naviscoord-mcp)](https://github.com/HorizunGroup/naviscoord-mcp/releases/latest)
[![MIT](https://img.shields.io/badge/license-MIT-blue)](LICENSE)
[![Navisworks](https://img.shields.io/badge/Navisworks%20Manage-2024–2026-0696d7)](docs/INSTALL.md)

[**Get started**](docs/INSTALL.md) · [Release evidence](docs/RELEASE-1.0-VERIFICATION.md) · [Report a problem](https://github.com/HorizunGroup/naviscoord-mcp/issues)

**1.1.1 is public:** [stable download](https://github.com/HorizunGroup/naviscoord-mcp/releases/tag/v1.1.1) · [official MCP Registry entry](https://registry.modelcontextprotocol.io/v0.1/servers/io.github.HorizunGroup%2Fnaviscoord-mcp/versions/1.1.1) · [Smithery](https://smithery.ai/servers/pabloalejandrozg/naviscoord-mcp).

![From clashes to coordination decisions](docs/assets/naviscoord-flow.svg)

> “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

| Ask for | Get back |
|---|---|
| “What needs attention first?” | Ranked issues with deterministic scores and the reasons behind them |
| “Are these really separate problems?” | Spatially bounded groups, duplicate collapse and traceable original clashes |
| “Could one change address several occurrences?” | Root-cause hypotheses, measured evidence and every affected occurrence |
| “What changed since the last delivery?” | Persistent issue identities, saved snapshots and a comparison of changes |
| “Prepare the coordination meeting.” | Work packages, trade ownership, narrative reports and PDF images |
| “Connect this to Revit and Power BI.” | Authoring element IDs, structured handoff files and tables for downstream tools |
| “Apply the reviewed plan.” | Targeted writes with document/revision checks and read-back verification |

**53 tools. One server. Four clients.** [Explore the tool guide](docs/TOOLS.md).

## Choose your client

| Client | Install |
|---|---|
| **ChatGPT Desktop — Work** | Run the desktop-plugin installer, then open **Plugins → Personal → NavisCoord → Install** |
| **Codex** | Use the same personal plugin, or register the executable with `codex mcp add` |
| **Claude Desktop** | Install the release `.mcpb`, which includes the standalone server |
| **Claude Code** | Install `naviscoord-mcp@horizun-navis`, or register the executable with `claude mcp add` |

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](https://learn.chatgpt.com/docs/enterprise/plugin-management).

### Install the two pieces

1. **Navisworks add-in:** close Navisworks and run [`Install-NavisCoord.ps1`](Install-NavisCoord.ps1). It detects your installed version, verifies the release checksums and backs up managed files.
2. **Your AI client:** install the desktop package or `.mcpb` from [Releases](https://github.com/HorizunGroup/naviscoord-mcp/releases/latest). Follow the [client-specific instructions](docs/INSTALL.md).
3. 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](docs/RELEASE-1.0-VERIFICATION.md) 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](profiles/example-profile.json). 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](https://github.com/HorizunGroup/horizun-revit-mcp) and [Horizun PBI MCP](https://github.com/HorizunGroup/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](docs/PRIVACY.md) and [security model](docs/SECURITY-MODEL.md).

## Build and contribute

```powershell
python -m pytest server/tests -q
dotnet run --project addin/NavisCoord.Tests -c Release
```

See [Testing](docs/TESTING.md), [Releasing](docs/RELEASING.md) and [Contributing](CONTRIBUTING.md). 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](https://github.com/HorizunGroup) · Independent of Autodesk, OpenAI and Anthropic.