AEC Model Bridge

A single MCP client — Claude Desktop, VS Code, GitHub Copilot, or a customagent — talks to one Python hub, and the hub routes each call to whicheverapp the task actually needs: draw geometry in Rhino, query parameters inRevit, resolve clashes in Navisworks, publish a dashboard to Power BI. Theagent plans the workflow once; the bridge is what lets it reach every appwithout you being the one copying data between them.

The Python hub handles MCP communication and routes each request to the relevantdesktop, headless, cloud, or compute provider:

• Revit: Native C# add-in (Revit 2024-2027) executing on the main thread via ExternalEvent.
• Navisworks Manage: Native C# add-in (Navisworks 2024-2027) exposing the API over a local bridge (in progress).
• Rhino/Grasshopper: Connects to the Rhino Bridge Add-in over HTTP localhost:3004.
• Speckle: Native Python provider integrating Specklepy V3 for seamless model pushing to Power BI.
• IfcOpenShell: Headless IFC semantic extraction and parsing.

Platform Status

The status below reflects the AEC Model Bridge system blueprint as of June 2026.In-progress integrations are implemented as routing infrastructure but require further registration or workflow integration.

Available Now

Revit, Rhino/Grasshopper, IfcOpenShell, and Speckle are available integrations. The Revit C# add-in (Revit 2024-2027) executes commands on the main thread. Rhino connects to the Rhino Bridge Add-in over HTTP on port 3004. IfcOpenShell provides headless IFC parsing, and Speckle integrates model pushing via Specklepy V3.

In Progress

Navisworks Manage is currently in progress; while the C# add-in routing infrastructure is in place, the provider is not yet registered in the shipped hub. Power BI is also in progress, with the provider and tool in place but not yet integrated into the active hub runtime.

Coming Soon

This wave adds Excel workbook round trips and a Parquet/DuckDB data plane for cross-platform reporting.

Highlights

• 100+ MCP tools for model authoring, documentation, parameters, views, sheets, exports, and QA.
• Native Revit & Navisworks add-ins with no Dynamo or pyRevit dependencies.
• Multi-platform synchronization: Cross-query Navisworks clash results, Revit parameters, and Rhino models dynamically.
• Speckle and PowerBI automated data handoffs.
• Async job orchestration and centralized PII redaction.
• Reflection and in-process Python for advanced API workflows.
• Localhost-only bridge by default for absolute security.
• Mock mode for development and automated testing without Revit.

How It Works

MCP Client (Claude Desktop, VS Code)
    |
    | MCP over stdio
    v
    Python MCP Server (Central Router)
        ├── [Revit Provider] -----> HTTP localhost:3000 -----> Revit Bridge Add-in
        ├── [Navisworks Provider] > HTTP localhost:3002 -----> Navisworks Bridge Add-in
        ├── [Speckle Provider] ---> HTTPS (OAuth) -----------> Speckle Manager / Power BI
        ├── [Rhino Provider] -----> HTTP localhost:3004 -----> Rhino Bridge Add-in
        └── [IFC Provider] -------> Local Filesystem --------> IfcOpenShell

Installation

Requirements

You also need Windows 10 or 11, Python 3.11 or later, and a licensed Revitinstallation for the version you want to use.

1. Install the MCP server

git clone https://github.com/Sam-AEC/aec-model-bridge.git
cd aec-model-bridge

py -m venv .venv
.\.venv\Scripts\Activate.ps1
python -m pip install -e packages/mcp-server-revit

2. Install the Revit add-in

Set the version to match your Revit installation:

$RevitVersion = Read-Host "Revit year (2024, 2025, 2026, or 2027)"

.\scripts\package.ps1 -RevitVersion $RevitVersion
.\scripts\install.ps1 -RevitVersion $RevitVersion

The installer places version-specific binaries in:

C:\ProgramData\AECModelBridge\bin\<year>

The add-in manifest is installed per user in:

%APPDATA%\Autodesk\Revit\Addins\<year>

Use -AllUsers with install.ps1 to install the manifest underC:\ProgramData\Autodesk\Revit\Addins\<year> instead.

To prepare binaries for every supported version in one pass:

.\scripts\package.ps1 -RevitVersion All

Prebuilt packages are attached to GitHub releases when available. The sourceinstallation above is the canonical path for all supported Revit versions.

3. Configure your MCP client

Use the Python executable from the virtual environment and choose a workspacethat the server may access:

{
  "mcpServers": {
    "aec-model-bridge": {
      "command": "C:\\path\\to\\aec-model-bridge\\.venv\\Scripts\\python.exe",
      "args": ["-m", "revit_mcp_server.mcp_server"],
      "env": {
        "MCP_REVIT_MODE": "bridge",
        "MCP_REVIT_BRIDGE_URL": "http://127.0.0.1:3000",
        "MCP_REVIT_WORKSPACE_DIR": "C:\\RevitProjects",
        "MCP_REVIT_ALLOWED_DIRECTORIES": "C:\\RevitProjects"
      }
    }
  }
}

VS Code users can start from .vscode/mcp.json.

Clients that support MCP Bundles can install the .mcpb file from thelatest release.The Revit add-in is still required because the MCP server communicates with therunning desktop application.

4. Verify the connection

Restart Revit after installing the add-in, open a model, and run:

Invoke-RestMethod http://127.0.0.1:3000/health

The response should report healthy and the active Revit version.

Revit API Access

The typed MCP tools cover the common workflow surface and are the recommendeddefault for agents.

For work outside the tool catalog, invoke_method, reflect_get, andreflect_set can work with public .NET API members. execute_python runsIronPython inside Revit with doc, uidoc, uiapp, and app available.

These advanced tools run with the same permissions as the Revit process. Keepthe bridge on localhost and only use trusted MCP clients and prompts.

Development

# Python tests
python -m pytest packages/mcp-server-revit/tests

# Build one Revit version
$RevitVersion = Read-Host "Revit year (2024, 2025, 2026, or 2027)"
.\scripts\build-addin.ps1 -RevitVersion $RevitVersion -Configuration Release

# Build all supported versions
.\scripts\package.ps1 -RevitVersion All

CI builds the Python server and add-in targets for Revit 2024 through 2027.

Documentation

• Installation guide
• Tool reference
• Architecture
• Configuration reference
• Security
• MCP clients and registry
• Contributing

Project

Maintained by A. Sam Mohammad.LinkedIn |Issues

Version 1.1.0 and later is available under your choice ofGPL-3.0-or-later with the Revit Linking Exception, or a separate commerciallicense. The GPL option permits community use while allowing theadd-in to operate through Autodesk Revit APIs. Commercial terms are availablefor proprietary distribution and negotiated requirements. Version 1.0.2 andearlier remains available under the MIT License.

AEC Model Bridge is an independent project and is not sponsored, endorsed, orprovided by Autodesk. Autodesk and Revit are trademarks of the Autodesk groupof companies. See TRADEMARKS.md.