Archicad-MCP
Related Servers
Alternatives to Archicad-MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceMCP server that lets Claude manage an ISO 19650 / TCVN 14177 Common Data Environment on Autodesk Construction Cloud — projects, CDE folder trees, permissions, files, document status and naming compliance.451MIT
- FlicenseNot gradedqualityCmaintenanceMCP server to control Autodesk Navisworks Manage 2025 from Claude via natural language, enabling model inspection, property search, selection sets, and clash detection.-
- AlicenseAqualityDmaintenanceA local MCP server giving Claude access to Trimble Connect, with 40 tools for projects, folder trees, files, versions, members, groups, and permissions via the Core API v2.40MIT
- AlicenseAqualityDmaintenanceAn MCP server that lets users query, validate, convert, and compare IFC/BIM files using natural language. Runs fully locally and integrates with AI agents like Claude.8MIT
- AlicenseCqualityCmaintenanceEnables Claude and other MCP clients to query and modify an open Archicad project through Graphisoft's official JSON API and the ~250 commands of the Tapir add-on, covering model summaries, quantity takeoffs, quality checks, element creation (walls, slabs, zones), ID management, undo/journal history, and execution of arbitrary API or Tapir commands.53MIT
- AlicenseAqualityBmaintenanceMCP server for Archicad automation, enabling AI assistants to run Python scripts against running Archicad instances via the Tapir JSON API for complex workflows.4121 PyPI6MIT
TDQS
Scored across 56 tools
Most tools have clearly distinct purposes (element CRUD, selection, attributes, properties, classifications, issues, BCF, QA rules, collisions, schedules), and the descriptions explain boundaries well, including when to prefer dedicated tools over the generic API escape hatches. Some overlap remains: create_elements can create any type while create_swept_beam/create_road_marking/create_road_arrow specialize in single library parts, show_elements also selects and highlights (overlapping highlight_failures and set_selection), and read/write API command tools shadow the dedicated surface.
All names are snake_case and almost uniformly verb_noun (list_issues, create_issue, get_element_data, modify_elements, delete_elements, run_rule, export_ifc). The few exceptions like 'publish' are still verb-first and unambiguous, so the set reads predictably.
56 tools is heavy for an agent to navigate, though the Archicad domain is genuinely enormous and each tool maps to a real subdomain. The count could be reduced by folding the three specialized creation tools into create_elements, merging selection tools, and trimming the generic API escape hatches, so the set is over-fragmented rather than fundamentally mismatched.
Coverage is unusually broad: element lifecycle, attributes, property/classification definitions and values, schedules (read/validate/edit XML), issues and BCF, QA rules, collisions, selection, view capture, library-part learning, Teamwork reservation, IFC export and publishing. Gaps exist around issue update/delete, layout/sheet and publisher-set management, undo, and story management, but generic tools and the API escape hatches let agents work around most of them.