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.4131 PyPI5MIT
TDQS
Scored across 50 tools
Most tools target clearly distinct Archicad concepts: element editing, attributes, properties, classifications, issues, schedules, QA, and IFC export are cleanly separated. The main ambiguity comes from the generic execute_read_api_command and execute_write_api_command tools, which overlap every dedicated tool, plus some highlight/selection tools that could be confused without reading descriptions.
The set overwhelmingly follows a snake_case verb_noun convention, such as get_element_data, create_elements, list_issues, and edit_attributes. A few names are verb-only or less pattern-perfect, such as publish and capture_window, but the naming remains predictable overall.
Fifty tools is very heavy even for a broad CAD automation domain, and the surface includes dedicated tools alongside generic API escape hatches. While many tools are specialized, the count makes tool selection and discoverability substantially harder.
The surface covers an unusually broad Archicad lifecycle: selection, element CRUD, properties, classifications, attributes, issues, BCF import/export, IFC verification/export, schedules, publishing, QA rules, and a generic API fallback. Obvious gaps are minimal because the generic command tools can reach remaining operations.