rvt-mcp

What it is

rvt-mcp is a local bridge between an MCP client and a running Revit session. A .NET 8 server talks MCP over stdio; a thin add-in per Revit year (2022–2027) runs inside Revit and is reached over localhost TCP (≤2024) or a named pipe (≥2025). Nothing leaves the machine, it is C# end to end, and lengths are millimetres at the tool boundary. Details: ARCHITECTURE.md.

Agents get a typed tool surface for common Revit work, a C# escape hatch for everything else, and an optional way to turn repeated patterns into personal tools (ToolBaker): start from a shared runtime and grow your tools on top. Family Editor authoring is out of scope for now (roadmap).

Related MCP server: Revit MCP Server

Install

For users: let your AI agent do it. You don't need to run anything yourself. Copy the line below, paste it into your AI agent (Claude Code, Codex, Cursor, …) and go get a coffee while it does the job. The agent follows AGENTS.md and asks you before it installs anything or edits your client config.

Install rvt-mcp for me: https://github.com/bimwright/rvt-mcp

Or run the installer yourself. Close Revit, then in PowerShell:

$tag = (Invoke-RestMethod https://api.github.com/repos/bimwright/rvt-mcp/releases/latest).tag_name
$dir = "$env:TEMP\RvtMcp.Setup-$tag-win-x64"
Invoke-WebRequest "https://github.com/bimwright/rvt-mcp/releases/download/$tag/RvtMcp.Setup-$tag-win-x64.zip" -OutFile "$dir.zip"
Expand-Archive "$dir.zip" -DestinationPath $dir -Force
powershell -ExecutionPolicy Bypass -File "$dir\install.ps1"

One run sets up both sides: the add-in for every Revit 2022–2027 on the machine, and the rvt-mcp entry in every MCP client it finds (each config is backed up first). Add -WhatIf to preview, -Client claude,cursor to wire only those clients, or -Client none to skip client configs and register the server yourself — it lives at %LOCALAPPDATA%\RvtMcp\rvt\server\current\rvt-mcp.exe (per-client steps).

Check it works: restart your AI client, open a model in Revit, start MCP from the ribbon (Add-Ins → RvtMcp) and ask the agent to call revit_get_current_view_info. It should return the active view's name and type.

Upgrade: run the new release's installer the same way — no uninstall first; clients only need a restart. Uninstall: uninstall.ps1 -Yes in the same folder removes the add-ins and the server (settings stay unless you add -Purge); run install.ps1 -Uninstall -Client auto first to also remove the client entries. More, including developer and NuGet installs: docs/install.md.

Videos

Community videos of rvt-mcp at work. Install steps shown in a video can be older than this README — follow the steps above.

• Connecting ChatGPT Astra to Revit | Testing AI Changes in a Real Project — Revit Mentor

• Exploring Revit + GPT 6 Astra — BIM Pure

• GPT-6 Astra Built a Revit House in 14 Minutes — Archi Vlogs

Tools

Counts exclude your personal baked tools. The installer writes the seeded default only when rvtmcp.config.json doesn't already set toolsets — your own list survives upgrades, and removing the key (or setting your own CSV) returns a bare server to the 41-tool surface. --read-only drops every write-capable toolset (including create) regardless of source.

send_code, ToolBaker, ribbon and languages

• revit_send_code_to_revit (on by default) compiles and runs a C# body inside Revit when no typed tool fits; --read-only or --disable-toolbaker removes it. See docs/send-code.md, and docs/stairs-workflow.md for stairs.

• ToolBaker: revit_list_baked_tools / revit_run_baked_tool need --toolsets toolbaker. Adaptive bake (--enable-adaptive-bake, off by default) suggests tools from repeated calls; nothing is added until you accept one. Bake compiles inside Revit — no Visual Studio needed. See docs/bake.md.

• Ribbon: start or stop the connection, open History to search and re-run past calls, and switch completion Toasts (on by default).

• UI languages: the add-in UI comes in 15 languages and follows Revit's UI language; change it with the Language button in the ribbon slide-out — it opens Settings → General → Language (BIMWRIGHT_UI_LANGUAGE still wins). Tool names and payloads stay English. See docs/localization.md.

Prompts

Four ready-made workflows ship as MCP prompts — pick /mcp__rvt-mcp__revit_<name> (Claude Code) or the prompts menu (Claude Desktop), and the agent follows the script with the tools it already has:

• revit_getting_started — orient in the open model (read-only, works on defaults).

• revit_model_audit — health audit: warnings, families, dry-run purge candidates (needs workflows,families,lint,meta).

• revit_pre_issue_check — checks resolved sheets before issue (needs sheets,view,annotation,lint,meta). Supply sheet numbers/IDs, an explicit number/name filter, or all; a named sheet set needs its member sheets. Sampled model warnings and incomplete checks are reported as NOT VERIFIED, not a sheet-level pass.

• revit_stairs — guided stair creation through send_code (writes only after your confirmation). Includes the transaction/failure/cleanup template; no source checkout is needed.

If a prompt's toolsets aren't enabled, it answers with the exact --toolsets line to add — nothing runs half-configured. Read-only protection stays on when the missing tools allow it; prompts requiring write-capable toolsets explain the conflict rather than silently changing configuration. Prompts are instructions for the agent, not server-enforced workflow locks.

Configuration

Precedence, high wins: CLI → env (BIMWRIGHT_*) → %LOCALAPPDATA%\RvtMcp\rvtmcp.config.json.

After changing server flags, restart the MCP connection so the client picks up the new tool list.

Supported Revit versions

Full Revit desktop only; Revit Viewer is not a supported target. CI builds all six add-ins, but runtime depth varies by year — recheck baked tools and custom C# on the years you use.

Security and privacy

• Local by default: loopback TCP or a local named pipe, with a per-session auth token in the discovery files under %LOCALAPPDATA%\RvtMcp\.

• Tool arguments are schema-checked before handlers run; errors returned to the model are sanitized.

• send_code runs arbitrary C# in the Revit process — powerful and risky. Use --read-only or --disable-toolbaker if that is unacceptable.

• Adaptive bake, body cache and send_code journals are opt-in and stay under your user profile; defaults do not write raw send_code bodies to long-lived logs.

More: SECURITY.md, docs/bake.md.

Docs

Community contributions

Code, bug reports, reproducible examples and proposals help improve rvt-mcp. Thanks to:

bimwright

Open-source tools connecting AI assistants to BIM and CAD applications.

The name bimwright combines BIM with wright, an old word for a maker or builder—as in shipwright.

• rvt-mcp — Revit

• dwg-mcp — AutoCAD

• nwd-mcp — Navisworks

• ipt-mcp — Inventor

• bim-wiki — Vietnamese-first BIM notes

License

Apache-2.0 — LICENSE.

Forks and rebrands are welcome — the license terms are all that's required (keep LICENSE and the copyright notices, mark changed files). If rvt-mcp helped you, a star or a mention of BIMwright in your product is appreciated but entirely optional. Issues and PRs are always welcome.

Revit and Autodesk are trademarks of Autodesk, Inc. bimwright is independent and not affiliated with Autodesk.