revit-mcp-hardened
Related Servers
Alternatives to revit-mcp-hardened
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceMCP server for Autodesk Revit (BIM) with 705+ API endpoints. Enables AI agents to create walls, place doors/windows, generate sheets, manage views, and produce construction documents via the Model Context Protocol. Uses named pipes for zero-crash Revit integration.22MIT
- AlicenseAqualityAmaintenanceAn MCP server that exposes an open Autodesk Revit model to MCP clients, enabling natural language inspection and editing of the model via Revit API calls through pyRevit Routes.211MIT
- FlicenseNot gradedqualityCmaintenanceNode.js MCP server enabling AI assistants to interact with Autodesk Revit for model operations, data queries, and sketch-to-building generation via LLM.231 npm-
- 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 gradedqualityCmaintenanceAn open-source MCP server that bridges AI agents to Autodesk Revit and IFC geometry, providing ASME B31.3 pipe thickness verification, UK HSE Legionella compliance auditing, and 3D BIM property inspection.1-
- -licenseNot gradedqualityNot gradedmaintenanceConnects MCP clients like Claude, Codex, and Cursor to a running Autodesk Revit session for typed BIM queries, verified model edits, family authoring, exports, and Power BI workflows. It is open-source, Apache-2.0, and designed for reliable, verified outcomes.-
TDQS
Scored across 26 tools
Each tool targets a distinct resource or operation: views, model info, elements, families, parameters, selection, creation, modification, deletion, visualization, document lifecycle, and system management. Descriptions clearly delineate boundaries, and overlapping-sounding tools like get_revit_status vs. get_revit_model_info are unambiguous.
All tool names follow a consistent verb_noun pattern in snake_case (list_, get_, create_, modify_, delete_, save_, etc.). Even compound names like create_line_based_element are consistent, and there is no mixing of conventions or vague verbs.
With 26 tools, the server is slightly over the typical well-scoped range, but the broad scope of Revit functionality justifies the count. Each tool serves a distinct purpose and there are no redundant tools, making it feel slightly heavy but still appropriate.
Several significant gaps exist: the descriptions explicitly reference an execute_revit_code tool that is not actually available, and there is no tool to load missing families, edit type parameters, or create certain element types. These gaps create dead ends and will cause agent failures when attempting those operations.