Skip to main content
Glama
tapir-archicad-mcp

tapir-archicad-mcp

by SzamosiMate

Related Servers

Alternatives to tapir-archicad-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Connects Claude and ChatGPT to a locally running Archicad project, enabling AI to read and modify building models, inspect 3D and 2D views, and follow guided skills through Archicad's JSON API and Tapir.
      7
      MIT
    • A
      license
      C
      quality
      C
      maintenance
      Enables 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.
      2
      53
      MIT
    • A
      license
      A
      quality
      B
      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
      132 PyPI
      6
      MIT
    • 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
      -

    TDQS

    A4.5/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each tool has a distinct role in the workflow: discovery, listing commands, fetching schemas, executing commands, and retrieving jobs. However, archicad_get_job has a dual purpose (listing all jobs vs. waiting for a specific job) and archicad_call_tool is a generic catch-all, which could cause minor confusion about when to use each.

    Naming Consistency4/5

    Most tools use snake_case with an archicad_ prefix and follow a verb_noun pattern (get_job, get_command_schema, list_commands). The exceptions are archicad_call_tool (vague verb_tool) and discovery_list_active_archicads (different prefix), but overall the convention is readable and mostly consistent.

    Tool Count5/5

    Five tools is well-scoped for a proxy server that exposes a large external API through a single generic executor. Each tool covers a necessary meta-operation, and no tool feels redundant or missing from the core set.

    Completeness4/5

    The surface covers the full lifecycle: discover instances, list commands, inspect schemas, execute commands, and track jobs. Minor gaps include no explicit job cancellation tool and no bulk schema retrieval, but agents can work around these.

    Maintenance

    ActivityActive
    ResponsivenessSyncing