Archicad

io.github.alesdev88Published by GitHub account alesdev88v0.14.0Updated Nov 7, 2026

Delivery-readiness QA and full official + Tapir API access for a running Archicad 29.

VerifiedSTDIODesktop onlyDeveloper ToolsData & AnalyticsMedia & Design

Overview

AI-generated overview

Connects an MCP client to a running Archicad 29 model so the assistant can inspect, change and create building elements and run delivery QA.

What you can do
  • Find and read elements, properties, classifications, GDL/IFC data, attributes and clashes
  • Change, move or delete elements, attributes, property definitions and classifications
  • Create elements of 44 types, swept beams, road markings, and GDL objects from mesh models
  • Run YAML office-standard rules and delivery-readiness audits, highlight failures and raise issues
  • Look at the model: show elements, capture the window, manage selection, issues, BCF, IFC export and publishing
  • Reserve and release elements in Teamwork, read and edit schedule schemes, and call about 500 API commands through a gateway
When to use it
Useful when an architect or BIM team wants to query and edit an open Archicad project in plain language, check a model against office standards before delivery, or script repetitive modelling and export tasks.
Requirements
A running Archicad 29 (or 30) on macOS or Windows, desktop only. Install the bundled extension in Claude Desktop, or use uv for Claude Code. Most tools need the Tapir add-on, which the server can install into Archicad's Add-Ons folder. Rules need a YAML folder set via the extension setting or ARCHICAD_MCP_RULES_DIR.
Before you install
Changes write to the live project: edits are dry-run first and delete or move need confirm=true, but commits still modify the model, so save first. Archicad 29 can crash on a property read and lose unsaved work; the server cannot prevent it. It talks only to Archicad on 127.0.0.1 with no telemetry, but what it reads goes to the MCP client.

Installation

In SourceWeft

  1. Open Archicad in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Archicad MCP

Connects Claude, ChatGPT or any MCP client to a running Archicad 29 (30 works too) on macOS and Windows. You ask in plain language; the server does it through Archicad's JSON API and the Tapir add-on.

  • Check a model against office standards. YAML rules run against the open model: pass or fail, a score, and the failing elements, highlighted or turned into issues.
  • Find, read and change elements. Criteria queries, properties, classifications, GDL and IFC data, favourites, attributes, clash checks.
  • Create elements. Walls, slabs, columns, doors and windows, zones, stairs, dimensions and 30-odd more types.
  • Everything else. About 500 official and Tapir commands through one gateway.

[!WARNING] Save before reading properties. Archicad 29 can crash on a property read, even of one element, taking unsaved work with it. The server cannot prevent it. Ask the client to run save_project first, and see Known issues.

Install

Claude Desktop: download the bundle for your platform from the latest release and drag it into Settings > Extensions. It carries its own Python, so there is nothing else to install.

PlatformFile
Windowsarchicad-mcp-0.14.0-win32.mcpb
macOS (Apple silicon)archicad-mcp-0.14.0-darwin-arm64.mcpb

To update, ask Claude to update the extension: it downloads the newest release, checks it and opens Claude Desktop's install dialog.

Claude Code (needs uv):

bash
uv tool install archicad-mcp-serverclaude mcp add archicad -- archicad-mcp --mode full

Tapir: most tools need the Tapir add-on in Archicad. Ask the client to install Tapir, or run archicad-mcp install-tapir. It puts the pinned Tapir 1.8.0 into Archicad's Add-Ons folder, checked by sha256, and never replaces an existing one unless told to. Restart Archicad afterwards.

Intel Macs, a hand-written Claude Desktop config, ChatGPT, Codex and all the settings: Install.

Check it works

With Archicad open, ask the client to list Archicad instances. It shows the port, Archicad version, open project and Tapir version, and what to install when something is missing. If the client shows no tools at all, see Check it works.

What you can ask

AreaTools
QAaudit_delivery_readiness, run_rule, list_rules, verify_ifc_export_readiness, highlight_failures, create_issues_from_failures
Find and readfind_elements, search_definitions, get_element_data, get_model_summary, get_project_info, list_attributes, find_collisions
Changeset_element_data, modify_elements, apply_favorites, move_elements, delete_elements, edit_attributes, edit_property_definitions, edit_classifications
Createcreate_elements (44 types), create_swept_beam, create_road_marking, create_road_arrow, and learn_library_part for placing furniture, doors and windows from a sketch
Lookshow_elements, capture_window, the selection tools
Issues and outputIssue Manager and BCF, export_ifc, publish, save_project
Teamworkreserve_elements, release_elements
Schedulesread_schedule_scheme, edit_schedule_scheme, validate_schedule_scheme, through Scheme Settings' XML (Archicad has no schedule API)
Library partsmesh models (OBJ, 3DS) to GDL objects: build_gdl_object, deploy_gdl_object
Gatewaylist_api_commands, describe_api_command, execute_read_api_command, execute_write_api_command

Every tool in detail, with what it checks and what it needs: Tools.

Safe by default. Changes to elements, data and definitions are a dry run first, showing current and new values. Delete and move also need confirm=true. Elements Archicad would refuse (another view's, a hidden or locked layer, a hotlinked module, not reserved in Teamwork) are skipped with the reason, never unlocked. A commit reads back what it wrote and reports what did not land.

Office rules

Rules are YAML files in a folder you point the server at (the extension's Office rules folder setting, or ARCHICAD_MCP_RULES_DIR):

yaml
- id: walls-fire-rating  type: property-required  property: "OFFICE/Fire Rating"  applies_to: { element_type: Wall }  severity: error

Six rule types are built in, and custom checks go in Python beside the YAML. Keep real office standards outside this repository. See Writing rules.

Docs

Privacy

The server runs on your machine and talks only to Archicad on 127.0.0.1. There is no telemetry and no backend. What it reads goes to the MCP client that asked, normally Claude, under that client's privacy terms. See PRIVACY.md.

License

MIT. See LICENSE.

Source: README.md at commit abab3d3

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

11
  1. v0.14.0LatestNov 7, 2026
  2. v0.13.1Nov 4, 2026
  3. v0.13.0Nov 3, 2026
  4. v0.12.0Oct 29, 2026
  5. v0.11.0Oct 23, 2026
  6. v0.10.0Oct 19, 2026
  7. v0.8.0Oct 12, 2026
  8. v0.7.1Sep 30, 2026
  9. v0.6.0Sep 23, 2026
  10. v0.5.4Sep 17, 2026
  11. v0.5.3Sep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts