Skip to main content
Glama
joacos

archicad-tapir-mcp

by joacos
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to archicad-tapir-mcp

No user-submitted related servers found.

    Related Servers

    • archicad-mcp

      Boti-Ormandi
      A
      license
      A
      quality
      A
      maintenance
      MCP server for Archicad automation, enabling AI assistants to run Python scripts against running Archicad instances via the Tapir JSON API for complex workflows.
      4
      80 PyPI
      5
      MIT

    • Archicad-MCP

      alesdev88
      A
      license
      A
      quality
      A
      maintenance
      An MCP server connecting Claude to a running Archicad 29 instance for delivery-readiness QA via YAML rules and full Archicad API access, including querying, editing, creating elements, and schedule scheme editing.
      40
      3
      MIT

    • archicad-tapir-mcp

      psxcode
      F
      license
      A
      quality
      B
      maintenance
      Read-only MCP bridge for Archicad using the Tapir Add-On, enabling discovery, context binding, and safe read operations on Archicad projects.
      8
      -

    • Archicad MCP

      3d-mcp
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP-compatible assistants to connect to a local Archicad instance through its built-in JSON API, checking connection status, inspecting the current selection, and optionally invoking supported native commands with confirmation.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.8/5.0

    Scored across 53 tools

    Disambiguation3/5

    Several tools overlap in purpose (e.g., archicad_list_elements vs GetElementsByType/GetAllElements, archicad_create_slabs vs CreateSlabs, archicad_move_elements vs MoveElements, archicad_classify_elements vs SetClassificationsOfElements). Descriptions distinguish high-level safe/undoable helpers from raw Tapir commands, but with 53 tools an agent can still easily misselect.

    Naming Consistency2/5

    Mixed naming conventions: PascalCase Tapir wrappers (GetSelectedElements, CreateWalls) alongside snake_case archicad_* and tapir_* tools. The split signals different layers but is inconsistent from a naming standpoint.

    Tool Count1/5

    53 tools far exceeds the typical 3-15 range and includes both high-level and low-level duplicates for the same operations. Even for a complex BIM API, this volume is excessive for an MCP server and burdens tool selection.

    Completeness4/5

    Core operations for querying, creating, modifying, and deleting Archicad elements are covered, with generic tapir_run_command and archicad_run_api_command providing an escape hatch for missing commands. Dedicated tools for many element types (roofs, windows, beams) are absent, but the generic commands mitigate that gap.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources