Connecting Claude to Revit 2024, 2025, or 2026 requires a connector built for that Revit version. Autodesk’s own external Revit MCP preview targets newer Revit releases; its instructions are not an installation recipe for these older versions.
This guide follows the public Revit Claude Connector project by Ibrahim Fahdah, using release v1.0.6, published March 31, 2026. We checked the release archive and installation documentation on November 10, 2026. The screenshots below are the maintainer’s published screenshots, not a claim that we independently installed these Windows combinations. For an integrated alternative that combines frontier intelligence with native application work, explore ArchiLabs Desktop.
Connect Claude to Revit 2024, 2025, and 2026: choose the correct build
The maintainer’s installation guide separates the downloaded package into two runtime variants. Revit 2024 uses the Revit2024 folder. Revit 2025 and Revit 2026 use Revit2025Plus. Both variants include an add-in manifest and a companion folder; those pieces belong together.
Revit 2024: Copy the contents from the release’s Revit2024 folder into %APPDATA%\Autodesk\Revit\Addins\2024.
Revit 2025: Copy the contents from Revit2025Plus into %APPDATA%\Autodesk\Revit\Addins\2025.
Revit 2026: Copy the contents from Revit2025Plus into %APPDATA%\Autodesk\Revit\Addins\2026.
Use the year of the installed Revit application, not the current calendar year. Keep the downloaded directory structure intact. In each destination, the RevitClaudeConnector.addin file should sit beside the RevitClaudeConnector folder. Placing only the manifest in the add-ins directory leaves Revit without the associated plugin files.
Step 1: prepare the Windows workstation
Use the full Windows version of Revit with a project open, and install the current Claude Desktop application. Confirm that your organization allows the chosen local extension and its access to project information. A connector can expose both reading and writing tools; review that scope before enabling it on project data.
Start with a disposable copy of a small model. Record the Revit year and build from its About dialog, the connector release, and the Claude Desktop version. Those three values make later troubleshooting much easier. Close Revit before copying the plugin files.
This walkthrough uses a packaged local extension. It does not require you to invent a remote connector URL or paste an unrelated server’s JSON configuration into Claude. Anthropic documents local MCP servers in Claude Desktop; client settings and available modes can change, so use the current local-extension controls in your installed application.
Step 2: download the pinned connector release
Open the v1.0.6 release page and download revit-claude-connector-v1.0.6.zip. Use the project’s release asset, rather than a repackaged download from a directory site.
The archive we inspected had SHA-256 9c722e03cac89c675d218f4463fde49b99d4404e340caa9079340393416889e9. This identifies the inspected file; it is not a security certification. Follow your organization’s software-review process. The maintainer documents checking the ZIP’s Windows Properties for an Unblock option before extraction when Windows has marked the download as blocked.
Extract the archive into a working folder. Each Revit version variant contains its own server folder with the matching MCP bundle. Preserve that extracted copy so the Revit plugin and Claude-side bundle come from the same release variant.
Step 3: install the Revit add-in for your version
Open the appropriate year-specific add-ins path from the version list above. Create the year folder if it does not already exist. Copy the manifest and complete companion folder from the correct release variant into it. Do not put the entire ZIP, or an extra outer Revit2025Plus directory, inside the target folder and expect Revit to discover the nested manifest.
Restart Revit and follow your organization’s policy for any add-in trust prompt. Look for the Revit Claude Connector ribbon controls. The maintainer’s screenshot shows the Claude Panel, Tools, Restart Claude, Reload Tools, and Status controls. Exact styling may differ in your installed release.
Screenshot: Revit Claude Connector ribbon and docked Claude window, published by the project maintainer. Original image and source.
Step 4: install the matching Claude Desktop extension
Inside your selected Revit2024 or Revit2025Plus variant, find server/Revit.Claude.Connector.Mcp.Server.mcpb. Follow the maintainer’s local-extension installation instructions: use Claude Desktop’s extension settings or its supported bundle installation flow, then restart Claude Desktop.
If your organization manages extension installation, have the administrator deploy the reviewed bundle through the approved route. Do not substitute a web custom-connector field: a locally installed bundle and a hosted remote MCP endpoint use different connection paths.
Once installed, make the Revit connector available to the conversation through Claude’s connector controls. The maintainer’s screenshot shows a connector toggle and tool-access options. Treat those labels as a visual reference, since Claude Desktop’s interface evolves independently of the Revit plugin.
Screenshot: the maintainer’s Claude connector and tool controls. Original image and source.
Step 5: check the bridge before asking for model work
In Revit, open the connector’s Status dialog. The documented healthy state is Bridge: Running with a local address and loaded tools. A visible Claude window alone does not establish that Revit’s bridge is running.
Screenshot: the maintainer’s Status dialog showing a running bridge. The tool count and local address shown are examples from that screenshot. Original image and source.
Start with a read-only request that has an obvious answer: “Use the connected Revit model to report the active view name and type. Do not modify the model.” Check the answer against Revit. Then ask for the IDs and categories of a few selected elements and compare those values with the actual selection.
Only after those checks should you try a small, explicit write on the disposable model. Specify the target element, the property, and the exact intended value. Inspect the result in Revit and confirm that you understand how to reverse it. Successful tool discovery, a plausible chat answer, and a correct native model change are three different milestones.
Troubleshooting Claude MCP connections to Revit
No ribbon controls: Check the Revit year, the runtime variant, and the directory nesting. Confirm that both the .addin file and its companion folder are present. Close and restart Revit after correcting the installation.
Ribbon appears, but Claude has no Revit tools: Check that the matching .mcpb bundle is installed and enabled in Claude Desktop. Restart Claude and open a new conversation. Review any managed-extension restriction with the administrator.
Claude can see tools, but requests cannot reach the model: Check the bridge Status dialog, keep Revit open with the intended project active, and close any modal Revit dialog. Confirm the active document with a read-only query before retrying a write.
A request reaches the connector but cannot perform the task: Inspect the selected connector’s available tools. An unsupported operation is different from a broken connection. Reduce the request to one operation with an explicit target and output.
Changes to plugin files do not appear in Revit 2024: The v1.0.6 release notes say hot reload is not supported for Revit 2024. Restart Revit after DLL changes instead of relying on Reload Tools.
Maintenance: keep the version combination visible
As of our check, v1.0.6 was the latest published release we found. That release date does not establish continuing support for every later Claude update. Before rolling out the connector broadly, review the repository’s current releases and issues, keep the previous working package, and record a simple read/write verification procedure for your office.
The project publishes its source under the Mozilla Public License 2.0. The reproduced screenshots remain credited to their source; no screenshot here is an ArchiLabs product demonstration.
ArchiLabs Desktop: frontier AI for Revit & AutoCAD
If your goal is to delegate project work, ArchiLabs Desktop offers a compelling alternative to assembling and maintaining a separate client-and-connector workflow. Desktop combines leading OpenAI and Anthropic models, reasoning-effort controls, rich inputs, native application connections, and editable knowledge libraries.
Bring the equipment PDF, the Excel register, an annotated capture, a narrated screen recording, or a native model selection into the assignment. Desktop’s native scope includes modeling, families, routing, schedules, tags, dimensions, and sheets. Its public equipment recording shows a specification becoming a native Revit family and then a placed model instance.
Personal, project, team, and company libraries keep recurring instructions readable and editable, with supporting files and revision history. That gives the office a practical way to retain standards while the actual project assignments change. Explore ArchiLabs Desktop, or use our version-and-skill comparison to choose the right approach for your team.
Follow a Revit 2027 drawing-package workflow, see Autodesk Assistant’s documented boundaries, and explore ArchiLabs Desktop’s frontier AI alternative.
Explore Autodesk Assistant’s Revit 2027 limits, view filters, Dynamo dependencies, and why ArchiLabs Desktop is a strong production-work alternative.
See how ArchiLabs Desktop combines frontier models, rich project context, native Revit and AutoCAD work, and reusable knowledge beyond Autodesk Assistant.