DRAWING NWX-001 · REV 02 · 2026

MCP server · Python · MIT · Windows / macOS / Linux · Autodesk APS compatible

Run clash queries in natural language

No more filtering rulesets by hand or wrangling spreadsheet exports. Navisworks MCP Toolkit turns any MCP-compatible AI client into a co-pilot for clash detection, model review, and quantity queries — straight out of your .nwf files.

Start free · 100 calls / month Read the docs
MCP TOOLS
05
ADAPTERS
03
TESTS
48 ✓
LATENCY p50
< 120 ms
§ 01 A3 · 1:50

A thin, honest bridge between AI agents and Autodesk Navisworks.

Purpose-built for BIM coordinators, VDC engineers, and AI systems.

An MCP-compatible Python server that runs locally on Windows and exposes five Navisworks tools — clash listing, clash execution, clash export, model review, and model-item queries — to any MCP-compatible AI client via stdio transport. Built for BIM coordinators, VDC engineers, and automation pipelines powered by Autodesk Platform Services.

  • N.01 No data leaves your machine unless you wire an external client.
  • N.02 Mock + XML adapters let you develop without a Navisworks license.
  • N.03 The COM adapter drives the real Clash Detective on Windows.
§ 02 SH. 2 / 5

Five tools, one protocol, three deploy modes.

Every capability is a first-class MCP tool with a typed schema.

F-001 CAPABILITY

Natural-Language Clash Queries

Ask in plain English: “show active duct-vs-structure clashes above 20 mm.” The server translates intent into Navisworks tool calls.

F-002 PROTOCOL

MCP Protocol Compatible

Stdio transport, stateless tools. Plugs into Claude Code, Claude Desktop, Cursor, and any MCP-conformant agent.

F-003 INTEGRATION

Navisworks Native

Wraps Autodesk Clash Detective, Model Review, and model-item queries. Supports .nwf and .nwd sources.

F-004 DEPLOY

Python MCP Server

Single pip install. Runs locally over stdio — no cloud dependency, no data leaves your machine unless you want it to.

F-005 QUALITY

48 Passing Tests

Three adapters (mock, XML, COM) covered by a deterministic test suite so you can trust returns without opening Navisworks.

F-006 BILLING

Pay-as-you-Go Billing

Free 100 calls/month for evaluation. Usage-based pricing from €0.01 per tool call thereafter. Cancel whenever.

§ 03 1:1

Wire it up in three commands.

Install, register, query. Stdio transport — works anywhere MCP does.

TERMINAL terminal + .mcp.json bash 
01# 1 — install02pip install navisworks-mcp03 04# 2 — register in Claude Code / Desktop (.mcp.json)05{06  "mcpServers": {07    "navisworks": {08      "command": "navisworks-mcp",09      "env": { "NW_MODE": "navisworks", "NW_FILE_PATH": "C:/models/site.nwf" }10    }11  }12}13 14# 3 — ask in natural language15> show active clashes on level 3 between ducts and beams16 17⟶  clash_detective_run({ testName: "HVAC vs STRUCT", level: 3 })18⟶  { clashes: [ { id: "CL-001", x: 1240, y: 308, z: 45, ... } ] }
§ 04 ISO A3

The full loop, on one sheet.

Three steps. Each one leaves an audit trail in your MCP client's session log.

  1. STEP 01 ~ 2 min

    CONFIGURE

    Install the Python MCP server. Point it at a .nwf or .nwd file.

  2. STEP 02 ~ 30 sec

    CONNECT

    Register the server in your MCP client's config. No cloud roundtrip.

  3. STEP 03 ∞

    QUERY

    Ask clash, review, or model questions in natural language. Get structured JSON back.

§ 05 PARTS MANIFEST · P-001…003

Priced like a part, not a SaaS.

Free tier to evaluate. Metered thereafter. No seats, no tiers-shaped-like-handcuffs.

[P-001] COMMUNITY Free 100 calls / month
[P-002] STUDIO € 0.01 / call Metered · stop any time
[P-003] ENTERPRISE Contact Air-gap · SSO · volume
See the full parts manifest