独立Revit MCP

Requirements

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

Installation

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 under C:\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 source installation above is the canonical path for all supported Revit versions.

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.

3. Configure your MCP client

Use the Python executable from the virtual environment and choose a workspace that 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 the latest release. The Revit add-in is still required because the MCP server communicates with the running desktop application.

Revit API Access

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

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

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