tapir-archicad-mcp
Related Servers
Alternatives to tapir-archicad-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceMCP server for Archicad automation, enabling AI assistants to run Python scripts against running Archicad instances via the Tapir JSON API for complex workflows.45MIT
- AlicenseNot gradedqualityDmaintenanceEnables 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.24MIT
- FlicenseAqualityBmaintenanceRead-only MCP bridge for Archicad using the Tapir Add-On, enabling discovery, context binding, and safe read operations on Archicad projects.8-
- AlicenseNot gradedqualityAmaintenanceAn MCP server that bridges AI agents to Autodesk Revit, enabling local tool-based interaction with Revit models, including query, create, and modify operations, with an optional personal tool baking system.19Apache 2.0
- FlicenseNot gradedqualityBmaintenanceEnterprise-grade MCP bridge exposing Open Design's REST API as 15 MCP tools, enabling AI agents to create, iterate, and manage design projects via the Model Context Protocol.-
- AlicenseBqualityDmaintenanceConnects AI coding agents to Autodesk Fusion 360 for CAD automation, enabling natural language control over sketching, 3D modeling, and CAM operations. It uses a Python-based bridge and a custom add-in to execute over 80 tools ranging from simple geometry creation to complex assembly and parameter management.8085MIT
TDQS
Scored across 4 tools
Each tool has a distinct purpose: one lists commands, one discovers instances, one retrieves schemas, and one executes commands. There is no overlap or ambiguity between them.
Tool names follow a consistent [prefix]_[verb]_[noun] pattern, but the prefixes vary ('archicad_' vs 'discovery_'), which is a minor inconsistency. Overall the naming is clear and predictable.
With 4 tools, the server is well-scoped. It provides just the right set for a meta-API bridge: discovery, schema lookup, and execution.
The toolset covers the complete workflow: list available commands, get schema for a command, discover instances, and execute commands with pagination support. No obvious gaps for its stated purpose.