tapir-archicad-mcp
Related Servers
Alternatives to tapir-archicad-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceConnects 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.7MIT
- AlicenseCqualityCmaintenanceEnables 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
- AlicenseAqualityBmaintenanceMCP server for Archicad automation, enabling AI assistants to run Python scripts against running Archicad instances via the Tapir JSON API for complex workflows.4132 PyPI6MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients like Claude to interact with Graphisoft Archicad through the Tapir add-on's JSON commands. Supports automated Archicad operations and custom tool integration for architectural design workflows.36MIT
- FlicenseAqualityBmaintenanceRead-only MCP bridge for Archicad using the Tapir Add-On, enabling discovery, context binding, and safe read operations on Archicad projects.8-
- AlicenseCqualityBmaintenanceEnables AI clients to inspect, visualize, modify, launch, and manage Autodesk BIM models, views, families, and documents through a local authenticated bridge, including direct code execution.33MIT
TDQS
Scored across 5 tools
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.
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.
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.
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.