Bimwright

What Bimwright does

Bimwright provides a local MCP bridge for Autodesk Revit versions 2022 through 2027. An MCP client can use it to inspect an open model, query views and elements, review relationships, work with sheets and schedules, and perform selected model operations. The gateway also supports batch execution and a C# escape hatch through send_code.

Its higher-level workflows focus on controlled architectural and BIM tasks. revit_drawing_layout examines actual viewport positions before proposing sheet alignment. revit_change surveys relationships, narrows the requested scope, presents a concrete change, and reads the result back. revit_model_audit reviews warnings, families, and purge candidates, while revit_pre_issue_check evaluates selected sheets or an explicitly named set before issue.

How it works

The gateway runs locally as a .NET 8 MCP server using stdio. A matching Revit add-in runs inside the selected Revit installation and communicates with the gateway over localhost TCP for Revit 2022–2024 or a named pipe for Revit 2025–2027. The implementation is C# end to end, and tool-boundary lengths are expressed in millimetres.

Start Revit with a model open, launch MCP from Add-Ins → RvtMcp, and ask the connected client to call a tool. The getting-started tool can orient an agent in the active model, and a current-view query can verify the connection. Changes are designed around proposals, confirmation, transactions, cleanup, and read-back rather than unrestricted mutation.

Setup and configuration

Installation is provided through a Windows PowerShell setup package. The installer can detect Revit 2022–2027 installations, install the corresponding add-ins, place the gateway under %LOCALAPPDATA%\Bimwright\rvt-mcp\server\current\rvt-mcp.exe, and register the server for selected MCP clients. A preview mode lets you inspect changes before applying them, and existing client configuration is backed up.

Claude Desktop can be configured directly or through its optional MCPB extension, but those routes should not be combined. The MCPB route requires the matching server and setup release and does not install the gateway or Revit add-ins by itself. Claude Code, Codex, and Cursor are also named installation targets. After installation, restart the client and use the Revit ribbon to start MCP.

Tool availability is controlled by rvtmcp.config.json. A fresh installation seeds the all toolset; a bare executable exposes a smaller base surface, and custom toolset selections are retained during upgrades. The optional ToolBaker workflow can add personal tools built on the shared runtime.

Tools and capabilities

• Inspect views, selections, filters, statistics, parameters, relationships, worksets, groups, and assemblies.
• Create grids, levels, rooms, and supported line-, point-, or surface-based elements.
• Create views, arrange sheet layouts, capture images, and adjust crop or scale.
• Query or create schedules, including fields, formulas, and schedule data.
• Load and audit families, manage types and instances, and export project-side .rfa files.
• Set parameters, change element types, assign worksets, operate on elements, and apply colors.
• Run audits, pre-issue checks, batch operations, and guided stair creation.

Limitations and notes

Revit must be running with a model available for the in-Revit tools. Read-only mode stops workflows before writing; mixed toolsets also filter out tools that can write files. Drawing-layout and change workflows require their relevant query, view, sheet, metadata, or other toolsets, and stair creation uses send_code only after confirmation.

The pre-issue workflow reports sampled warnings or incomplete checks as NOT VERIFIED rather than treating them as a sheet-level pass. Family Editor authoring is outside the stated scope. Tool counts can vary with the configured toolsets and development state, and personal baked tools are separate from the built-in catalog.