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.45MIT
- FlicenseNot gradedqualityCmaintenanceMCP server to control Autodesk Navisworks Manage 2025 from Claude via natural language, enabling model inspection, property search, selection sets, and clash detection.-
- AlicenseAqualityCmaintenanceA 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
- AlicenseAqualityBmaintenanceAn 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
- AlicenseCqualityBmaintenanceEnables 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.253MIT
- AlicenseAqualityAmaintenanceMCP server for Archicad automation, enabling AI assistants to run Python scripts against running Archicad instances via the Tapir JSON API for complex workflows.4136 PyPI5MIT
TDQS
Scored across 41 tools
Most tools target clearly distinct resources and actions, and the descriptions do valuable work separating similar operations. However, the generic execute_read_api_command and execute_write_api_command overlap with many dedicated tools, and create_elements overlaps the specialized create_road_marking and create_swept_beam, so a few selections require careful reading.
Names consistently use snake_case with a predictable verb-first pattern: list_*, get_*, create_*, execute_*, edit_*, import_*, export_*, and so on. The few single-word or longer names such as publish, audit_delivery_readiness, and verify_ifc_export_readiness still fit the same readable convention.
With 41 tools, the surface is well beyond the typical 3-15 range and exceeds the 25+ threshold for being too many. The Archicad domain is broad, but the generic execute_read_api_command and execute_write_api_command already provide a wide fallback, making many dedicated tools additive rather than strictly necessary.
Coverage is broad across elements, properties, definitions, classifications, issues/BCF, QA rules, Teamwork, schedules, selection, and the full API. Minor lifecycle gaps exist, such as issue update/delete, detaching elements from issues, and editing schedule criteria, but the generic API tools provide workarounds so agents are unlikely to hit hard dead ends.