Archicad AI Pilot— MEPbridge ACAIstr | Version v0.1.2 Release, Read/Write & Automation Validation

[Bleufeng]

Hello, With 30 years of practice as an architect, I have long‑engaged in the full workflow spanning schematic design through project management. Amid the disruption brought by the AI revolution, I am exploring new directions for architectural design.

This project was born from a persistent industry pain point: cross-disciplinary coordination between architectural and MEP design on Archicad has long failed to gain widespread adoption across all teams. With the rise of artificial intelligence, Blender, Rhino and Revit have each rolled out MCP-powered automation capabilities, which motivated me to build this tool as a spare-time side project. While it cannot yet fully support end-to-end real-world construction projects, it has proven a critical breakthrough: AI can read all parameters stored within design files and trigger corresponding software operations. The full technical potential of this solution remains to be unlocked, hinging on the iterative advancement of large language models and future functional expansions. Its core purpose is simply to offer architects an open, experimental technical pathway to explore AI-augmented design. Beyond being a standalone Archicad MCP connector, this tool integrates dual operation modes — AI-driven smart workflow and manual command control — alongside an extensible platform for custom user expansions. The project MEPbridge ACAIstr is open-sourced and available for download on GitHub at https://github.com/bleufeng/mepbridge-acaistr 

所用操作系统：Windows

• General building elements: walls, columns, beams, slabs, roofs, doors, windows, stairs, objects, lamps, meshes, zones, and grids
• MEP domains: pipe, duct, cable carrier, flexible segment, take-off, systems, sizes, and route operations
• Model editing: move, rotate, mirror, copy, geometry changes, batch creation, selection, and deletion
• Project queries: project information, stories, libraries, hotlinks, properties, geometry, mesh, and viewport capture
• CollabAI Smart and Manual operation modes with risk classification, confirmation gates, and result readback
• MCP tools generated dynamically from ai-adapter/tool-descriptors.json
• Local user templates, custom commands, knowledge base, learning memory, and audit logs
• Reviewed Workbench modules loaded from modules/registry.json
• AC28/AC29 support with preview, confirmation, result readback, and failure handling according to operation risk

[Bleufeng]

v0.1.2 -Changed
Installation guides document the Node.js prerequisite, custom install paths, and a full step-by-step manual installation procedure covering administrator rights, locating the Archicad folder, choosing between Archicad 28 and 29, handling a previous build, and verifying the result.
The registered command and descriptor counts now come from a single ai-adapter/command-boundary.json file that the release gate, the public repository validator, CI, and the packaging scripts all read, instead of each carrying its own copy.
Command examples no longer contain hardcoded MEP system names or attribute indexes. Those identifiers are not stable across projects, locales, or Archicad versions, so omitting them lets the Add-On use the domain default. A static check keeps them out.
The Archicad runtime regression now checks returned content rather than only that response fields exist, and covers the favourite, layer-batch and classification write commands end to end, each restoring what it changed.
The internal command guide lists all 74 registered commands. It had 52, so the favourites, profile, view-map, classification and layer commands were absent along with the project and story queries. Command counts there now defer to ai-adapter/command-boundary.json.
The public repository validator no longer aborts on a Markdown link containing a stray percent sign; such a link is reported as broken instead.

[catalinpopa]

claude is also working on this, what s the difference?