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
Merge main into task/B6 and resolve README conflicts
A. Sam Mohammad52bff043dec7
diff --cc README.mdindex 3fe4e7c,e3697fb..f5a6ebb--- a/README.md+++ b/README.md@@@ -18,23 -46,47 +46,50 @@@ MCP server and native bridges for AI-as</div>AEC Model Bridge connects MCP clients such as Claude Desktop, VS Code, GitHub-Copilot, and custom agents to Revit and a growing ecosystem of AEC platforms.+Copilot, and custom agents to a live session across multiple AEC platforms simultaneously.- The Python server handles MCP communication, routing queries to the correct provider:+ The Python hub handles MCP communication and routes each request to the relevant-desktop, headless, cloud, or compute provider. Revit commands run through a-native C# add-in and `ExternalEvent`, keeping API work on Revit's main thread.++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.+- **Rhino/Grasshopper**: Connects to Rhino.Compute or proxies to an active Rhino MCP server over SSE.+- **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 Omni-Bridge system blueprint as of June 12, 2026.++The status below reflects the Omni-Bridge system blueprint as of June 2026.+ Preview integrations are present but still have incomplete workflows or+ hardening tasks.++ ### Available Now++ Revit, IfcOpenShell, and Speckle are available integrations. Navisworks+ currently exposes bridge health and document metadata; model-tree,+ append/refresh, viewpoints, and clash workflows are next. Rhino.Compute is+ integrated, while live Rhino MCP connectivity remains a preview.++ ### Coming Soon++ This wave adds Excel and SharePoint workbook round trips, ACC/Forma workflows+ through Autodesk Platform Services, Solibri model checking, and Power BI+ templates backed by Speckle or a local Parquet/DuckDB data plane.++ ### Future Roadmap++ Future connectors are opportunity-driven and will be scheduled when each has a+ defined workflow, test access, and a supported API path.+## Highlights-- 100 MCP tools for model authoring, documentation, parameters, views, sheets,- exports, worksharing, architecture, structure, MEP, geometry, and QA.-- Native Revit add-in with no pyRevit or Dynamo dependency.-- Revit 2024, 2025, 2026, and 2027 support.-- Headless IFC, Speckle cloud, Rhino.Compute, and cross-platform provider- architecture.+- 100+ MCP tools for model authoring, documentation, parameters, views, sheets, exports, and QA.- - Native Revit & Navisworks add-ins with no Dynamo dependencies.++- 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.+- Localhost-only bridge by default for absolute security.+ - Mock mode for development and automated testing without Revit.## How It Works