What it takes off you is the round trip through the Revit API: ask in words which levels, views and families the project has, get a view back as an image, and place a component — without writing C# or opening the API reference.
A bridge between an MCP client and Autodesk Revit. The server speaks MCP on one side and, on the other, makes HTTP calls to a pyRevit Routes REST API running inside the Revit process, so every answer comes from the document that is open.
- Which document is open, and whether the Revit side is answering at all
- Every level in the model, and every view, listed by name
- A view returned as an image you can look at
- The family categories the project uses, and the families loaded under them
- A loaded family placed into the model
Autodesk Revit with pyRevit installed and its Routes module running — the MCP server reaches it over a local HTTP port. The Routes API is in draft form and carries no authentication of its own, so keep that port local and add your own controls before using it anywhere shared.
One command — mcp install main.py