bim-forge
AI-native open-source BIM coordination bootstrap: versioned model workflow with agent proposals and engineer review, currently a specification and safety harness at report-only level, before the first model-writing feature.
Summary rewritten from the vendor site because the catalog version did not match it.
What it does and how it connects
BIM Forge is AI-native, open-source BIM authoring and coordination infrastructure that treats a building model as a versioned, queryable project graph. Engineers describe work as issues, agents inspect the model, plan a bounded change, work in an isolated branch, run BIM-aware validators, and open a pull request containing the proposed model delta. People remain the final authority for consequential changes.
The repository is currently the bootstrap specification and safety harness: it defines the loop, storage direction, agent contracts and GitHub workflow before the first model-writing feature is added. The default operating level is L1 report-only, and no agent may merge or mutate a production model unattended.
The intended flow runs from project overview through context-aware 2D, 3D and VR model views to captured intent, an AI-prepared proposal, coordinated review and versioned acceptance. The recommended storage direction is a PostgreSQL source of truth plus object storage for immutable model snapshots, with IFC and native exports.
Alternatives
Compare side by side- BIM-IT Revit MCP
A vendor-neutral MCP capability layer for Autodesk Revit, rather than an IFC-based BIM coordination bootstrap.
- REVIT_MCP_study
A Revit MCP server with 194 tools and 84 BIM SOPs, rather than a BIM coordination bootstrap at report-only level.
- opentakeoff
A browser takeoff engine for construction plan sets with 61 MCP tools, rather than a BIM authoring and coordination bootstrap.
- AgentCAD (lizaixi01)
A CAD runtime for AI agents that makes 2D DXF drawings, rather than a BIM coordination bootstrap.
Recurring errors it addresses
Error Index entries this tool is built to reduce or work around.
- real IfcOpenShell IFC4 exports checked against the native model with an explicit loss inventory failed exchange check EX-02, came out inconclusive on EX-08, and a roundtrip added four failed observations including bounded-property loss.Error Index
- Bonsai expects a linked model's transform as 16 numbers in IfcDocumentReference.Identification, but files from other tools legally put text there, the parse throws, and the project opens with an empty scene.Error Index
- the IFC model diff keys property sets by name, so two same-named sets on one wall collapse into one and the diff reports the wall as "modified" with an empty list of changed components.Error Index
- In a millimetre project, whole-number-of-feet beam-system spacing exported as feet divided by 304.8, so 2 ft 0 in landed in the IFC as 0.0066 instead of 609.6 (off by a factor of about 93,000) on Revit 2024 and 2026 with no warning.Error Index
- On IFC import, an IfcDoor or IfcWindow with no opening or fill relationship to a host wall is dropped without a warning: on a 15 MB hospital model doors went 436 to 0, windows 305 to 0, with an empty warnings list.Error Index
Sources
Not verified
- Pricing (no price stated on the repository README)
- Real user voices (recent repo activity is the maintainer's own pull requests)
- A named individual builder beyond the repository owner handle Frederik91
- A public release (no releases are published)
- BIM authoring as a current capability (the README states the repository is a bootstrap specification before the first model-writing feature)
Last verified November 6, 2026. Listings are informational. The evidence score measures public, verifiable evidence and is not an endorsement or a compatibility claim.