FFaris the Explorer

FIELD GUIDE / REVIT 2025

Revit MCP
v2.2.1 setup.

A standalone setup, verification and troubleshooting guide for connecting Claude Desktop to Autodesk Revit 2025.

← Documentation home

Revit MCP v2.2.1 for Revit 2025

This guide documents a reproducible setup for the mcp-servers-for-revit v2.2.1 Revit 2025 release with Autodesk Revit 2025 and Claude Desktop. It is based on the release package and a working Windows configuration. Paths marked as a reference setup may need adjustment on another computer.

Scope and status: This page is prepared for technical review. The matching GitHub release package and its installation instructions remain the source of truth for official installation details. This guide is hosted independently here; external references are provided for verification, not to host this page.

Contents

Versions and prerequisites

This guide focuses on Revit 2025. If using Revit 2023, 2024 or 2026, do not copy Revit 2025 compiled files or folder paths into another Revit-year folder. Find a package matching the installed Revit version, if available, and follow that release's instructions.

Required for this walkthrough:

  • Autodesk Revit 2025 installed and licensed.
  • Claude Desktop installed.
  • Release ZIP named mcp-servers-for-revit-v2.2.1-Revit2025.zip.

Official references: Revit MCP repository, releases, and installation guide.

The prebuilt release includes a portable Node.js runtime, so a separate system-wide Node.js installation is not normally required just to use the prebuilt package. The repository lists Node.js 18+ and .NET 8 SDK as build requirements for compiling the server/plugin from source for Revit 2025; those are not the same as prerequisites for using the prebuilt release.

Install the release

  1. Close Revit.
  2. Press Windows + R.
  3. Enter %AppData%\Autodesk\Revit\Addins\2025 and press Enter.
  4. Extract the Revit 2025 release ZIP contents directly into that folder.

The release ZIP root contains these items:

  • revit_mcp_plugin — plugin and MCP server files.
  • scripts — helper scripts included with the package.
  • INSTALLa — Windows batch file.
  • DISINSTALLA — Windows batch file.
  • mcp-servers-for-revit.addin — Revit add-in manifest.

Follow the current official guide for whether to run any helper script. Do not run the uninstaller, and do not run an installer script without understanding its effect on an existing installation.

Expected key layout:

%AppData%\Autodesk\Revit\Addins\2025\
├── mcp-servers-for-revit.addin
└── revit_mcp_plugin\
    ├── RevitMCPPlugin.dll
    └── Commands\
        └── RevitMCPCommandSet\
            ├── command.json
            ├── 2025\RevitMCPCommandSet.dll
            └── server\
                ├── build\index.js
                ├── node_modules\
                ├── runtime\node.exe
                └── package.json

The package may include additional files. Check that the manifest is directly inside Addins\2025 and the version-specific command assembly and server files exist.

Verify the Revit ribbon

  1. Open Revit 2025.
  2. If Revit presents an add-in security prompt, review it and choose Always Load only if you trust the package source.
  3. Open the Add-Ins tab and look for the Revit MCP Plugin panel.
  4. Confirm it contains Revit MCP Switch, MCP Panel, and Settings controls.
  5. Open the target project. For a cloud-hosted model, use the normal Autodesk Docs/BIM 360 workflow.
  6. Click Revit MCP Switch to start the local MCP service.

The release documentation identifies TCP port 8080 for the local Revit service.

Configure Claude Desktop

Press Windows + R and open %AppData%\Claude. Locate claude_desktop_config.json and back it up before editing. If other MCP servers are already configured, preserve those entries.

Reference configuration used on a working Revit 2025 computer

Replace <WINDOWS_USERNAME> with the Windows account folder name. This reference launches the bundled Node executable directly:

{
  "mcpServers": {
    "revit-mcp": {
      "command": "C:\\Users\\<WINDOWS_USERNAME>\\AppData\\Roaming\\Autodesk\\Revit\\Addins\\2025\\revit_mcp_plugin\\Commands\\RevitMCPCommandSet\\server\\runtime\\node.exe",
      "args": [
        "C:\\Users\\<WINDOWS_USERNAME>\\AppData\\Roaming\\Autodesk\\Revit\\Addins\\2025\\revit_mcp_plugin\\Commands\\RevitMCPCommandSet\\server\\build\\index.js"
      ]
    }
  }
}

This is a reference setup, not a universal config for every release. The official guide may use a different method or server key. Follow the instructions for the downloaded release and use this direct-path example only when the files exist at those paths.

Save the JSON, fully quit Claude Desktop (including its system-tray process), then reopen it. In Claude Desktop settings, check that the Revit MCP server is shown as running.

Test the connection

With Revit open, the target model active, and the MCP switch enabled:

  1. Confirm Claude Desktop reports the server as running.
  2. Confirm the Revit tools are available in Claude.
  3. If say_hello is available, use it with a simple message such as Connection test.
  4. Try a read-only query, such as “Tell me the project name of the currently open Revit model” or “List the levels in the currently open model.”

Verify the response refers to the intended model before asking Claude to modify anything.

Autodesk Docs / BIM 360 workflow

MCP communicates with the active Revit Desktop session; it is not a direct connection from Claude to Autodesk Docs/BIM 360.

  1. Open Revit 2025.
  2. Open the cloud model through the normal Autodesk Docs/BIM 360 workflow.
  3. Wait for the model to finish loading.
  4. Start the MCP service with Revit MCP Switch.
  5. Confirm Claude Desktop has connected and can read model information.
  6. Start with read-only requests. Before edits, confirm the correct cloud model is open and follow the project's worksharing and change-control procedures.

Troubleshooting

Plugin does not appear in Revit

  • Check that mcp-servers-for-revit.addin is directly inside the correct Revit-year Add-ins folder.
  • Confirm the ZIP matches Revit 2025.
  • Review any Revit add-in load warning.
  • Consult the official troubleshooting section.

Claude shows the server as running, but no tools work

  • Confirm Revit is open and the intended project is active.
  • Click Revit MCP Switch and verify the service is active.
  • Check that the configured node.exe and index.js paths exist.
  • Fully restart Claude Desktop after a config change.

Connection refused or intermittent connection

  • The local service may not be listening when Claude attempts to connect.
  • Confirm the Revit MCP service is started and TCP port 8080 is available.
  • From Command Prompt, check port usage:
netstat -ano | findstr :8080
  • Review Revit's journal and MCP logs if the problem persists.

Built-in Revit chat asks for an API key

The plugin's built-in chat panel has a separate Anthropic API-key requirement according to the project documentation. That key is not required just to use the tools through Claude Desktop. Never put an API key in a public guide or share one in screenshots.

Updating and uninstalling

Before updating, close Revit and back up the current plugin folder and Claude configuration. Follow the current release instructions and use a ZIP matching the Revit version. Do not copy compiled DLLs from a different Revit-year build into the Revit 2025 folder.

For uninstalling, follow the official guide and confirm the target folder carefully before deleting the manifest or plugin directory.

Validation checklist

Before treating this as a universal procedure, confirm that the exact release ZIP is still available, current release instructions match this page, the direct-path Claude configuration works on a second computer, ribbon controls and any say_hello test work, and any machine-specific compatibility modifications are documented separately from official installation steps.

References