Revit MCP guide · Start

Connect Claude

Tell Claude Desktop or Claude Code where the Revit server is. One tick box or one line.

Claude Desktop

If you ticked Connect Claude Desktop in the installer

It is already done. Start Claude Desktop again (if it was open, quit it fully from the tray icon first, then start it) and go to Check the connection.

If you did not

  1. Quit Claude Desktop fully

    Right-click its icon in the Windows tray and choose Quit. Closing the window is not enough.
  2. Run this line in PowerShell

    powershell -NoProfile -ExecutionPolicy Bypass -File "$env:LOCALAPPDATA\Programs\Lavart\RevitMcp\server\connect-claude-desktop.ps1" -Exe "$env:LOCALAPPDATA\Programs\Lavart\RevitMcp\server\revit-mcp.exe"
    It adds the Revit server to Claude Desktop under the name revit-pro, and keeps a backup copy of the settings file it changes.
  3. Start Claude Desktop

Claude Code

One line in a terminal. In PowerShell, which is the Windows default:

claude mcp add revit-pro -- "$env:LOCALAPPDATA\Programs\Lavart\RevitMcp\server\revit-mcp.exe"

In the older Command Prompt, use this form instead:

claude mcp add revit-pro -- "%LOCALAPPDATA%\Programs\Lavart\RevitMcp\server\revit-mcp.exe"

Either one tells Claude Code that a server named revit-pro exists and where its program is. Run it once per Windows user.

Other assistants

It is a standard MCP server, so other assistants that speak MCP, such as Cursor and VS Code, can use it. In that assistant’s MCP settings, add a server that starts this program, with no arguments:

%LOCALAPPDATA%\Programs\Lavart\RevitMcp\server\revit-mcp.exe
We build and test with Claude Desktop and Claude Code first. Other assistants should work, and we would like to hear when one does not.

Check the connection

  1. Start Revit and open a project

  2. Ask your assistant: What is open in Revit?

    It should answer with the name of your file. In Revit, the status button on the lAvArt MCP panel shows the assistant as connected.

Working? Next: Your first prompt.

Something here wrong, or missing? Write to info@lavart.ai.