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
      80 PyPI
      5
      MIT

    • redraft

      KaelinGraf
      A
      license
      Not graded
      quality
      B
      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
    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

    A3.7/5.0

    Scored across 40 tools

    Disambiguation4/5

    Most tools target a clear resource+action (issues, elements, properties, selections, schedules), and descriptions explicitly steer callers to dedicated tools over the generic execute_read/write_api_command. A few boundaries blur: find_elements vs get_element_data vs get_model_summary all read elements at different granularity, create_elements vs create_swept_beam overlap, and set_element_data vs edit_property_definitions differ subtly. These are mostly resolvable from the descriptions.

    Naming Consistency5/5

    Names are uniformly snake_case with a verb_noun convention (list_issues, create_issue, get_element_data, set_element_data, delete_elements). Minor variants like the single-verb 'publish' and noun-first phrasings (get_model_summary) still fit the same readable pattern.

    Tool Count2/5

    40 tools is heavy for a single server and sits well past the 25-tool threshold. The surface spans many subdomains (issues/BCF, QA rules, elements, properties, schedules, Teamwork, raw API), so some breadth is justified, but the count is high enough to burden selection.

    Completeness5/5

    The set covers full lifecycles: element create/read/update/delete/select, property value and definition editing, issues with comments/BCF import-export, schedules, Teamwork reserve/release, and QA rules. The execute_read/write_api_command escape hatches close any remaining gaps.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources