RevitMCPBridge2026

RevitMCPBridge2026 exposes the entire Revit API through the MCP (Model Context Protocol) using Windows named pipes. It allows AI agents and custom tools to read, create, modify, and validate elements in a Revit model without manual steps or Dynamo. With 705+ endpoints across numerous categories, you can query model data, create and modify elements (walls, doors, rooms, sheets, schedules, etc.), generate construction documents, and perform validation tasks such as code compliance checks. Interaction is done via JSON messages sent to the bridge through a named pipe, serialized and deserialized by the bridge, ensuring operations run on Revit’s main UI thread for reliability. To connect, simply point your client at the designated named pipe (for example, \.\pipe\RevitMCPBridge2026) and send requests in the form {"method": "<name>", "params": { ... }}.

Once connected, you can:

• Read model data: extract element properties, schedules, and geometry.
• Create elements: walls, doors, windows, rooms, and MEP components.
• Modify elements: adjust dimensions, parameters, and types within Revit transactions.
• Generate documents: create sheets, views, and schedules automatically.
• Validate models: run code checks, compliance rules, and QC checks.
• Leverage AI autonomy: chain methods and goals to automate multi-step workflows across the model.

The bridge is designed for AI agents written in any language capable of speaking JSON and writing to a named pipe, enabling seamless integration with larger automation pipelines and custom assistants.

Prerequisites:

• Autodesk Revit 2025 or 2026
• .NET Framework 4.8
• Visual Studio 2022 (for building from source)

Install / Build from source:

1. Clone the repository git clone https://github.com/WeberG619/RevitMCPBridge2026.git cd RevitMCPBridge2026

2. Build the project (Release configuration) msbuild RevitMCPBridge2026.csproj /p:Configuration=Release

3. Deploy the add-in to Revit (example, Windows path fallback)

   • Copy the built RevitMCPBridge2026.dll to the Revit Addins path, e.g. %APPDATA%\Autodesk\Revit\Addins\2026\
   • Copy RevitMCPBridge2026.addin to the same folder
   • Copy appsettings.json (if used) to the same folder

4. Run the bridge (if not configured to auto-start with Revit)

   • Use the dotnet runtime to start the DLL when Revit begins, or package as a standalone executable if provided by the build

5. Verify connection

   • Open a client and attempt to connect to the pipe named pipe\.\pipe\RevitMCPBridge2026 and issue a simple request, e.g., {"method": "healthCheck", "params": {}}

Prerequisite tips:

• Ensure Revit is running before starting the bridge so the add-in can initialize properly.
• If you deploy as a DLL-based add-in, you may need to adjust Addins manifest files to point to the built DLL.
• Ensure the firewall allows named pipe communication for inter-process communication on the host.

Notes and tips:

• Named pipes serialize requests through Revit’s ExternalEvent queue, providing stable performance under heavy workloads. Avoid HTTP-based MCPs for large or long-running sessions with Revit.
• The bridge exposes 705+ endpoints across many categories (Walls, Doors & Windows, Rooms, Views, Sheets, Schedules, Families, Parameters, Structural, MEP, Details, Annotations, Intelligence, etc.). Consult the API reference to discover specific method signatures and parameter schemas.
• The default pipe name is RevitMCPBridge2026; ensure clients use the exact pipe name to connect.
• If you upgrade Revit to a newer version, verify compatibility with the bridge’s target framework and add-in manifest.
• When debugging, enable verbose logs if available to diagnose endpoint validation or transaction errors.
• Security: since this runs locally, ensure access is restricted to trusted processes; avoid exposing the named pipe to untrusted clients.
• For CI or automation, wrap JSON requests with proper error handling to manage structured error responses from the MCP bridge.