About AEC Model Bridge
AEC Model Bridge is a Python MCP server for reviewing BIM model quality and fixing Revit parameters from Claude, Codex and other MCP clients. Read-only tools inspect the model, and changes require an approved plan by default.
Key features
- 01Reviews BIM model quality
- 02Fixes Revit parameters
- 03Read-only tools for model inspection
- 04Model changes require an approved plan
- 05Includes IFC, Rhino, Grasshopper and Speckle providers
Use cases
- 01Checking parameter quality in Revit models
- 02Applying approved parameter fixes to a Revit model
- 03Developing and testing tools in mock mode
MCP support
This project is an MCP server that exposes over 200 tools for reading and editing BIM models to MCP clients.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEAEC Model Bridge
Python MCP server for reviewing BIM model quality and fixing Revit parameters with Claude, Codex and other MCP clients. Read-only tools inspect the model; model changes require an approved plan by default.
Get started | Example workflows | Tool reference
Live Revit automation requires Windows, Revit 2024–2027 and the native Revit add-in. The server also includes IFC inspection, Rhino and Grasshopper, and Speckle providers. Navisworks integration is in progress. See the installation guide.
Run the server
Requires Python 3.11 or newer. To explore the tools in mock mode from a repository checkout:
python -m pip install -e packages/mcp-server-revit
$env:MCP_REVIT_MODE = "mock"
$env:MCP_REVIT_WORKSPACE_DIR = (Get-Location).Path
$env:MCP_REVIT_ALLOWED_DIRECTORIES = $env:MCP_REVIT_WORKSPACE_DIR
python -m revit_mcp_server.mcp_server
MCP clients start the server over stdio. The console command is
aec-model-bridge; revit-mcp-server remains available as a compatibility
alias. For development without Revit, set MCP_REVIT_MODE=mock to return canned
responses. The release .mcpb bundle uses the MCPB uv runtime and prompts for
a permitted workspace directory.
Configuration
| Environment variable | Purpose |
|---|---|
MCP_REVIT_MODE | bridge for a live application or mock for development |
MCP_REVIT_WORKSPACE_DIR | Workspace root for server file operations |
MCP_REVIT_ALLOWED_DIRECTORIES | Semicolon-separated permitted directories |
MCP_REVIT_HOST_VERSION | Optional Revit year selector, such as 2026 |
MCP_REVIT_BRIDGE_URL | Optional explicit bridge endpoint |
MCP_REVIT_AUDIT_LOG | Audit log location |
MCP_REVIT_LOG_LEVEL | Logging verbosity |
See the configuration reference and release notes.
License
GPL-3.0-or-later with the Revit Linking Exception, or a commercial license.
Maintained by A. Sam Mohammad.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.