VitruAI + ArchiCAD
The VitruAI for ArchiCAD integration installs as a signed ArchiCAD add-on that exposes live models to VitruAI agents through the ArchiCAD JSON Command API on ArchiCAD 26, 27, and 28 for Windows and macOS. It is currently shipping with 1–3 design partners, including firms already running the Tapir community add-on on the same JSON-API surface.
- Native ArchiCAD model access across elements, classifications, properties, and layout books read and written through the JSON Command API.
- Tapir-compatible deployment that extends the same API surface firms already use, without requiring an either/or decision on the community add-on.
- Cross-platform support for Windows and macOS on ArchiCAD 26+, with one code path to install, maintain, and update.
Install, requirements, and what runs through the integration.
-
Install in ~20 minutes
Drop the signed VitruAI add-on into ArchiCAD’s add-ons folder, restart ArchiCAD, and pair the add-on with the workspace token your admin issued from the VitruAI console. The installer validates ArchiCAD 26, 27, or 28 and confirms JSON Command API availability before first connect. Most firms treat this as a standard add-on rollout, alongside tools like Tapir or their Revit plugins.
-
ArchiCAD 26, 27, 28 on Windows and macOS
The integration runs on ArchiCAD 26, 27, and 28 with a single code path across Windows and macOS, using the JSON Command API instead of platform-specific bindings. That keeps deployment and support identical for mixed-OS teams and avoids separate installer tracks. Version checks in the add-on block unsupported builds, so older 25 projects stay on manual workflows until upgraded.
-
Co-exists with Tapir
Firms already running the Tapir community add-on keep it in place; VitruAI’s add-on extends the same JSON Command API surface without conflict or port reconfiguration. Both add-ons register their own command namespaces, so Tapir-based scripts and automations continue to run. This matters for teams already using Tapir for data extraction while VitruAI agents handle tasks like Archicad standards audit or code checks.
-
AI-assistant compatibility via MCP
For teams that want to drive ArchiCAD from an MCP-compatible assistant, the VitruAI add-on exposes the same JSON Command API endpoints used in the `claude archicad mcp` pattern. The MCP wiring, assistant configuration, and supported tools are documented on the dedicated MCP integration page. This page focuses on the ArchiCAD add-on itself; MCP connects that add-on to desktop assistants and IDEs when your IT team is ready.
-
Outbound HTTPS only
The ArchiCAD add-on initiates outbound HTTPS connections only, to a single VitruAI fully qualified domain name and IP range defined in your onboarding pack. Network teams typically add two firewall rules and choose a tenant region (eu-central or me-central) to keep data residency aligned with project storage. The same network profile also covers VitruAI agents that read IFC via the IFC / openBIM integration.
-
What agents can run through ArchiCAD
Once connected, VitruAI agents see ArchiCAD elements, classifications, properties, and layout books as first-class data, similar to how they already read Revit or IFC models. That means agents such as the Code Compliance Agent can evaluate ArchiCAD geometry and data against rule libraries, while studio QA/QC agents can audit naming, layer usage, and documentation standards alongside your Revit-based projects.
ArchiCAD integration FAQ
-
Does this work with ArchiCAD 25 or earlier?
No, the VitruAI add-on supports ArchiCAD 26, 27, and 28 only, because it depends on JSON Command API capabilities that are incomplete in 25 and earlier. On older projects, teams either upgrade the file or export to IFC and run checks through the IFC / openBIM integration. Firms planning a version uplift often pilot the add-on on a single 27 or 28 project first.
-
Does this conflict with Tapir?
No, the VitruAI add-on and the Tapir community add-on both use the ArchiCAD JSON Command API and co-exist in the same environment. Each add-on registers its own commands, so Tapir-based scripts continue to operate while VitruAI agents read and write model data. Many practices keep Tapir for lightweight data pulls and use VitruAI for heavier workflows like Archicad standards audit or rule-based compliance.
-
Can I drive ArchiCAD from Claude or Cursor (the `claude archicad mcp` pattern)?
Yes, but that wiring lives on the MCP side rather than inside the ArchiCAD add-on itself. The VitruAI add-on exposes ArchiCAD through the JSON Command API; the MCP layer then connects that capability to desktop assistants and IDEs following the documented `claude archicad mcp` pattern. For details on supported tools and configuration, see the dedicated MCP integration entry.
-
Is this cross-platform?
Yes, the same VitruAI add-on supports ArchiCAD 26, 27, and 28 on both Windows and macOS with a single installer track. Mixed-OS studios run one configuration and one workspace token, which simplifies IT support and updates. ArchiCAD on Linux is not planned, so Linux users typically access VitruAI through exported IFC models or via the Revit integration on other projects.
-
What does the Beta cohort look like?
The current Beta cohort includes 1–3 design partners running ArchiCAD-led practices with classification-driven templates and at least one jurisdictional compliance workflow. Typical pilots pair the ArchiCAD add-on with agents like the Code Compliance Agent or a studio QA/QC agent focused on documentation standards. Each Beta deployment ships a per-project accuracy report calibrated to the customer’s pipeline, covering both ArchiCAD-native and IFC-based checks.