Skip to content

Open-source Revit MCP server: let Claude and other AI assistants read and edit BIM models, with human approval on every change.

docs: rewrite README for readers and search, redraw diagrams, prepare 1.3.0

sammohammad578ee85ad031fc9
diff --git a/CHANGELOG.md b/CHANGELOG.md
index a88cce0..547e2e9 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -2,6 +2,11 @@
## Unreleased
+## 1.3.0 - 2026-10-09
+
+- Versioning: the root `VERSION` file is now the single source of truth (SemVer). `scripts/version.py` checks and sets the version across every manifest, CI fails on drift, and pushing a `vX.Y.Z` tag builds the GitHub release with notes taken from this changelog. See `docs/versioning.md`.
+- Docs: README rewritten for readers and search (plain-language intro, install and connect guides, FAQ, release pointers). Architecture, approval and ADR 0008 diagrams redrawn with a colour scheme that stays legible in light and dark mode.
+- Fix CI: the IFC provider could not find elements whose `GlobalId` is malformed (for example 24 characters instead of 22) once `ifcopenshell` 0.9 started resolving GUIDs through a validated index, which failed `test_ifc_provider_tools` on Python 3.11. Lookup now falls back to scanning `IfcRoot` and no longer crashes on an unknown Express ID.
- Ribbon: Workflows and Tools now use one large button plus stacked 16 px buttons, every button gets the brand tooltip image and F1 help, and icons redraw live when Revit's theme changes.
- Dialogs: semantic vector status glyphs replace emoji, link/panel errors use the branded dialog instead of native MessageBox/TaskDialog, and the dialog window carries the app icon.
- Panel: empty states and assistant messages carry icons, nav exposes `aria-current`.
@@ -11,6 +16,7 @@
- Replace the Span brand mark with the Pier mark: an isometric model cube with a bridge arch through each face, on a dark app tile. Applied to `assets/logo.svg` (new `assets/logo-mark.svg`), the panel rail, the dialog header, the About/status brand card, the ribbon brand icon and the Power BI tool icon.
- Redraw all ribbon icons in the Autodesk-style flat grammar: 32 px grid, charcoal outline, light teal fill, one teal accent and a state badge (green run/pass, red stop, amber waiting). Adds an About icon.
+
## 1.2.1 - 2026-09-23
- Add the Plugin Module Registry with discovery, I/O verification, and validate/on_result hooks.
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 50e7341..fd66245 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -15,7 +15,6 @@ corrections are welcome without a code contribution.
## Focus Areas
-
Contributions are most useful when they improve one of the following:
- Revit command coverage
- MCP tool reliability and error handling
@@ -30,10 +29,30 @@ Contributions are most useful when they improve one of the following:
- If a change affects UI or commands, include reproduction steps and expected behavior.
- Update examples or docs when behavior changes.
+## Building and testing
+
+Build the add-in for one Revit version and run the Python tests:
+
+```powershell
+.\scripts\build-addin.ps1 -RevitVersion 2026 -Configuration Release
+python -m pytest packages/mcp-server-revit/tests
+```
+
+Supported Revit versions are 2024 (net48), 2025 and 2026 (net8.0-windows), and
+2027 (net10.0-windows). See
+[docs/target-frameworks-and-dependencies.md](docs/target-frameworks-and-dependencies.md).
+
+## Releases and versions
+
+The project uses Semantic Versioning, and the root `VERSION` file is the
+single source of truth. Tags use the form `vX.Y.Z`. Do not bump version numbers
+by hand in other files. [docs/versioning.md](docs/versioning.md) describes the
+release process, and [CHANGELOG.md](CHANGELOG.md) lists what changed.
+
## Repository Hygiene & Build Artifacts
-- **Build Artifacts (`dist/`, `build/`)**: Compiled distribution files, zip packages, and binary builds must not be committed to the git repository. All releases are attached directly to GitHub Releases.
-- **Local virtual environments**: Always run tests and scripts within local `.venv` environments, which are ignored by git.
+- **Build artifacts (`dist/`, `build/`)**: Do not commit compiled files, zip packages, or binary builds. Releases are attached to GitHub Releases.
+- **Virtual environments**: Run tests and scripts inside a local `.venv`. Git ignores it.
## Pull Request Checklist
diff --git a/README.md b/README.md
index 7dfd78c..8c9a6b9 100644
--- a/README.md
+++ b/README.md
@@ -1,200 +1,234 @@
<div align="center">
-<img src="assets/logo.svg" alt="AEC Model Bridge" height="120">
-
-# AEC Model Bridge
-
-AEC Model Bridge is the open, secure runtime that puts Revit, Rhino, Navisworks, and Power BI behind one MCP call center — so an AI agent orchestrates them directly, instead of you manually dumping data between disconnected apps.
+<img src="assets/logo.svg" alt="AEC Model Bridge logo: an isometric model cube with a bridge arch" height="120">
+# AEC Model Bridge: Revit MCP server
+**An open-source Revit MCP server and AI assistant for Revit. It lets Claude, Codex and other Model Context Protocol clients read and edit BIM models, with you approving every change.**
[![MCP Registry](https://img.shields.io/badge/MCP_Registry-active-0F766E?style=flat-square)](https://registry.modelcontextprotocol.io/?q=io.github.Sam-AEC%2Faec-model-bridge)
[![License](https://img.shields.io/badge/license-GPLv3%2B%20%2F%20Commercial-2563EB?style=flat-square)](LICENSING.md)
[![Python](https://img.shields.io/badge/Python-3.11+-3776AB?style=flat-square&logo=python&logoColor=white)](https://www.python.org/)
[![Revit](https://img.shields.io/badge/Revit-2024--2027-0696D7?style=flat-square)](https://www.autodesk.com/products/revit/)
-<br>
-<strong>Available now</strong><br>
-
-![Revit available](https://img.shields.io/badge/Revit-available-16A34A?style=flat-square)
-![Rhino and Grasshopper available](https://img.shields.io/badge/Rhino_%2F_Grasshopper-available-16A34A?style=flat-square)
-![IfcOpenShell available](https://img.shields.io/badge/IfcOpenShell-available-16A34A?style=flat-square)
-![Speckle available](https://img.shields.io/badge/Speckle-available-16A34A?style=flat-square)
-
-<strong>In progress</strong><br>
-
-![Navisworks Manage in progress](https://img.shields.io/badge/Navisworks_Manage-in_progress-F59E0B?style=flat-square)
-![Power BI in progress](https://img.shields.io/badge/Power_BI-in_progress-F59E0B?style=flat-square)
-
-<strong>Coming soon</strong><br>
-
-![Microsoft Excel coming soon](https://img.shields.io/badge/Microsoft_Excel-coming_soon-2563EB?style=flat-square)
-![Parquet and DuckDB coming soon](https://img.shields.io/badge/Parquet_%2F_DuckDB-coming_soon-2563EB?style=flat-square)
-
-[Install](#installation) | [Tools](docs/tools-generated.md) | [Documentation](#documentation) | [Latest release](https://github.com/Sam-AEC/aec-model-bridge/releases/latest)
+[Install](#install-the-revit-add-in) | [Connect a client](#connect-claude-desktop-to-revit) | [Tools](docs/tools-generated.md) | [Documentation](#documentation) | [Latest release](https://github.com/Sam-AEC/aec-model-bridge/releases/latest)
</div>
-A single MCP client — Claude Desktop, VS Code, GitHub Copilot, or a custom
-agent — talks to one Python hub, and the hub routes each call to whichever
-app the task actually needs: draw geometry in Rhino, query parameters in
-Revit, resolve clashes in Navisworks, publish a dashboard to Power BI. The
-agent plans the workflow once; the bridge is what lets it reach every app
-without you being the one copying data between them.
-
-The Python hub handles MCP communication and routes each request to the relevant
-desktop, 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
+AEC Model Bridge is a Python MCP server plus a native Revit add-in. An AI
+assistant such as Claude or Codex connects to the server, and the server runs
+BIM automation tasks in the Revit model you have open. The same server also
+reads IFC files, and it has providers for Rhino and Grasshopper, Speckle and
+Navisworks.
+
+It does not edit your model on its own. Any tool that changes the model goes
+through a plan that you review and approve first. See
+[How approval works](#how-approval-works).
+
+## What can the AI do in Revit?
+
+The server exposes more than 200 tools across all providers. The full list is
+in the [tool reference](docs/tools-generated.md). In Revit, the tools cover:
+
+- **Reading the model:** list elements, categories, levels, views, sheets and
+ families. Read element and type parameters, geometry, worksets, links,
+ phases and warnings.
+- **Editing parameters:** set one value, set values in batches, or set values
+ for every element matching a filter. Create shared and project parameters.
+- **Creating elements:** walls, floors, roofs, levels, grids, columns, beams,
+ doors, windows, rooms, family instances, and some MEP elements such as ducts,
+ pipes and conduit.
+- **Documentation:** create views and sections, apply view templates, create
+ and renumber sheets, place viewports, tag elements, add text notes and
+ dimensions, and build schedules.
+- **Exports:** IFC, DWG, images and Navisworks.
+- **Checks and reports:** model snapshots and change diffs, a QA/QC checker,
+ and report generation.
+
+For anything the tool catalog does not cover, `invoke_method`, `reflect_get`
+and `reflect_set` work with public Revit API members, and `execute_python`
+runs IronPython inside Revit. These advanced tools have the same permissions as
+the Revit process. Use them only with MCP clients and prompts you trust.
+
+## How it works
+
+The MCP client talks to one Python hub. The hub sends each call to the
+provider that owns the tool. Providers for desktop apps talk to a small add-in
+inside that app over localhost.
-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.
+```mermaid
+---
+config:
+ look: neo
+ theme: base
+ themeVariables:
+ primaryColor: "#334155"
+ primaryTextColor: "#FFFFFF"
+ primaryBorderColor: "#1E293B"
+ secondaryColor: "#334155"
+ tertiaryColor: "#334155"
+ lineColor: "#6E7781"
+ textColor: "#6E7781"
+ titleColor: "#6E7781"
+ nodeTextColor: "#FFFFFF"
+ clusterBkg: "rgba(110,119,129,0.10)"
+ clusterBorder: "#6E7781"
+ edgeLabelBackground: "#334155"
+ actorBkg: "#334155"
+ actorTextColor: "#FFFFFF"
+ actorBorder: "#1E293B"
+ actorLineColor: "#6E7781"
+ signalColor: "#6E7781"
+ signalTextColor: "#6E7781"
+ labelBoxBkgColor: "#334155"
+ labelBoxBorderColor: "#6E7781"
+ labelTextColor: "#FFFFFF"
+ loopTextColor: "#6E7781"
+ sequenceNumberColor: "#FFFFFF"
+ noteBkgColor: "#F59E0B"
+ noteTextColor: "#1F1300"
+ noteBorderColor: "#92400E"
+ transitionColor: "#6E7781"
+ transitionLabelColor: "#FFFFFF"
+ stateLabelColor: "#FFFFFF"
+ stateBkg: "#334155"
+ labelBackgroundColor: "#334155"
+ compositeBackground: "#334155"
+ specialStateColor: "#6E7781"
+---
+flowchart LR
+ subgraph clients["AI clients"]
+ client(["MCP client<br/>Claude, Codex, VS Code"])
+ end
+
+ subgraph hubzone["Python hub"]
+ hub["MCP hub<br/>routes every tool call"]
+ revitP["Revit provider"]
+ rhinoP["Rhino provider"]
+ navP["Navisworks provider"]
+ ifcP["IFC provider"]
+ speckleP["Speckle provider"]
+ end
+
+ subgraph apps["Desktop apps, add-ins on localhost"]
+ revitA["Revit add-in"]
+ rhinoA["Rhino add-in"]
+ navA["Navisworks<br/>add-in<br/>in progress"]
+ end
+
+ ifcLib[("IFC files<br/>read with IfcOpenShell")]
+ cloud(["Speckle server"])
+
+ client -->|"sends tool calls"| hub
+ hub -->|"routes Revit tools"| revitP
+ hub -->|"routes Rhino tools"| rhinoP
+ hub -.->|"routes Navisworks tools"| navP
+ hub -->|"routes IFC tools"| ifcP
+ hub -->|"routes Speckle tools"| speckleP
+ revitP -->|"HTTP"| revitA
+ rhinoP -->|"HTTP"| rhinoA
+ navP -.->|"local bridge"| navA
+ ifcP -->|"parses"| ifcLib
+ speckleP -->|"syncs"| cloud
+
+ classDef live fill:#0F766E,stroke:#0B4F4A,stroke-width:1.5px,color:#FFFFFF
+ classDef wip fill:#F59E0B,stroke:#92400E,stroke-width:1.5px,stroke-dasharray:4 3,color:#1F1300
+ classDef data fill:#4F46E5,stroke:#3730A3,stroke-width:1.5px,color:#FFFFFF
+ class hub,revitP,rhinoP,ifcP,speckleP,revitA,rhinoA live
+ class navP,navA wip
+ class ifcLib,cloud data
+```
-## Highlights
+Teal boxes work today. The amber dashed boxes are in progress. Indigo
+shapes are data and external services.
-- 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 approval works
-## How It Works
+The hub stops any tool call that changes the model unless it carries an
+approved plan. The default mode is `required`. The AI proposes a plan, you
+review it in the Revit side panel, and the add-in runs it on Revit's main
+thread in a named transaction.
```mermaid
-flowchart TD
-
-subgraph group_clients["Clients and UI"]
- node_panel_ui["Bridge Panel<br/>[app.js]"]
-end
-
-subgraph group_hub["Hub and Governance"]
- node_mcp_hub["MCP Hub<br/>[mcp_server.py]"]
- node_provider_registry["Provider Registry<br/>[registry.py]"]
- node_job_manager["Job Manager<br/>[jobs.py]"]
- node_security_controls["Security Controls<br/>[workspace.py]"]
- node_audit_log["Audit Log<br/>[audit.py]"]
-end
-
-subgraph group_revit["Revit Runtime"]
- node_revit_bridge_client["Bridge Client<br/>[client.py]"]
- node_revit_addin["Revit Add-in<br/>[BridgeServer.cs]"]
- node_external_executor["External Executor"]
- node_revit_commands["Revit Commands"]
- node_revit_model[("Revit Model")]
-end
-
-subgraph group_providers["Integration Providers"]
- node_revit_provider["Revit Provider<br/>[revit.py]"]
- node_rhino_provider["Rhino Provider<br/>[rhino.py]"]
- node_rhino_addin["Rhino Add-in<br/>[BridgeCommands.cs]"]
- node_ifc_provider["IFC Provider<br/>[ifc.py]"]
- node_speckle_provider["Speckle Provider<br/>[cloud.py]"]
- node_navisworks_provider["Navisworks Provider<br/>[navisworks.py]"]
- node_navisworks_addin["Navisworks Add-in<br/>[BridgeServer.cs]"]
- node_powerbi_provider["Power BI Provider<br/>[powerbi.py]"]
- node_powerbi_tool["Power BI Tool<br/>[Program.cs]"]
-end
-
-subgraph group_intelligence["AEC Intelligence"]
- node_semantic_provider["Semantic Provider"]
- node_semantic_engine["Semantic Engine<br/>[engine.py]"]
- node_revit_modules["Revit Tool Modules"]
- node_approval_provider["Approval Provider"]
-end
-
-node_mcp_client(("MCP Client"))
-
-node_mcp_client -->|"sends requests"| node_mcp_hub
-node_panel_ui -->|"shows results"| node_mcp_hub
-node_mcp_hub -->|"validates access"| node_security_controls
-node_mcp_hub -->|"records calls"| node_audit_log
-node_mcp_hub -->|"schedules jobs"| node_job_manager
-node_mcp_hub -->|"dispatches tools"| node_provider_registry
-node_provider_registry -->|"routes Revit"| node_revit_provider
-node_provider_registry -->|"routes Rhino"| node_rhino_provider
-node_provider_registry -->|"routes IFC"| node_ifc_provider
-node_provider_registry -->|"routes Speckle"| node_speckle_provider
-node_provider_registry -->|"routes semantics"| node_semantic_provider
-node_provider_registry -->|"routes approvals"| node_approval_provider
-node_provider_registry -.->|"routes clashes"| node_navisworks_provider
-node_provider_registry -.->|"routes dashboards"| node_powerbi_provider
-node_revit_provider -->|"calls tools"| node_revit_bridge_client
-node_revit_bridge_client -->|"uses HTTP"| node_revit_addin
-node_revit_addin -->|"queues commands"| node_external_executor
-node_external_executor -->|"executes tools"| node_revit_commands
-node_revit_commands -->|"reads and writes"| node_revit_model
-node_revit_addin -->|"opens panel"| node_panel_ui
-node_rhino_provider -->|"uses HTTP"| node_rhino_addin
-node_ifc_provider -->|"extracts IFC"| node_semantic_engine
-node_speckle_provider -->|"pushes models"| node_semantic_engine
-node_navisworks_provider -.->|"uses bridge"| node_navisworks_addin
-node_powerbi_provider -.->|"executes queries"| node_powerbi_tool
-node_semantic_provider -->|"queries graph"| node_semantic_engine
-node_approval_provider -->|"updates queue"| node_panel_ui
-
-click node_panel_ui "https://github.com/Sam-AEC/aec-model-bridge/blob/main/panel/app.js"
-click node_mcp_hub "https://github.com/Sam-AEC/aec-model-bridge/blob/main/packages/mcp-server-revit/src/revit_mcp_server/mcp_server.py"
-click node_provider_registry "https://github.com/Sam-AEC/aec-model-bridge/blob/main/packages/mcp-server-revit/src/revit_mcp_server/providers/registry.py"
-click node_job_manager "https://github.com/Sam-AEC/aec-model-bridge/blob/main/packages/mcp-server-revit/src/revit_mcp_server/jobs.py"
-click node_security_controls "https://github.com/Sam-AEC/aec-model-bridge/blob/main/packages/mcp-server-revit/src/revit_mcp_server/security/workspace.py"
-click node_audit_log "https://github.com/Sam-AEC/aec-model-bridge/blob/main/packages/mcp-server-revit/src/revit_mcp_server/security/audit.py"
-click node_revit_provider "https://github.com/Sam-AEC/aec-model-bridge/blob/main/packages/mcp-server-revit/src/revit_mcp_server/providers/revit.py"
-click node_revit_bridge_client "https://github.com/Sam-AEC/aec-model-bridge/blob/main/packages/mcp-server-revit/src/revit_mcp_server/bridge/client.py"
-click node_revit_addin "https://github.com/Sam-AEC/aec-model-bridge/blob/main/packages/revit-bridge-addin/src/Bridge/BridgeServer.cs"
-click node_external_executor "https://github.com/Sam-AEC/aec-model-bridge/blob/main/packages/revit-bridge-addin/src/Bridge/ExternalEventHandler.cs"
-click node_revit_commands "https://github.com/Sam-AEC/aec-model-bridge/blob/main/packages/revit-bridge-addin/src/Bridge/BridgeCommandFactory.cs"
-click node_rhino_provider "https://github.com/Sam-AEC/aec-model-bridge/blob/main/packages/mcp-server-revit/src/revit_mcp_server/providers/rhino.py"
-click node_rhino_addin "https://github.com/Sam-AEC/aec-model-bridge/blob/main/packages/rhino-bridge-addin/src/BridgeCommands.cs"
-click node_ifc_provider "https://github.com/Sam-AEC/aec-model-bridge/blob/main/packages/mcp-server-revit/src/revit_mcp_server/providers/ifc.py"
-click node_speckle_provider "https://github.com/Sam-AEC/aec-model-bridge/blob/main/packages/mcp-server-revit/src/revit_mcp_server/providers/cloud.py"
-click node_navisworks_provider "https://github.com/Sam-AEC/aec-model-bridge/blob/main/packages/mcp-server-revit/src/revit_mcp_server/providers/navisworks.py"
-click node_navisworks_addin "https://github.com/Sam-AEC/aec-model-bridge/blob/main/packages/navisworks-bridge-addin/src/BridgeServer.cs"
-click node_powerbi_provider "https://github.com/Sam-AEC/aec-model-bridge/blob/main/packages/mcp-server-revit/src/revit_mcp_server/providers/powerbi.py"
-click node_powerbi_tool "https://github.com/Sam-AEC/aec-model-bridge/blob/main/packages/powerbi-bridge-tool/src/Program.cs"
-click node_semantic_provider "https://github.com/Sam-AEC/aec-model-bridge/blob/main/packages/mcp-server-revit/src/revit_mcp_server/providers/semantic_provider.py"
-click node_semantic_engine "https://github.com/Sam-AEC/aec-model-bridge/blob/main/packages/mcp-server-revit/src/revit_mcp_server/semantic/engine.py"
-click node_revit_modules "https://github.com/Sam-AEC/aec-model-bridge/tree/main/packages/mcp-server-revit/src/revit_mcp_server/modules"
-click node_approval_provider "https://github.com/Sam-AEC/aec-model-bridge/blob/main/packages/mcp-server-revit/src/revit_mcp_server/providers/approval_provider.py"
-
-classDef toneNeutral fill:#f8fafc,stroke:#334155,stroke-width:1.5px,color:#0f172a
-classDef toneBlue fill:#dbeafe,stroke:#2563eb,stroke-width:1.5px,color:#172554
-classDef toneAmber fill:#fef3c7,stroke:#d97706,stroke-width:1.5px,color:#78350f
-classDef toneMint fill:#dcfce7,stroke:#16a34a,stroke-width:1.5px,color:#14532d
-classDef toneRose fill:#ffe4e6,stroke:#e11d48,stroke-width:1.5px,color:#881337
-classDef toneIndigo fill:#e0e7ff,stroke:#4f46e5,stroke-width:1.5px,color:#312e81
-classDef toneTeal fill:#ccfbf1,stroke:#0f766e,stroke-width:1.5px,color:#134e4a
-class node_panel_ui,node_mcp_client toneBlue
-class node_mcp_hub,node_provider_registry,node_job_manager,node_security_controls,node_audit_log toneAmber
-class node_revit_bridge_client,node_revit_addin,node_external_executor,node_revit_commands,node_revit_model toneMint
-class node_revit_provider,node_rhino_provider,node_rhino_addin,node_ifc_provider,node_speckle_provider,node_navisworks_provider,node_navisworks_addin,node_powerbi_provider,node_powerbi_tool toneRose
-class node_semantic_provider,node_semantic_engine,node_revit_modules,node_approval_provider toneIndigo
+---
+config:
+ look: neo
+ theme: base
+ themeVariables:
+ primaryColor: "#334155"
+ primaryTextColor: "#FFFFFF"
+ primaryBorderColor: "#1E293B"
+ secondaryColor: "#334155"
+ tertiaryColor: "#334155"
+ lineColor: "#6E7781"
+ textColor: "#6E7781"
+ titleColor: "#6E7781"
+ nodeTextColor: "#FFFFFF"
+ clusterBkg: "rgba(110,119,129,0.10)"
+ clusterBorder: "#6E7781"
+ edgeLabelBackground: "#334155"
+ actorBkg: "#334155"
+ actorTextColor: "#FFFFFF"
+ actorBorder: "#1E293B"
+ actorLineColor: "#6E7781"
+ signalColor: "#6E7781"
+ signalTextColor: "#6E7781"
+ labelBoxBkgColor: "#334155"
+ labelBoxBorderColor: "#6E7781"
+ labelTextColor: "#FFFFFF"
+ loopTextColor: "#6E7781"
+ sequenceNumberColor: "#FFFFFF"
+ noteBkgColor: "#F59E0B"
+ noteTextColor: "#1F1300"
+ noteBorderColor: "#92400E"
+ transitionColor: "#6E7781"
+ transitionLabelColor: "#FFFFFF"
+ stateLabelColor: "#FFFFFF"
+ stateBkg: "#334155"
+ labelBackgroundColor: "#334155"
+ compositeBackground: "#334155"
+ specialStateColor: "#6E7781"
+---
+sequenceDiagram
+ autonumber
+ participant You
+ participant AI as AI assistant
+ participant Hub as MCP hub + ApprovalGate
+ participant Panel as Side panel (WebView2)
+ participant Addin as Revit add-in
+ participant Model as Revit model
+
+ AI->>Hub: plan_actions (proposed changes)
+ Hub->>Panel: show the pending plan
+ Panel->>You: review the plan
+ alt You approve
+ You->>Panel: Approve
+ Panel->>Hub: approved
+ AI->>Hub: execute_plan
+ Hub->>Addin: forward the commands
+ Addin->>Model: run in one named transaction
+ Model-->>Addin: done
+ Addin-->>AI: result (rollback_plan can reverse it)
+ else You reject, or never approve
+ You->>Panel: Reject
+ Panel->>Hub: rejected
+ AI->>Hub: execute_plan
+ Hub--xAI: blocked, the model is untouched
+ end
```
-## Installation
+If a plan is approved and later turns out wrong, `rollback_plan` reverses it.
+Rollback uses Revit Undo in the same session or inverse parameter values.
+Operations that cannot be reversed, such as file output, ask for a second
+confirmation. The lifecycle is in
+[ADR 0008](docs/0008-approval-gate-lifecycle.md).
-### Requirements
+For unattended pipelines you can set `MCP_REVIT_APPROVAL_MODE=auto`. That turns
+the human check off, so use it only in a controlled environment.
-| Revit version | Add-in target | Required build tools |
+## Supported Revit versions
+
+| Revit version | Add-in target | Build tools |
|---|---|---|
| 2024 | .NET Framework 4.8 | .NET 8 SDK and .NET Framework 4.8 developer pack |
| 2025 | .NET 8 for Windows | .NET 8 SDK |
@@ -202,7 +236,25 @@ class node_semantic_provider,node_semantic_engine,node_revit_modules,node_approv
| 2027 | .NET 10 for Windows | .NET 10 SDK |
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 for the version you use. Mock mode runs the server without Revit,
+which is useful for development and tests.
+
+### Other integrations
+
+| Integration | Status |
+|---|---|
+| Revit | Available. Native C# add-in. |
+| IFC (IfcOpenShell) | Available. Reads IFC files without Revit running. |
+| Rhino and Grasshopper | Available. Connects to the Rhino add-in on `localhost:3004`. |
+| Speckle | Available. Needs a Speckle client ID in your environment. |
+| Navisworks Manage | In progress. The provider and its tools are registered. The Navisworks add-in is not finished. |
+| Power BI | In progress. The provider and tool exist but are not registered in the hub. |
+| Excel, Parquet and DuckDB | Planned. |
+
+## Install the Revit add-in
+
+You install two parts: the Python MCP server and the Revit add-in. Live Revit
+automation needs both.
### 1. Install the MCP server
@@ -250,12 +302,19 @@ To prepare binaries for every supported version in one pass:
```
Prebuilt packages are attached to GitHub releases when available. The source
-installation above is the canonical path for all supported Revit versions.
+installation above works for all supported Revit versions. For a double-click
+Windows installer, `scripts/build-installer.ps1` builds one with Inno Setup.
+The full guide, with troubleshooting, is in [docs/install.md](docs/install.md).
-### 3. Configure your MCP client
+## Connect Claude Desktop to Revit
-Use the Python executable from the virtual environment and choose a workspace
-that the server may access:
+Add the server to your MCP client configuration. For Claude Desktop, that is
+the `mcpServers` section of `claude_desktop_config.json`. Codex, Cursor, VS
+Code and other MCP clients use the same `command`, `args` and `env` values in
+their own config format.
+
+Use the Python executable from your virtual environment, and choose a workspace
+folder the server may access:
```json
{
@@ -283,21 +342,19 @@ that the server may access:
}
```
-Omit `MCP_REVIT_HOST_VERSION` to target the newest open Revit instance, or set
-it to a year such as `2024` or `2026` to keep a client entry locked to that
-Revit version. `MCP_REVIT_BRIDGE_URL` remains available as an explicit endpoint
-override for advanced setups.
-
-VS Code users can start from [`.vscode/mcp.json`](.vscode/mcp.json).
-Hermes Desktop users can start from [`Hermes.json`](Hermes.json); replace the
-placeholder Python path with the path to your local virtual environment.
+Leave out `MCP_REVIT_HOST_VERSION` to target the newest open Revit instance.
+Set it to a year such as `2024` or `2026` to lock a client entry to that Revit
+version. `MCP_REVIT_BRIDGE_URL` overrides the endpoint for advanced setups.
-Clients that support MCP Bundles can install the `.mcpb` file from the
+VS Code users can start from [`.vscode/mcp.json`](.vscode/mcp.json). Hermes
+Desktop users can start from [`Hermes.json`](Hermes.json) after replacing the
+placeholder Python path. Clients that support MCP Bundles can install the
+`.mcpb` file from the
[latest release](https://github.com/Sam-AEC/aec-model-bridge/releases/latest).
-The Revit add-in is still required because the MCP server communicates with the
-running desktop application.
+The Revit add-in is still required, because the server talks to the running
+desktop application.
-### 4. Verify the connection
+### Check the connection
Restart Revit after installing the add-in, open a model, and run:
@@ -307,19 +364,70 @@ $switch = Get-Content $registry.FullName -Raw | ConvertFrom-Json
Invoke-RestMethod "$($switch.endpoint)/health"
```
-The response should report `healthy` and the active Revit version.
+The response should report `healthy` and the running Revit version. In Revit,
+look for the `AEC Bridge` ribbon tab. Its Workflows panel has Open Panel,
+Health Check, Pending Actions and Reports. Its Tools panel has Config, Help
+and About.
+
+## Security
+
+- The Revit bridge listens on localhost only.
+- The server reads and writes only inside the folders in
+ `MCP_REVIT_ALLOWED_DIRECTORIES`.
+- Mutating tools need an approved plan unless you turn approval off.
+- Tool calls are written to an audit log, and secrets are redacted.
+
+Details are in [docs/security.md](docs/security.md). To report a
+vulnerability, follow [SECURITY.md](SECURITY.md).
+
+## FAQ
+
+### What is an MCP server for Revit?
-## Revit API Access
+The Model Context Protocol (MCP) is an open standard that lets AI assistants
+call tools in other software. An MCP server for Revit publishes Revit
+operations as tools. The assistant picks the tools, and the add-in runs them
+inside Revit.
-The typed MCP tools cover the common workflow surface and are the recommended
-default for agents.
+### Which AI assistants work with it?
-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.
+Any MCP client that can start a local stdio server. We document Claude
+Desktop, VS Code with GitHub Copilot, and clients that read a standard
+`mcpServers` configuration. The panel chat can also use an Anthropic API key
+or the `claude` or `codex` command-line tools if they are installed. See
+[ADR 0012](docs/0012-native-agent-chat-backend.md).
-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.
+### Can the AI change my model without asking?
+
+Not in the default mode. Tools that change the model are blocked until a plan
+is approved in the Revit panel. Read-only tools run without approval. If you
+set `MCP_REVIT_APPROVAL_MODE=auto`, approval is skipped.
+
+### Does it send my model to the cloud?
+
+The server and the add-in run on your machine, and the bridge listens on
+localhost. What the AI assistant sees depends on the client you use: the tool
+results go to that client's model provider. Cloud-facing providers, such as
+Speckle, only run when you configure them and call their tools.
+
+### Does it work with IFC files without Revit?
+
+Yes. The IFC provider reads files with IfcOpenShell. It can return file
+metadata, the spatial structure, element properties and bounding boxes, run
+queries by class, GUID, name or property, and validate the schema. It does
+not edit IFC files.
+
+### Can I use it without Revit installed?
+
+You can run the server in mock mode for development and tests. Live model work
+needs Revit 2024 to 2027 and the add-in.
+
+## Releases and versions
+
+AEC Model Bridge follows Semantic Versioning. Releases are tagged `vX.Y.Z` on
+GitHub, and a root `VERSION` file holds the version number. See
+[docs/versioning.md](docs/versioning.md) for the release process and
+[CHANGELOG.md](CHANGELOG.md) for what changed in each version.
## Development
@@ -327,15 +435,15 @@ the bridge on localhost and only use trusted MCP clients and prompts.
# 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 one Revit version, for example 2026
+.\scripts\build-addin.ps1 -RevitVersion 2026 -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.
+CI builds the Python server and the add-in targets for Revit 2024 through 2027.
+See [CONTRIBUTING.md](CONTRIBUTING.md) before opening a pull request.
## Documentation
@@ -345,10 +453,11 @@ CI builds the Python server and add-in targets for Revit 2024 through 2027.
- [Configuration reference](docs/configuration-reference.md)
- [Security](docs/security.md)
- [MCP clients and registry](docs/marketplaces.md)
+- [Versioning and releases](docs/versioning.md)
- [Contributing](CONTRIBUTING.md)
- [Contributors](CONTRIBUTORS.md)
-## Project
+## Project and license
Maintained by [A. Sam Mohammad](https://github.com/Sam-AEC).
[LinkedIn](https://www.linkedin.com/in/a-sam-mohammad-92790416b) |
diff --git a/docs/0008-approval-gate-lifecycle.md b/docs/0008-approval-gate-lifecycle.md
index 7b19f40..bc13b96 100644
--- a/docs/0008-approval-gate-lifecycle.md
+++ b/docs/0008-approval-gate-lifecycle.md
@@ -12,13 +12,63 @@ AI agents modifying production BIM models (e.g., Revit, Navisworks) pose signifi
An **ActionPlan** is the unit of human approval and execution control. It transitions through the following states:
```mermaid
-graph TD
- Draft[Draft] -->|plan_actions| Validated[Validated]
- Validated -->|submit| Pending[Pending Review]
- Pending -->|approve| Approved[Approved]
- Pending -->|reject| Rejected[Rejected]
- Approved -->|execute| Executed[Executed]
- Executed -->|rollback| RolledBack[Rolled Back]
+---
+config:
+ look: neo
+ theme: base
+ themeVariables:
+ primaryColor: "#334155"
+ primaryTextColor: "#FFFFFF"
+ primaryBorderColor: "#1E293B"
+ secondaryColor: "#334155"
+ tertiaryColor: "#334155"
+ lineColor: "#6E7781"
+ textColor: "#6E7781"
+ titleColor: "#6E7781"
+ nodeTextColor: "#FFFFFF"
+ clusterBkg: "rgba(110,119,129,0.10)"
+ clusterBorder: "#6E7781"
+ edgeLabelBackground: "#334155"
+ actorBkg: "#334155"
+ actorTextColor: "#FFFFFF"
+ actorBorder: "#1E293B"
+ actorLineColor: "#6E7781"
+ signalColor: "#6E7781"
+ signalTextColor: "#6E7781"
+ labelBoxBkgColor: "#334155"
+ labelBoxBorderColor: "#6E7781"
+ labelTextColor: "#FFFFFF"
+ loopTextColor: "#6E7781"
+ sequenceNumberColor: "#FFFFFF"
+ noteBkgColor: "#F59E0B"
+ noteTextColor: "#1F1300"
+ noteBorderColor: "#92400E"
+ transitionColor: "#6E7781"
+ transitionLabelColor: "#FFFFFF"
+ stateLabelColor: "#FFFFFF"
+ stateBkg: "#334155"
+ labelBackgroundColor: "#334155"
+ compositeBackground: "#334155"
+ specialStateColor: "#6E7781"
+---
+stateDiagram-v2
+ state "Pending review" as Pending
+ state "Rolled back" as RolledBack
+
+ [*] --> Draft
+ Draft --> Validated: plan_actions
+ Validated --> Pending: submit
+ Pending --> Approved: approve
+ Pending --> Rejected: reject
+ Approved --> Executed: execute
+ Executed --> RolledBack: rollback_plan
+ Rejected --> [*]
+ RolledBack --> [*]
+
+ classDef ok fill:#0F766E,stroke:#0B4F4A,color:#FFFFFF
+ classDef blocked fill:#B91C1C,stroke:#7F1D1D,color:#FFFFFF
+ class Approved,Executed ok
+ class Rejected blocked
```
- **Draft**: A plan containing proposed actions (tool calls and arguments) under construction.
@@ -64,7 +114,7 @@ The ActionPlan represents a batch of modifications:
- **Auto-Approval**: For headless CI/CD pipelines, `approval_mode=auto` can be set via environment variable (`MCP_REVIT_APPROVAL_MODE=auto`).
### 4. Rollback Strategies
-- **Revit Undo (`undo`)**: If executed inside the same Revit session, the add-in wraps the execution in a single named transaction (`"AMB: Plan <plan_id>"`). The add-in can tigger Revit's native Undo command.
+- **Revit Undo (`undo`)**: If executed inside the same Revit session, the add-in wraps the execution in a single named transaction (`"AMB: Plan <plan_id>"`). The add-in can trigger Revit's native Undo command.
- **Inverse Counter-Plan (`inverse`)**: For persistent history rollbacks, the hub generates an inverse counter-plan by capturing the before-state (e.g., parameter values) and executing a compensating batch of updates.
- **Irreversible (`none`)**: High-risk operations (e.g., deleting models, file outputs) cannot be rolled back and require a double-confirmation from the human operator.
diff --git a/docs/0011-panel-architecture.md b/docs/0011-panel-architecture.md
index 39c9848..eed8e29 100644
--- a/docs/0011-panel-architecture.md
+++ b/docs/0011-panel-architecture.md
@@ -52,8 +52,8 @@ To maintain security boundaries while enabling rapid data transfer:
### 4. UI Design System & Frameworks
- **Design tokens**: `docs/design/tokens.md` (approved) is the single source of truth for the brand mark, color, typography, surfaces, motion and the ribbon icon grammar. There is no codegen or token-sync tool. Values are hand-copied into `panel/styles.css` (as `--amb-*` CSS custom properties), `IconGenerator.cs` and `assets/logo.svg`, and each copy site carries a `keep in sync with docs/design/tokens.md` comment.
-- **Brand mark**: "The Span", two bearings joined by a deck under a brand-colored apex. It replaces the three disagreeing cube/gradient marks. It appears as an inline SVG in the panel rail, as the ribbon brand icon, and in `assets/logo.svg`.
-- **Theming**: Light and dark palettes, each with its own verified contrast. The panel follows **Revit's** theme, not only the OS theme. The add-in sends `isDarkTheme` (from `UIThemeManager.CurrentTheme`) in every `host.status` message, and `app.js` sets `data-theme` on `<html>`. `prefers-color-scheme` is only a fallback until the first `host.status` arrives. A mid-session Revit theme toggle re-themes the panel live: the add-in subscribes to Revit's `ThemeChanged` event (Revit 2024+, guarded for older versions) and sends a fresh `host.status`. Ribbon icons are the exception. They are generated once at startup, so they show the theme Revit had at session start and only change after a full Revit restart. This is a known, accepted limitation.
+- **Brand mark**: the "Pier", an isometric model cube with a bridge arch through each side face, on a dark app tile. It replaces the earlier Span mark and the three disagreeing cube/gradient marks. It appears as an inline SVG in the panel rail, in the dialog header and brand card, as the ribbon brand icon, and in `assets/logo.svg` and `assets/logo-mark.svg`. The panel rail is a 64 px icon rail whose icons and labels follow the same grammar as the ribbon.
+- **Theming**: Light and dark palettes, each with its own verified contrast. The panel follows **Revit's** theme, not only the OS theme. The add-in sends `isDarkTheme` (from `UIThemeManager.CurrentTheme`) in every `host.status` message, and `app.js` sets `data-theme` on `<html>`. `prefers-color-scheme` is only a fallback until the first `host.status` arrives. A mid-session Revit theme toggle re-themes the panel live: the add-in subscribes to Revit's `ThemeChanged` event (Revit 2024+, guarded for older versions) and sends a fresh `host.status`. Ribbon icons redraw on the same `ThemeChanged` event, so they follow the theme without a Revit restart.
- **Surfaces**: Only two surfaces get the glass treatment: the topbar (`--amb-glass` fill plus `--amb-glass-filter`) and the rail (`--amb-glass-filter` over its always-dark `--amb-rail` fill). Cards, inputs and list rows stay opaque so body text stays legible. This narrows the original "glassmorphism card layouts" idea on purpose. Elevation uses two shadow tokens. A single `:focus-visible` ring is the universal focus affordance.
- **Semantic color**: One set of semantic tokens (danger, warning, info, success, pending, idle) drives both the panel badges and the ribbon icons. `pending` (plans waiting for approval) is violet on both.
- **Motion**: Two motion tokens (`--amb-motion-fast` for hover/press, `--amb-motion-view` for view switches). All animation and transitions are turned off under `prefers-reduced-motion: reduce`.
diff --git a/docs/build-and-install-scripts.md b/docs/build-and-install-scripts.md
index 822889f..6015933 100644
--- a/docs/build-and-install-scripts.md
+++ b/docs/build-and-install-scripts.md
@@ -27,6 +27,16 @@ Key behavior:
- always builds a wheel as fallback
- writes `default.json` and `README.txt` into the distribution payload
+### `scripts/build-installer.ps1`
+
+Builds the double-click Windows installer.
+
+Key behavior:
+
+- runs `package.ps1` first, so the payload is current
+- locates Inno Setup (`ISCC.exe`) or installs it if missing
+- uses the wizard images and app icon from `assets/`, generated by `scripts/make_brand_assets.py`
+
### `scripts/install.ps1`
Installs from a prepared distribution package.
diff --git a/docs/design/tokens.md b/docs/design/tokens.md
index d4f3699..005b39e 100644
--- a/docs/design/tokens.md
+++ b/docs/design/tokens.md
@@ -9,7 +9,8 @@ Status: **approved**.
> `UI/BrandMark.cs` (dialog header, brand card, ribbon brand icon). Ribbon icons
> in `IconGenerator.cs` use a 32 px grid, 2 px charcoal outline, light teal fill,
> one `amb-brand` accent and a lower-right state badge. Sections 2 and 5 below
-> describe the earlier Span mark and are superseded where they conflict.
+> describe the earlier Span mark (retired in 1.3.0) and are superseded where they
+> conflict. The Pier is the only current brand mark.
### One design across surfaces (current)
@@ -51,7 +52,20 @@ All five are replaced by **one mark** and **one palette** below.
---
-## 2. The mark — "the Span"
+## 2. The mark
+
+**Current: the Pier.** An isometric model cube with a bridge arch cut through
+each side face, on a rounded `#111923` tile (96 px viewBox, 20 px corner
+radius). The top face is `#1CB5CA`, the left face `#FFFFFF`, the right face
+`#AEBCCB`, with a 2.5 px `#111923` stroke between faces. The source of truth
+for the geometry is `assets/logo-mark.svg`; `UI/BrandMark.cs`, `panel/index.html`
+and `scripts/make_brand_assets.py` copy it.
+
+The rest of this section, 2.1 to 2.6, documents the **Span**, the mark that the
+Pier replaced. It is kept as history and as the reference for the retired
+wordmark and rail-mark geometry. Do not use it for new work.
+
+### Span (retired)
### 2.1 Concept
diff --git a/docs/install.md b/docs/install.md
index 550c063..e5f11fb 100644
--- a/docs/install.md
+++ b/docs/install.md
@@ -1,12 +1,13 @@
-# Installation
+# Install AEC Model Bridge
-AEC Model Bridge has two components:
+AEC Model Bridge has two parts:
-1. A Python MCP server used by the AI client.
-2. A native add-in loaded by Revit.
+1. A Python MCP server that your AI client starts.
+2. A native add-in that Revit loads.
-Both are required for live Revit automation. Mock mode only requires the Python
-server.
+You need both for live Revit automation. Mock mode needs only the Python
+server. Supported Revit versions are 2024 to 2027. For release numbering, see
+[versioning](versioning.md).
## Requirements
@@ -43,7 +44,8 @@ Choose the Revit version installed on your machine:
$RevitVersion = Read-Host "Revit year (2024, 2025, 2026, or 2027)"
```
-Build, package, and install the matching add-in:
+Build, package, and install the matching add-in. To only build, run
+`.\scripts\build-addin.ps1 -RevitVersion 2026` (use your Revit year):
```powershell
.\scripts\package.ps1 -RevitVersion $RevitVersion
@@ -178,7 +180,7 @@ python -m pytest packages/mcp-server-revit/tests
### Bridge connection refused
- Confirm Revit is running.
-- Confirm the `AEC Bridge` ribbon tab is present.
+- Confirm the `AEC Bridge` ribbon tab is present. It has Connection, Workflows and Tools panels.
- Check that the manifest year matches the running Revit year.
- Check the bridge log at `%APPDATA%\AECModelBridge\Logs\bridge.jsonl`.
- Confirm no other process is using port `3000`.
diff --git a/docs/revit-addin-lifecycle.md b/docs/revit-addin-lifecycle.md
index 56266ad..ae28200 100644
--- a/docs/revit-addin-lifecycle.md
+++ b/docs/revit-addin-lifecycle.md
@@ -37,16 +37,11 @@ That pattern is what makes live Revit automation safe inside Autodesk's threadin
`CreateModernRibbonInterface()` creates:
- an `AEC Bridge` tab
-- a `Connection` panel
-- a `Tools` panel
+- a `Connection` panel with Connect, Disconnect and Status
+- a `Workflows` panel with one large Open Panel button and stacked Health Check, Pending Actions and Reports buttons
+- a `Tools` panel with stacked Config, Help and About buttons
-It wires button commands for:
-
-- connect
-- disconnect
-- status
-- settings
-- help
+Every button has a tooltip with the brand image, and F1 opens the documentation. The icons use the 32 px flat grammar from `docs/design/tokens.md`, with a state badge where a button reports status. They redraw when Revit's theme changes.
The ribbon is more than cosmetic: it exposes operational status and provides a manual control surface for the bridge lifecycle.
diff --git a/packages/mcp-server-revit/README.md b/packages/mcp-server-revit/README.md
index cbe6dd5..091422c 100644
--- a/packages/mcp-server-revit/README.md
+++ b/packages/mcp-server-revit/README.md
@@ -1,6 +1,6 @@
# AEC Model Bridge (Python Package)
-Independent MCP integration for Autodesk Revit software, used by AI clients over stdio.
+Python MCP server for Autodesk Revit, plus IFC, Rhino, Speckle and Navisworks providers. AI clients such as Claude and Codex start it over stdio. Mutating tools need an approved plan by default.
- Repository: https://github.com/Sam-AEC/aec-model-bridge
- Maintainer: [A. Sam Mohammad](https://github.com/Sam-AEC)
@@ -8,6 +8,8 @@ Independent MCP integration for Autodesk Revit software, used by AI clients over
- MCP entrypoint: `python -m revit_mcp_server.mcp_server`
- Console scripts: `aec-model-bridge` and the compatibility alias `revit-mcp-server`
- Requires Python 3.11+
+- Works with the Revit add-in for Revit 2024 to 2027 (see the repository README for setup)
+- Versioning: Semantic Versioning, see [docs/versioning.md](https://github.com/Sam-AEC/aec-model-bridge/blob/main/docs/versioning.md)
- The `.mcpb` bundle uses the MCPB `uv` runtime and prompts for a permitted workspace directory.
Environment variables (prefix `MCP_REVIT_`) include: