Revit Model MCP

Overview Schema Source Related Servers Discussions Admin

Export Model Files

revit_export

Destructive

Export PDF, DWG, IFC, or schedule CSV files from an open Revit model; dry runs preview outputs, and overwrites require confirmation.

Instructions

Export PDF, DWG, IFC or schedule CSV files on the Revit workstation; dry_run returns planned file names. Replacing existing files (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
`views`	No
`format`	Yes
`sheets`	No
`dry_run`	No
`options`	No
`document`	No	Title or file name substring of the target open document; needed when several are open.
`overwrite`	No
`sheet_set`	No
`all_sheets`	No
`output_dir`	No
`confirm_token`	No
`timeout_seconds`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed17 schema fields changedv0.10.0Oct 14, 2026

removedInput schema / properties / all_sheets / title
```
Removed value: -"All Sheets"
```
removedInput schema / properties / confirm_token / title
```
Removed value: -"Confirm Token"
```

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 / folder

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Folder"
-}

removedInput schema / properties / format / title
```
Removed value: -"Format"
```
removedInput schema / properties / options / title
```
Removed value: -"Options"
```

addedInput schema / properties / output_dir

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

removedInput schema / properties / overwrite / title
```
Removed value: -"Overwrite"
```

removedInput schema / properties / response_timeout_s

Removed value: -{
-  "default": 1800,
-  "maximum": 3600,
-  "minimum": 30,
-  "title": "Response Timeout S",
-  "type": "integer"
-}

removedInput schema / properties / sheet_set / title
```
Removed value: -"Sheet Set"
```
removedInput schema / properties / sheets / title
```
Removed value: -"Sheets"
```

addedInput schema / properties / timeout_seconds

Added value: +{
+  "default": 1800,
+  "maximum": 3600,
+  "minimum": 30,
+  "type": "integer"
+}

removedInput schema / properties / views / title
```
Removed value: -"Views"
```
removedInput schema / title
```
Removed value: -"revit_exportArguments"
```

removedOutput schema / title

Removed value: -"revit_exportDictOutput"

Addedv0.9.1Oct 7, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Beyond the destructive/non-idempotent annotations it discloses the two-phase confirm flow for overwrites, the partial-completion hazard ('may already have changed the model'), the status=running/jobId return shape, and that resubmitting repeats the action. That is exactly the behavioral detail an agent needs before invoking a destructive export.

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?

Three dense sentences, front-loaded with the core capability before the confirmation and async caveats. Each sentence carries distinct information, though the run-on delivery of the job-status clause is slightly compressed.

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

Completeness4/5

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

For a destructive, 12-parameter export tool the description covers the risky paths (overwrite confirmation, async job handoff, partial mutation). An output schema exists so return values need not be restated, yet the unaddressed selection parameters remain a gap in an otherwise complete picture.

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

Parameters3/5

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

With schema coverage at 8%, the description carries most of the burden, and it does explain dry_run, overwrite, and confirm_token meaningfully. However, views, sheets, sheet_set, all_sheets, options, output_dir, document, and timeout_seconds are left entirely undocumented, so nearly two thirds of the parameters gain no meaning from either source.

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?

The description names a specific verb and resource and enumerates the four export formats (PDF, DWG, IFC, schedule CSV), which pins down scope well. It stops short of distinguishing itself from close siblings like revit_export_view or revit_export_nwc, so an agent must infer the boundary.

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

Usage Guidelines4/5

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

It gives concrete conditional guidance: use dry_run to preview planned file names, and supply a confirm_token from a first call when overwrite=true. It also routes the agent to revit_jobs when a run outlives the wait budget. No explicit when-not or sibling-alternative guidance is offered.

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

Deploy Server