Revit Model MCP¶
For people reviewing or automating Revit models with an AI client: read a live Revit model through MCP, read-only by default, and act in it only when two explicit gates are on.
Install¶
On the Revit workstation¶
Download RevitModelMcp-<version>-SingleUser.msi (current user) or RevitModelMcp-<version>-MultiUser.msi (all users) from the latest release.
Run it with Revit closed, then start Revit and open a model.
Alternatively, run from a clone in PowerShell:
.\install.ps1 -Source Release
On the machine with the MCP client¶
Install uv and use Python 3.11+. For Claude Code on the same Windows workstation:
claude mcp add revit-model-mcp -e REVIT_MCP_HOST=local -e REVIT_MCP_REDACT_PATHS=1 -- uvx revit-model-mcp
For Claude Desktop, add to its MCP configuration:
{
"mcpServers": {
"revit-model-mcp": {
"command": "uvx",
"args": ["revit-model-mcp"],
"env": {
"REVIT_MCP_HOST": "local",
"REVIT_MCP_REDACT_PATHS": "1"
}
}
}
}
From a clone, uv run --directory server revit-model-mcp runs the same server without installing the package.
For macOS or Linux clients, configure a remote workstation.
Check¶
Call revit_ping in the MCP client and expect success: true.
In action¶
Claude Desktop runs on a Mac and connects to Revit 2026 on a Windows workstation. Both action gates are enabled in this recording.

What happens in the recording, in order:
- "What model is open in Revit right now?" The client reads the document, levels and room counts.
- "Which level has the most room area? Find the largest room and show it to me." The client aggregates room areas by level and queries the largest room.
revit_showopens a matching plan and selects the room. - "Isolate that room, place a Chair-Breuer at its centre and move it 800 mm along X."
revit_isolate, thenrevit_place_familyat the room'sroomCenterMm, thenrevit_move. Each mutation is its own Revit transaction. - Cleanup afterwards is one more sentence: reset the view, delete the chair.
The picture below is the PNG saved by revit_export_view during an earlier session against Revit 2023 over SSH, untouched:
What you get¶
| Read tools | Names |
|---|---|
| Document and catalog | revit_ping, revit_document_info, revit_list_catalog, revit_list_instances |
| Elements and parameters | revit_query_elements, revit_aggregate_elements, revit_element_details, revit_list_relations, revit_list_warnings |
| Views and export | revit_list_views, revit_view_summary, revit_view_elements, revit_view_warnings, revit_export_view |
| Coordinator checks | revit_model_health, revit_links_status, revit_shared_coordinates, revit_parameter_fill_check |
See the full tool reference for arguments, units and limits.
Actions are opt-in: both REVIT_MCP_ALLOW_WRITE=1 in the server and the workstation allow-write file are required.
Model mutations support dry_run previews and return verification; revit_batch groups actions into one undo entry.
See actions for gates, exceptions and verification failures.
Remote workstations¶
Local Windows clients use REVIT_MCP_HOST=local under the Revit user's account.
Remote clients can use an SSH tunnel to the workstation's loopback endpoint.
HTTP requires a bearer token except for /health and binds to loopback by default; see transport setup.
Security¶
The default tools read the model without model-changing transactions; exports and channel operations write files outside it.
MCP actions require both gates, while direct HTTP callers require the bearer token and workstation gate.
REVIT_MCP_REDACT_PATHS=1 hides directories in response path fields, but names, parameter values, errors, channel files and exported image localPath values remain visible.
See security details for authentication and privacy boundaries, and SECURITY.md to report a vulnerability.
Compatibility¶
| Revit year | Add-in target framework | Validation status |
|---|---|---|
| 2022 | .NET Framework 4.8 | Build evidence |
| 2023 | .NET Framework 4.8 | Build evidence |
| 2024 | .NET Framework 4.8 | Builds and install script |
| 2025 | .NET 8 | Build evidence |
| 2026 | .NET 8 | Builds, live reads/actions and install script |
| 2027 | .NET 10 | Build evidence |
See validation evidence for dates and limits, and known gaps.
Contributing and support¶
Documentation covers setup, tools and transport.
Start with CONTRIBUTING.md, ask questions in Discussions, or report bugs and request features through the issue forms. CI runs the C# and Python test suites and builds the supported Revit configurations.
Contributors¶
License¶
MIT, maintained by Dinar Sharafutdinov. See third-party notices for dependency licenses.