Open-source Revit MCP server: let Claude and other AI assistants read and edit BIM models, with human approval on every change.
Python aecai-agentsautodeskautomationbimclaudeifcmcpmcp-servermodel-context-protocolnavisworksrevitrevit-addinrevit-apirhino
Document Revit 2024-2026 support
sammohammad578bd19a4b17d89
diff --git a/README.md b/README.mdindex 4b27c33..4a859cf 100644--- a/README.md+++ b/README.md@@ -9,7 +9,7 @@[](LICENSE)[](https://python.org)[](https://dotnet.microsoft.com)-[](https://autodesk.com/products/revit)+[](https://autodesk.com/products/revit)[Quick Start](#quick-start) · [Documentation](docs/) · [API Reference](docs/tools.md)@@ -40,7 +40,7 @@ Production-ready MCP server enabling AI agents to control Autodesk Revit through### Prerequisites- Windows 10/11-- Autodesk Revit 2024 or 2025+- Autodesk Revit 2024-2026- Python 3.11+- .NET Framework 4.8@@ -121,7 +121,7 @@ Expected response:└───────────────┬─────────────────┘│ Revit API┌───────────────▼─────────────────┐-│ Autodesk Revit 2024/2025 │+│ Autodesk Revit 2024-2026 │└─────────────────────────────────┘```diff --git a/docs/architecture.md b/docs/architecture.mdindex 27bb683..6512ccd 100644--- a/docs/architecture.md+++ b/docs/architecture.md@@ -59,7 +59,7 @@ MCP Revit Bridge is a two-tier system connecting MCP clients to Autodesk Revit t│ Revit API│┌────────────────────────────────▼─────────────────────────────────┐-│ Autodesk Revit (2020-2024) │+│ Autodesk Revit (2024-2026) ││ - Document operations ││ - Element queries and modifications ││ - Export operations (PDF, DWG, IFC, CSV) │@@ -190,7 +190,7 @@ export MCP_REVIT_MODE=mock**Requirements**:- Windows 10/11-- Revit 2020-2024 running+- Revit 2024-2026 running- Bridge add-in installed and loaded**Configuration**:diff --git a/docs/install.md b/docs/install.mdindex f7be027..4cd1cda 100644--- a/docs/install.md+++ b/docs/install.md@@ -11,7 +11,7 @@ This guide covers installation for both mock mode (no Revit required) and bridge### Bridge Mode (Additional)- Windows 10/11-- Autodesk Revit 2020-2024+- Autodesk Revit 2024-2026- .NET Framework 4.8- Visual Studio 2019/2022 or MSBuild tools- Revit SDK (installed with Revit or available from Autodesk Developer Network)diff --git a/docs/target-frameworks-and-dependencies.md b/docs/target-frameworks-and-dependencies.mdindex 2b90d69..d9d188a 100644--- a/docs/target-frameworks-and-dependencies.md+++ b/docs/target-frameworks-and-dependencies.md@@ -21,8 +21,8 @@ The add-in project file is [packages/revit-bridge-addin/RevitBridge.csproj](../pIt conditionally targets:-- `net48` for Revit 2024 and earlier project settings-- `net8.0-windows` when `RevitVersion == 2025`+- `net48` for Revit 2024+- `net8.0-windows` for Revit 2025 and 2026That dual-target behavior is one of the most important build facts in the repo.diff --git a/scripts/package.ps1 b/scripts/package.ps1index d8250df..242bc78 100644--- a/scripts/package.ps1+++ b/scripts/package.ps1@@ -21,7 +21,7 @@ if (-not (Test-Path $distDir)) {}# Define versions to build-$versionsToBuild = @("2024", "2025")+$versionsToBuild = @("2024", "2025", "2026")if ($RevitVersion -ne "All") {if ($versionsToBuild -notcontains $RevitVersion) {Write-Error "Unsupported Revit version: $RevitVersion. Supported: $($versionsToBuild -join ', ')"@@ -46,7 +46,7 @@ foreach ($year in $versionsToBuild) {New-Item -ItemType Directory -Path $binDir -Force | Out-Null$sourcePath = "$PSScriptRoot\..\packages\revit-bridge-addin\bin\Release\$year"- # Adjust source path for net8.0-windows if 2025+ # Adjust source path for the selected target frameworkif ($year -ge "2025" -and (Test-Path "$sourcePath\net8.0-windows")) {$sourcePath = "$sourcePath\net8.0-windows"}