rvt-mcp
A local MCP gateway that lets AI agents query and modify a running Autodesk Revit session through typed tools and a C# escape hatch.
At a Glance
Self-hosted local MCP gateway for Autodesk Revit, licensed under Apache License 2.0 with no-charge, royalty-free terms.
Engagement
Available On
Listed Nov 2026
About rvt-mcp
rvt-mcp is an open-source MCP server for Autodesk Revit published by the bimwright organization under the Apache-2.0 license. A .NET 8 server speaks MCP over stdio and connects to a thin add-in running inside Revit 2022–2027. The latest release listed is v1.2.0.
What It Is
rvt-mcp is a local bridge between an MCP client and a running Revit session. The server reaches the add-in over localhost TCP (Revit 2022–2024) or a named pipe (Revit 2025 and later). Per the README, nothing leaves the machine, and lengths are in millimetres at the tool boundary. Agents get a typed tool surface for common Revit work, plus a C# escape hatch (revit_send_code_to_revit) for tasks that no typed tool covers. Family Editor authoring is stated to be out of scope for now.
Tool Surface and Toolsets
The v1.2.0 release exposes 237 tools with all toolsets enabled, or 50 for a bare server (query, create, view, meta). Toolsets cover querying, creation, views and sheets, schedules, families, modification, annotation, export (PDF/DWG/IFC/NWC), MEP, graphics, materials, geometry, rooms, links, parameters, structural elements and composite workflows. A read-only mode filters out write-capable tools. Six MCP prompts guide the agent through getting started, drawing layout, change impact, model audit, pre-issue checks and stair creation.
Safety, Targets and ToolBaker
The server binds to a single Revit instance and requires explicit target and document confirmation before writes when several instances run. Controlled failure handling rolls back MCP warnings by default and records issues for review in the add-in History. An optional ToolBaker feature turns repeated patterns into personal tools; adaptive bake is off by default. The README warns that send_code runs arbitrary C# inside Revit and can be disabled.
Setup Path
Installation is Windows-focused. Users can have an AI agent follow AGENTS.md, or run the PowerShell installer, which registers the add-in for every detected Revit version and wires clients such as Claude Desktop or Claude Code. A Claude Desktop MCPB extension and a NuGet server package are also available. The add-in UI is offered in 15 languages.
Community Discussions
Be the first to start a conversation about rvt-mcp
Share your experience with rvt-mcp, ask questions, or help others learn from your insights.
Pricing
Open Source (Apache-2.0)
Self-hosted local MCP gateway for Autodesk Revit, licensed under Apache License 2.0 with no-charge, royalty-free terms.
- Licensed under Apache-2.0
- Local MCP server (.NET 8) plus per-year Revit add-ins (2022-2027)
- 237 MCP tools
- Optional ToolBaker for personal tools
- Forks and rebrands welcome under license terms
Capabilities
Key Features
- 237 typed Revit tools across 23 toolsets
- C# send_code escape hatch
- ToolBaker personal tools with optional adaptive bake
- Read-only mode and per-tool annotations
- Multi-instance Revit target selection and document verification
- Controlled failure rollback with History and Issues review
- Change tracking and change-impact survey
- Response guard for oversized outputs
- Six built-in MCP prompts
- Add-in UI in 15 languages
- Activity toasts in Revit
- Claude Desktop MCPB extension
Integrations
Demo Video

