# Bimwright [Health: Active] **Category:** ๐Ÿ’ป Developer Tools **Repository:** https://github.com/bimwright/rvt-mcp **GitHub Stars:** 19 **Views:** 0 **Installs:** 0 **Upvotes:** 0 **Directory Page:** https://allmcps.com/mcp/bimwright ## Description MCP gateway for Autodesk Revit 2022-2027 - toolset gating + Transaction-safe batch execution. ## Claude Desktop Quick Installation Heuristic fallback โ€” verify the package name and runner against the repository README before running it. Uses `npx` (confidence: low): ```json "mcpServers": { "bimwright": { "command": "npx", "args": ["-y","bimwright"] } } ``` ## Documentation & README

rvt-mcp

rvt-mcp

MCP gateway for Autodesk Revit โ€” local tools for agents, optional personal bake loop

build license Revit 2022-2027 MCP tools

English ยท Tiแบฟng Viแป‡t ยท ็ฎ€ไฝ“ไธญๆ–‡ ยท ๆ—ฅๆœฌ่ชž

--- ## Install Client machines should use the setup ZIP from [GitHub Releases](https://github.com/bimwright/rvt-mcp/releases/latest). It bundles a self-contained MCP server and Revit 2022โ€“2027 plugins โ€” no .NET SDK, NuGet global tool, or source clone. **AI agents:** download `RvtMcp.Setup-*-win-x64.zip` from the latest release and run the installer. Do **not** clone, build, or `dotnet tool install` unless the user asked for a developer setup. Protocol: [AGENTS.md](https://github.com/bimwright/rvt-mcp/blob/HEAD/AGENTS.md). ```powershell $tag = (Invoke-RestMethod https://api.github.com/repos/bimwright/rvt-mcp/releases/latest).tag_name $zip = "$env:TEMP\RvtMcp.Setup-$tag-win-x64.zip" $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 $zip Expand-Archive $zip -DestinationPath $dir -Force powershell -ExecutionPolicy Bypass -File "$dir\install.ps1" -WhatIf powershell -ExecutionPolicy Bypass -File "$dir\install.ps1" ``` The installer detects Revit 2022โ€“2027, installs matching plugins, copies the server under `%LOCALAPPDATA%\RvtMcp\rvt\server\\`, and wires detected MCP clients. Override with `-Client codex|opencode|claude|kilo|none`. Do **not** install v0.5.0 or earlier ZIPs. Do **not** `dotnet tool install -g Bimwright.Rvt.Server` (legacy 0.1โ€“0.3). Do **not** use NuGet instead of this ZIP on a Revit client machine โ€” the tool package has no add-in. For AutoCAD, use [dwg-mcp](https://github.com/bimwright/dwg-mcp) separately โ€” different product, different install. ### Check that it works 1. Open Revit with a model. 2. Start the MCP connection from the ribbon (BIMwright / RvtMcp panel). 3. From the MCP client, list tools, then call `revit_get_current_view_info`. You should get something like: ```json { "viewName": "Level 1", "viewType": "FloorPlan", "levelName": "Level 1", "scale": 100 } ``` If that fails, install is not done yet โ€” fix client config / plugin load before anything else. ### Uninstall From the setup ZIP root (or this repoโ€™s `scripts/`): ```powershell # Setup ZIP layout: powershell -ExecutionPolicy Bypass -File .\uninstall.ps1 -WhatIf powershell -ExecutionPolicy Bypass -File .\uninstall.ps1 -Yes # Clone layout: powershell -ExecutionPolicy Bypass -File .\scripts\uninstall-all.ps1 -WhatIf powershell -ExecutionPolicy Bypass -File .\scripts\uninstall-all.ps1 -Yes ``` Removes plugins, self-contained server, client entries, discovery files, logs, and ToolBaker cache. ### Developer install ```powershell git clone https://github.com/bimwright/rvt-mcp.git cd rvt-mcp dotnet build src/RvtMcp.sln -c Debug powershell -ExecutionPolicy Bypass -File .\scripts\install.ps1 -SourceDir . -Client none ``` Close every Revit first โ€” the build deploys plugin DLLs into `%APPDATA%\Autodesk\Revit\Addins\\RvtMcp\`. `install.ps1` finds Revit 2022โ€“2027, copies the server under `%LOCALAPPDATA%\RvtMcp\rvt\server\\`, and wires detected MCP clients (`-Client codex|opencode|claude|kilo|none`, `-Years 2024` for one year). **Optional โ€” NuGet server only** (does **not** install Revit plugins). Use this if the add-in is already on the machine (ZIP or a local build) and you want the MCP server on PATH: ```powershell dotnet tool uninstall -g Bimwright.Rvt.Server # skip if you never installed the 0.1โ€“0.3 tool dotnet tool install -g RvtMcp.Server --version 0.6.1 ``` Command name: `rvt-mcp`. Keep using the GitHub Release ZIP for plugins. `Bimwright.Rvt.Server` is obsolete. ### Migrating from `Bimwright.Rvt.*` (v0.3 and earlier) v0.4+ renamed packages and folders to `RvtMcp.*` (repo name and brand stay bimwright). 1. Close every Revit. 2. `pwsh scripts/uninstall-old.ps1` โ€” drops old `%APPDATA%\โ€ฆ\Bimwright\` plugins and old server root; keeps user bake/journal data and migrates it to `%LOCALAPPDATA%\RvtMcp\` on first new launch. 3. Install the current GitHub Release ZIP (Client install above). Do not install v0.5.0 or earlier packages. Uninstall the old global tool if present: `dotnet tool uninstall -g Bimwright.Rvt.Server`. 4. Point MCP clients at entry name **`rvt-mcp`** (old per-year `bimwright-rvt-r22`โ€ฆ entries are removed by the installer). --- ## What this is `rvt-mcp` is a **local** bridge between an MCP client (Claude, Cursor, Codex, OpenCode, โ€ฆ) and a running Revit session. Two processes: | Piece | Role | |--------|------| | **RvtMcp.Server** | .NET 8 MCP server on stdio. No Revit reference โ€” builds anywhere. | | **RvtMcp.Plugin** | One thin add-in per Revit year (2022โ€“2027). Runs inside Revit, executes on the UI thread. | Agent โ†’ MCP โ†’ server โ†’ localhost TCP (โ‰ค2024) or Named Pipe (โ‰ฅ2025) โ†’ plugin โ†’ Revit API. Everything stays on the machine. No cloud relay is required for the gateway itself. There is no Node/TypeScript sidecar. Server, plugins, handlers, and ToolBaker are C# end to end. Shared command code lives in `src/shared/`; each year is a small shell project with `#if` where the API drifted. Details: [ARCHITECTURE.md](https://github.com/bimwright/rvt-mcp/blob/HEAD/ARCHITECTURE.md). --- ## Why it exists People who live in Revit already know what they want automated. The friction was always shipping that idea as software: learn enough C#/Dynamo, fight the API, package an add-in, survive version upgrades โ€” or pay someone else, or buy a fixed tool that only half-matches the office. Agents change the first half of that loop (describe the task, try it live). They do not remove transactions, units, selection, worksharing, or โ€œdid this just trash the model?โ€ That is what this gateway is for: a **typed tool surface** for common work, plus an escape hatch when you need ad-hoc C# inside Revit, plus an **optional** path to turn repeated local patterns into personal tools (ToolBaker). It is not a universal add-in for every firm. Offices differ. The bet is: start from a shared runtime, grow *your* tools on top. **Scope posture (honest):** we do not mint a new MCP tool for every edge case. Prefer typed tools when they exist; for everything else use `revit_send_code_to_revit` (C# only). Family *project* management is covered; full Family Editor authoring suites and Revit Viewer hosts are out of scope for now โ€” see [docs/roadmap.md](https://github.com/bimwright/rvt-mcp/blob/HEAD/docs/roadmap.md). --- ## How a normal session looks 1. Revit open with a model; plugin connected (ribbon). 2. MCP client starts `rvt-mcp` / the installed server. 3. Agent uses tools: query view/selection, create grids/rooms, sheets, MEP, export, โ€ฆ Lengths in **mm** at the tool boundary. 4. Several writes in one undo step: `revit_batch_execute`. 5. Multiple Revits running: `revit_list_available_targets` then `revit_switch_target` with a four-digit year (`2024`, not `R24`). When no typed tool fits: ```text revit_send_code_to_revit # C# body, compiled and run inside the plugin ``` That tool is on by default (toolset `meta`). Strip it with `--read-only` or `--disable-toolbaker` if you do not want agents compiling code in the model. ### ToolBaker (optional) Default surface includes `revit_send_code_to_revit`. `revit_list_baked_tools` / `revit_run_baked_tool` need `--toolsets toolbaker` (or `--toolsets all`). **Adaptive bake** (suggest new tools from usage) is **off** unless you enable it. When on, repeated patterns can show up under `revit_list_bake_suggestions`; you accept or dismiss explicitly. Nothing ships itself into your ribbon without that step. Useful flags (also JSON / env โ€” see [Configuration](#configuration)): | Goal | What to turn on | |------|------------------| | Learn tools from repeated **typed** calls | `--enable-adaptive-bake` | | Also cluster **`send_code`** bodies for suggestions | plus `--cache-send-code-bodies` (redacted; still local) | | Short-lived disk journal of send_code bodies | `persistSendCodeBodies` + TTL (default privacy keeps this off) | Bake compile runs **inside Revit** via Roslyn โ€” end users do not need Visual Studio. Details and privacy notes: [docs/bake.md](https://github.com/bimwright/rvt-mcp/blob/HEAD/docs/bake.md). ### Toast (optional) Completion toast in Revit is **off** by default. Turn on with the ribbon **Toast** button, `enableToast` in config, or `BIMWRIGHT_ENABLE_TOAST=1`. Only finished calls are shown (no โ€œin progressโ€ toast). Capture success can show a thumbnail when the file sits under the path allowlist. Ribbon **Status** also prints toast + bake/privacy flags so you can see what is enabled without guessing. --- ## Architecture (short) ```text MCP client (stdio) โ†’ RvtMcp.Server (.NET 8) โ†’ TCP (Revit 2022โ€“2024) or Named Pipe (2025โ€“2027) โ†’ Plugin shell (per year) โ†’ ExternalEvent โ†’ Revit API / transactions / undo ``` Handlers return plain DTOs โ€” never live Revit objects on the wire. --- ## Tools Counts (without counting personal baked tools): | Mode | Tools | Notes | |------|------:|-------| | Default | **40** | `query` + `create` + `view` + `meta` | | `--toolsets all` | **229** | Full catalog | | `all` + adaptive bake | **232** | Adds 3 suggestion-lifecycle tools | Tool names are MCP-facing as `revit_*`. Wire names between server and plugin stay unprefixed snake_case. **Default-on toolsets:** `query`, `create`, `view`, `meta` **Off unless you ask:** everything else (`export`, `geometry`, `mep`, `structural`, `toolbaker`, `modify`, `delete`, โ€ฆ). Example: `--toolsets query,view,meta` or `--toolsets all`. `--read-only` drops every write-capable toolset (including `create`). | Toolset | What it covers | Default | |---------|----------------|---------| | `query` | View, selection, filters, stats, parameters, relationships, worksets, groups/assemblies | on | | `create` | Grids, levels, rooms, line/point/surface-based elements, groups | on | | `view` | Create views, sheets layout helpers, capture image, crop/scale | on | | `meta` | Batch execute (max 20), multi-Revit targets, project info, purge unused (MVP), message, send_code | on | | `lint` | View naming patterns, firm-profile detect, warnings summary | off | | `schedule` | List/create schedules, fields, formulas, data | off | | `families` | Load/unload, types, instances, audit, export `.rfa` (project-side) | off | | `modify` | Operate/color elements, set parameters, change type, workset assign | off | | `delete` | Delete by id | off | | `annotation` | Tags, text, dimensions, regions, keynotes, checks | off | | `export` | PDF/DWG/IFC/NWC helpers, room data, and related export tools | off | | `mep` | Systems, connectors, networks, place terminals/fixtures, etc. | off | | `graphics` | View filters, overrides, visibility/phase | off | | `toolbaker` | list/run baked tools; suggestion tools only if adaptive on | off | | `sheets` | Sheets, titleblocks, revisions, renumber | off | | `materials` | Materials, appearance, assignment, takeoff | off | | `geometry` | BBox, measure, clash, volume/area, โ€ฆ | off | | `rooms` | Rooms/areas/spaces, finishes, separators | off | | `links` | Revit/CAD links, coordinate audit, acquire/publish coordinates | off | | `parameters` | Project/shared parameters | off | | `organization` | Saved selections, view templates | off | | `workflows` | Composite clash/audit/sheet/takeoff-style flows | off | | `structural` | Columns, beams, foundations, rebar, loads, โ€ฆ | off | | `kei` | Active KEI project DB path, query/write SQLite (WAL-safe), equipment import | off | ### Representative tools Not a full dump of 200+ schemas โ€” just anchors agents and humans use often: | Toolset | Tool | Role | |---------|------|------| | `query` | `revit_get_current_view_info` | Active view type, level, scale | | `query` | `revit_get_selected_elements` | Current selection | | `query` | `revit_ai_element_filter` | Category + parameter filter (mm) | | `query` | `revit_get_element_details` | Location, bbox, workset, phase, โ€ฆ | | `create` | `revit_create_grid` / `revit_create_level` / `revit_create_room` | Core layout | | `create` | `revit_create_point_based_element` | Doors, furniture, โ€ฆ from type id | | `view` | `revit_capture_view_image` | Raster capture (path allowlist) | | `meta` | `revit_batch_execute` | One `TransactionGroup` for several commands | | `meta` | `revit_list_available_targets` / `revit_switch_target` | Multi-Revit | | `families` | `revit_load_family_from_path` | Load `.rfa` into the project | | `links` | `revit_get_project_coordinate_system` / `revit_get_link_coordinate_system` | Host/link origins, sites, transforms, True North | | `toolbaker` | `revit_send_code_to_revit` | Escape hatch (C#) | | `toolbaker` | `revit_list_baked_tools` / `revit_run_baked_tool` | Personal accepted tools | | `toolbaker` | `revit_list_bake_suggestions` | Adaptive only | | `lint` | `revit_analyze_view_naming_patterns` | Naming outliers | Golden snapshots in tests pin the exact surface; if counts and code disagree, trust tests/code. --- ## Supported Revit versions | Revit | Plugin TFM | Transport | |-------|------------|-----------| | 2022โ€“2024 | .NET Framework 4.8 | TCP | | 2025โ€“2026 | .NET 8 (`net8.0-windows7.0`) | Named Pipe | | 2027 | .NET 10 (`net10.0-windows7.0`) | Named Pipe | Compile matrix covers all six shells. Runtime depth still varies by year โ€” bake and custom C# should be rechecked on the years you care about. **Host:** full Revit desktop only. Revit Viewer is not a supported target. --- ## Security and privacy - Transport is local by default (loopback TCP / local named pipe). - Discovery files under `%LOCALAPPDATA%\RvtMcp\` include a per-session auth token. - Tool arguments are schema-checked before handlers run. - Errors returned to the model are sanitized (path leakage reduced). - `send_code` can run arbitrary C# in the Revit process โ€” powerful and risky; disable toolbaker if that is unacceptable. - Adaptive bake, body cache, and TTL journals are **opt-in** and stay under the user profile. Defaults do not write raw send_code bodies to long-lived logs. More: [SECURITY.md](https://github.com/bimwright/rvt-mcp/blob/HEAD/SECURITY.md), [docs/bake.md](https://github.com/bimwright/rvt-mcp/blob/HEAD/docs/bake.md). --- ## Configuration Precedence, high wins: **CLI โ†’ env (`BIMWRIGHT_*`) โ†’** `%LOCALAPPDATA%\RvtMcp\rvtmcp.config.json`. | Setting | CLI | Env | JSON | |---------|-----|-----|------| | Target year | `--target 2024` | `BIMWRIGHT_TARGET` | `target` | | Toolsets | `--toolsets query,create` | `BIMWRIGHT_TOOLSETS` | `toolsets` | | Read-only | `--read-only` | `BIMWRIGHT_READ_ONLY=1` | `readOnly` | | LAN bind (plugin) | โ€” | `BIMWRIGHT_ALLOW_LAN_BIND=1` | `allowLanBind` | | ToolBaker surface | `--enable-toolbaker` / `--disable-toolbaker` | `BIMWRIGHT_ENABLE_TOOLBAKER` | `enableToolbaker` | | Adaptive bake | `--enable-adaptive-bake` / `--disable-adaptive-bake` | `BIMWRIGHT_ENABLE_ADAPTIVE_BAKE=1` | `enableAdaptiveBake` | | Cache send_code bodies (bake clusters) | `--cache-send-code-bodies` / `--no-โ€ฆ` | `BIMWRIGHT_CACHE_SEND_CODE_BODIES=1` | `cacheSendCodeBodies` | | Persist send_code journal | `--persist-send-code-bodies` / `--no-โ€ฆ` | `BIMWRIGHT_PERSIST_SEND_CODE_BODIES=1` | `persistSendCodeBodies` | | Journal TTL | `--persist-send-code-bodies-for 4h` | `BIMWRIGHT_PERSIST_SEND_CODE_BODIES_TTL` | `persistSendCodeBodiesUntil` | | Completion toast | ribbon **Toast** | `BIMWRIGHT_ENABLE_TOAST=1` | `enableToast` | After changing server flags, restart the MCP connection so the client picks up the new tool list. --- ## MCP clients | Client | Wiring | |--------|--------| | Claude Code | project `.mcp.json` or `~/.claude.json` | | Claude Desktop | `%APPDATA%\Claude\claude_desktop_config.json` | | OpenCode / Codex / Kilo | `install.ps1 -Client โ€ฆ` (scripted) | | Cursor / Cline / VS Code Copilot | documented JSON layouts | | Gemini CLI / Antigravity | `gemini mcp add` or settings JSON | Installer auto-detect is usually enough; see [AGENTS.md](https://github.com/bimwright/rvt-mcp/blob/HEAD/AGENTS.md) and `docs/mcp-config-*.md` when hand-editing. --- ## Repo layout ```text rvt-mcp/ โ”œโ”€โ”€ src/ โ”‚ โ”œโ”€โ”€ RvtMcp.sln โ”‚ โ”œโ”€โ”€ server/ # MCP server โ”‚ โ”œโ”€โ”€ shared/ # Handlers, transport, ToolBaker, toast, โ€ฆ โ”‚ โ”œโ”€โ”€ plugin-r22/ โ€ฆ r27/ # One shell per Revit year โ”œโ”€โ”€ tests/ # xUnit + golden tool lists โ”œโ”€โ”€ scripts/ # install / uninstall / package โ”œโ”€โ”€ docs/ # roadmap, bake, testing โ”œโ”€โ”€ AGENTS.md โ””โ”€โ”€ ARCHITECTURE.md ``` --- ## Development ```bash dotnet test tests/RvtMcp.Tests/RvtMcp.Tests.csproj dotnet build src/server/RvtMcp.Server.csproj -c Release dotnet build src/plugin-r26/RvtMcp.Plugin.R26.csproj -c Release ``` Close Revit before building plugins (DLL lock). Plugin projects deploy into `%APPDATA%\Autodesk\Revit\Addins\\RvtMcp\` on a normal Debug/Release build. ```powershell pwsh scripts/stage-plugin-zip.ps1 -Config Release ``` Contribution norms and snapshot rules: [CONTRIBUTING.md](https://github.com/bimwright/rvt-mcp/blob/HEAD/CONTRIBUTING.md). ### Maturity Usable, not sacred. CI builds the six plugin shells and server tests. Runtime coverage is strongest on mid-range years; treat production models carefully and verify on *your* Revit build. Fresh-machine checklist: [docs/testing/fresh-install-checklist.md](https://github.com/bimwright/rvt-mcp/blob/HEAD/docs/testing/fresh-install-checklist.md). --- ## More docs | Doc | Topic | |-----|--------| | [AGENTS.md](https://github.com/bimwright/rvt-mcp/blob/HEAD/AGENTS.md) | Agent install protocol | | [ARCHITECTURE.md](https://github.com/bimwright/rvt-mcp/blob/HEAD/ARCHITECTURE.md) | Processes, transport, DTO rules | | [docs/bake.md](https://github.com/bimwright/rvt-mcp/blob/HEAD/docs/bake.md) | Adaptive bake and body privacy | | [docs/roadmap.md](https://github.com/bimwright/rvt-mcp/blob/HEAD/docs/roadmap.md) | Near-term hardening and non-goals | | [docs/kei-equipment-import.md](https://github.com/bimwright/rvt-mcp/blob/HEAD/docs/kei-equipment-import.md) | KEI SQLite tools (`--toolsets kei`) | | [CHANGELOG.md](https://github.com/bimwright/rvt-mcp/blob/HEAD/CHANGELOG.md) | Release notes | --- ## bimwright Same house style across AEC hosts: - [rvt-mcp](https://github.com/bimwright/rvt-mcp) โ€” Revit - [dwg-mcp](https://github.com/bimwright/dwg-mcp) โ€” AutoCAD - [nwd-mcp](https://github.com/bimwright/nwd-mcp) โ€” Navisworks - [ipt-mcp](https://github.com/bimwright/ipt-mcp) โ€” Inventor - [bim-wiki](https://github.com/bimwright/bim-wiki) โ€” Vietnamese-first BIM notes --- ## License Apache-2.0 โ€” [LICENSE](https://github.com/bimwright/rvt-mcp/blob/HEAD/LICENSE). Revit and Autodesk are trademarks of Autodesk, Inc. bimwright is independent and not affiliated with Autodesk.