Install Git, which you need for the clone step below
winget install --id Git.Git -e --source winget
‣
Turn on pyRevit Routes (in Revit)
In Revit, go to the pyRevit tab → Settings → Routes and turn on Routes Server. pyRevit then listens at http://localhost:48884/.
‣
Get the MCP Server Code (in PowerShell)
Clone the repo somewhere permanent, such as C:\Tools:
powershell
cd C:\Tools
git clone https://github.com/mcp-servers-for-revit/mcp-server-for-revit-python
Then rename the folder so it ends in .extension, for example mcp-server-for-revit-python.extension.
‣
Install and Enable the Revit-MCP-Python Extension (in Revit)
Go to pyRevit tab → Settings → Custom Extensions and add the folder that contains your .extension folder (in this example, C:\Tools).
Save, then reload pyRevit. You may need to restart Revit completely.
pyRevit’s Extensions manager also has an install option. However, the clone gives you the main.py file the MCP server needs anyway, so using that single copy for both is simpler.
Enable the MCP Extension
pyRevit > Extensions
Choose the revit-mcp-python extension
Click Enable
‣
Install the Python Dependencies (in PowerShell)
In the repo folder, run:
powershell
cd C:\Tools\mcp-server-for-revit-python.extension
uv sync
‣
Pair Revit with the MCP Server (in Revit)
Open a project in Revit and choose MCP → Bridge → Connect, then approve the consent prompt. This creates an encrypted pairing secret for your Windows user.
‣
Test the Connection from the Repo Folder (in PowerShell)
powershell
cd c:\Tools\mcp-server-for-revit-python.extension
uv run --frozen python -c "import anyio; from main import revit_get; print(anyio.run(revit_get, '/status/'))"
You should get back "status": "active" and "health": "healthy". Opening the URL in a browser won’t work for this test, because the browser request isn’t paired and gets denied.
If you received errors or don’t get "status": "active" and "health": "healthy"
Copy the PowerShell error messages into Claude and ask it to help you debug the error.
Claude will suggest fixes to try running in PowerShell.
This took several iterations to fully debug the installation on my computer (an M5 MacBook running Parallels with Windows ARM), but persistence paid off.
Claude eventually debugged all the errors and solved the problems created by the computer’s unusual setup.