Revit Model MCP

Overview Schema Source Related Servers Discussions Admin

Link CAD Drawing

revit_link_cad

Destructive

Link or import a DWG into a Revit plan view to reference CAD geometry. Returns layer names and extents in millimeters for positioning.

Instructions

Link or import a DWG into a plan view on the Revit workstation. Returns CAD layers and extents in mm.

Input Schema

Name	Required	Description	Default
`link`	No
`path`	Yes
`view`	No
`level`	No
`units`	No		auto
`layers`	No
`origin`	No		internal
`dry_run`	No
`document`	No	Title or file name substring of the target open document; needed when several are open.
`timeout_seconds`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedv0.10.0Oct 14, 2026

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 / layers / title
```
Removed value: -"Layers"
```
removedInput schema / properties / level / title
```
Removed value: -"Level"
```
removedInput schema / properties / link / title
```
Removed value: -"Link"
```
removedInput schema / properties / origin / title
```
Removed value: -"Origin"
```
removedInput schema / properties / path / title
```
Removed value: -"Path"
```

removedInput schema / properties / response_timeout_s

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

addedInput schema / properties / timeout_seconds

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

removedInput schema / properties / units / title
```
Removed value: -"Units"
```
removedInput schema / properties / view / title
```
Removed value: -"View"
```

removedInput schema / title

Removed value: -"revit_link_cadArguments"

removedOutput schema / title

Removed value: -"revit_link_cadDictOutput"

Addedv0.9.1Oct 7, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations already flag this as a non-read-only, destructive, non-idempotent operation, so the safety profile is covered. The description adds that CAD layers and extents (in mm) are returned, but says nothing about what gets modified in the model, dry_run behavior, or the timeout implication for a long-running job.

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

Conciseness5/5

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

Two tight sentences that lead with the action and then the return payload. Zero filler.

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

Completeness2/5

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

For a 10-parameter destructive mutation with almost no schema documentation, the description is far too thin. It does not need to restate the output schema, but the parameter behavior, prerequisites, and link/import distinction should have been covered here.

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 10% (just the 'document' param), yet the description explains none of the 10 parameters: the link-vs-import semantics of 'link', the meaning of 'auto' units, layer filtering, origin modes, or dry_run. It fails to compensate for the coverage gap.

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 (link or import a DWG) and the target context (a plan view on the Revit workstation). It is distinguishable from siblings like revit_walls_from_cad or revit_remove_links, though it never names them explicitly.

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

Usage Guidelines2/5

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

No guidance on when to link versus import, when to prefer this over revit_walls_from_cad, or what prerequisites (open document, plan view) must hold. The 'link' parameter defaults to true but the description never explains the choice.

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

Deploy Server