Revit Model MCP

Overview Schema Source Related Servers Discussions Admin

Export Navisworks NWC

revit_export_nwc

Destructive

Export Revit models, views, or selections to NWC for Navisworks coordination, applying exporter settings XML or explicit export options.

Instructions

Export NWC on the Revit workstation; needs the Navisworks exporter. settings_xml applies exporter XML values, explicit arguments take precedence. Replacing an existing file (overwrite=true) needs a confirm_token from a first call. A long action can return status=running and jobId when the wait budget expires; it may already have changed the model, and revit_jobs returns its result. Resubmitting repeats the action.

Input Schema

Name	Required	Description
`path`	Yes
`view`	No
`scope`	No
`dry_run`	No
`document`	No	Title or file name substring of the target open document; needed when several are open.
`overwrite`	No
`parameters`	No
`coordinates`	No
`element_ids`	No
`export_urls`	No
`export_links`	No
`export_parts`	No
`settings_xml`	No
`confirm_token`	No
`convert_lights`	No
`faceting_factor`	No
`timeout_seconds`	No
`export_element_ids`	No
`export_room_geometry`	No
`find_missing_materials`	No
`divide_file_into_levels`	No
`export_room_as_attribute`	No
`convert_element_properties`	No
`convert_linked_cad_formats`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed28 schema fields changedv0.10.0Oct 14, 2026
- removedInput schema / properties / confirm_token / title
```
Removed value: -"Confirm Token"
```
- removedInput schema / properties / convert_element_properties / title
```
Removed value: -"Convert Element Properties"
```
- removedInput schema / properties / convert_lights / title
```
Removed value: -"Convert Lights"
```
- removedInput schema / properties / convert_linked_cad_formats / title
```
Removed value: -"Convert Linked Cad Formats"
```
- removedInput schema / properties / coordinates / title
```
Removed value: -"Coordinates"
```
- removedInput schema / properties / divide_file_into_levels / title
```
Removed value: -"Divide File Into Levels"
```
- changedInput schema / properties / document / description
```
Previous value: -"Case-insensitive substring of the target open document's title or file name. Required to disambiguate when the Revit process has more than one document open; omit only when a single document is open (the active document is used). An unknown or ambiguous reference is rejected before any change."New value: +"Title or file name substring of the target open document; needed when several are open."
```
- removedInput schema / properties / document / title
```
Removed value: -"Document"
```
- removedInput schema / properties / dry_run / title
```
Removed value: -"Dry Run"
```
- removedInput schema / properties / element_ids / title
```
Removed value: -"Element Ids"
```
- removedInput schema / properties / export_element_ids / title
```
Removed value: -"Export Element Ids"
```
- removedInput schema / properties / export_links / title
```
Removed value: -"Export Links"
```
- removedInput schema / properties / export_parts / title
```
Removed value: -"Export Parts"
```
- removedInput schema / properties / export_room_as_attribute / title
```
Removed value: -"Export Room As Attribute"
```
- removedInput schema / properties / export_room_geometry / title
```
Removed value: -"Export Room Geometry"
```
- removedInput schema / properties / export_urls / title
```
Removed value: -"Export Urls"
```
- removedInput schema / properties / faceting_factor / title
```
Removed value: -"Faceting Factor"
```
- removedInput schema / properties / find_missing_materials / title
```
Removed value: -"Find Missing Materials"
```
- removedInput schema / properties / overwrite / title
```
Removed value: -"Overwrite"
```
- removedInput schema / properties / parameters / title
```
Removed value: -"Parameters"
```
- removedInput schema / properties / path / title
```
Removed value: -"Path"
```
- removedInput schema / properties / response_timeout_s
```
Removed value: -{
-  "default": 1800,
-  "maximum": 3600,
-  "minimum": 30,
-  "title": "Response Timeout S",
-  "type": "integer"
-}
```
- removedInput schema / properties / scope / title
```
Removed value: -"Scope"
```
- removedInput schema / properties / settings_xml / title
```
Removed value: -"Settings Xml"
```
- addedInput schema / properties / timeout_seconds
```
Added value: +{
+  "default": 1800,
+  "maximum": 3600,
+  "minimum": 30,
+  "type": "integer"
+}
```
- removedInput schema / properties / view / title
```
Removed value: -"View"
```
- removedInput schema / title
```
Removed value: -"revit_export_nwcArguments"
```
- removedOutput schema / title
```
Removed value: -"revit_export_nwcDictOutput"
```

Changed1 schema field changedv0.9.1Oct 7, 2026

addedInput schema / properties / confirm_token

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Confirm Token"
+}

Addedv0.7.0Sep 30, 2026

TDQS

A3.6/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well beyond the annotations (destructiveHint, idempotentHint=false): it discloses the exporter dependency, the two-step confirm_token flow for overwriting files, the async job pattern (status=running + jobId, result retrievable via revit_jobs), the fact the model may already have been modified, and that resubmission repeats the action. That last point is consistent with idempotentHint=false, not contradictory.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Five dense sentences, each front-loaded and carrying distinct information (dependency, precedence, confirm flow, async behavior, resubmission risk) with no filler. Slightly packed, but nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers the operational mechanics well, and the output schema means return values need no explanation. But for a 24-parameter export tool, the bulk of the configuration surface is unexplained in both description and schema, leaving an agent guessing how to drive view/scope/element_ids/export flags.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 4% (just `document`), so the description must carry the load. It explains settings_xml precedence and the overwrite/confirm_token pairing, but leaves ~20 parameters (view, scope, dry_run, element_ids, parameters, coordinates, all the export_*/convert_* flags, faceting_factor, timeout_seconds) wholly undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource (export NWC) and adds the key precondition (requires the Navisworks exporter), which helps distinguish it from sibling revit_export and revit_export_view. It never names those siblings explicitly, so differentiation is present but not airtight.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives operational conditions: overwrite=true requires a confirm_token from a first call, settings_xml is overridden by explicit arguments, and long runs may return status=running. However it never says when to choose this over revit_export / revit_export_view, so the when-to-use guidance is implied rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server