Skip to main content
Glama
alesdev88

Archicad-MCP

by alesdev88
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Archicad-MCP

No user-submitted related servers found.

    Related Servers

    • ACC MCP

      nhantruong96
      A
      license
      A
      quality
      C
      maintenance
      MCP 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.
      45
      MIT

    • trimble-connect-mcp

      nhantruong96
      A
      license
      A
      quality
      C
      maintenance
      A 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.
      40
      MIT

    • ifcopenshell-mcp

      Daviidro
      A
      license
      A
      quality
      B
      maintenance
      An 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.
      8
      MIT

    • 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
      5
      MIT

    • redraft

      KaelinGraf
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server for AI-assisted project development and tracking. It exposes a typed graph of design nodes (concepts, decisions, requirements, etc.) and edges to Claude Code, enabling structured management of project knowledge and report generation.
      3
      Apache 2.0
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 36 tools

    Disambiguation3/5

    Most tools are scoped to distinct resources, but there is real overlap: the generic execute_read/write_api_command tools can perform many of the same operations as the dedicated read/write tools, and audit_delivery_readiness, verify_ifc_export_readiness, and run_rule all execute QA rules. Descriptions clarify the intended use, but an agent still has to choose among overlapping paths.

    Naming Consistency4/5

    The set overwhelmingly follows a snake_case verb_noun pattern (get_element_data, list_issues, edit_schedule_scheme, execute_write_api_command). It is slightly inconsistent because publish is a bare verb, read_schedule_scheme uses read instead of the more common get, and a few names are multi-word phrases like create_issues_from_failures.

    Tool Count2/5

    36 tools is well above the 25+ threshold and will be heavy for an agent to navigate in every context. The broad Archicad domain explains the variety, but the set could be consolidated: QA readiness checks, issue actions, schedule operations, and the generic API command tools all form clusters that could be trimmed or merged.

    Completeness4/5

    The surface covers the main Archicad workflows: element lifecycle, selections, Teamwork reservations, QA rules, issues/BCF, schedules, and a generic API escape hatch. Minor gaps exist, notably updating/closing issues and a dedicated live schedule-scheme enumerator, but the execute_* tools and existing schedule file tools provide workarounds.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources