The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Revit Model MCP listing page.
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.
Revit Model MCP returns requested model data to the selected MCP client. The bundle enables response path redaction by default. The privacy policy covers collection, storage, sharing, retention and contact information.
Install uv on the client's PATH, download revit-model-mcp-<version>.mcpb from the latest release, and open it in Claude Desktop.
The settings form configures the workstation host, path redaction, optional actions and the HTTP bearer token without editing JSON.
Use local on the Windows Revit workstation, or configure a remote workstation for macOS and Linux clients.
Path redaction starts enabled and actions start disabled.
The Windows workstation still needs the add-in below.
See the bundle guide for build details and prerequisites.
Verify downloads. Release assets include GitHub build provenance attestations; follow download verification before installing.
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 uv and use Python 3.11+. For Claude Code on the same Windows workstation:
For manual Claude Desktop registration, add to its MCP configuration:
From a clone, uv run --directory server revit-model-mcp runs the same server without installing the package.
With REVIT_MCP_HOST=local the server reaches each Revit through its own named pipe, restricted to the Windows user running Revit; no port or URL reservation is needed.
For macOS or Linux clients, configure a remote workstation.
Call revit_ping in the MCP client and expect success: true.
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:
revit_show opens a matching plan and selects the room.revit_isolate, then revit_place_family at the room's roomCenterMm, then revit_move. Each mutation is its own Revit transaction.The picture below is the PNG saved by revit_export_view during an earlier session against Revit 2023 over SSH, untouched:
| 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 enabled by default: opt out with REVIT_MCP_READ_ONLY=1 in the server, or the workstation read-only file.
Model mutations support dry_run previews and return verification and a human-readable summary; a committed action assimilates into one named Revit undo entry, visible in the add-in's "MCP activity" pane; revit_undo_last undoes it while it is still Revit's last change.
See actions for gates, exceptions and verification failures.
Local Windows clients use REVIT_MCP_HOST=local under the Revit user's account.
Remote clients run the whole server on the workstation over SSH, as the same Windows user that runs Revit.
Install it there once with uv tool install revit-model-mcp, then register ssh as the command:
Replace revit-pc with the workstation's SSH host alias.
MCP stdio flows through the SSH session and the remote server uses the named pipe, so no port opens.
REVIT_MCP_HOST=ssh:<alias> (file channel over SSH) and HTTP through an SSH tunnel remain available; HTTP requires a bearer token except for /health and binds to loopback by default.
See transport setup.
The default tools read the model without model-changing transactions; exports and channel operations write files outside it.
MCP actions are refused in read-only mode, while direct HTTP callers require the bearer token and are refused while the workstation read-only file is present.
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.
| 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.
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.
MIT, maintained by Dinar Sharafutdinov. See third-party notices for dependency licenses.