revit-mcp
Related Servers
Alternatives to revit-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityFmaintenanceAllows AI to interact with Autodesk Revit via the MCP protocol, enabling retrieval of project data and automation of tasks like creating, modifying, and deleting elements.1354 npm472MIT
- AlicenseBqualityNot gradedmaintenanceAllows AI assistants to interact with Autodesk Revit through the MCP protocol, enabling the AI to create, modify, and delete elements in Revit projects.1554 npm1-
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to connect to Revit 2024 via MCP, inspect documents and selections, query and modify elements, and validate, preview, or commit plans with audit logging and rollback.-
- AlicenseBqualityCmaintenanceEnables AI agents to connect to Autodesk Revit and run Revit API Python, inspect models, capture screenshots, request user element selections or annotated snips, and manage multi-instance connections through MCP.13MIT
- FlicenseNot gradedqualityDmaintenanceEnables natural language control of Autodesk Revit through an AI-powered MCP server, allowing creation of walls, rooms, floor plans, and dimensions using conversational commands.-
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants like Claude Desktop or Cursor to control supported CAD applications through MCP tools for drawing, layer, block, entity, data export, and file/session operations using natural language or direct tool calls.-
TDQS
Scored across 13 tools
Most tools have clear distinct purposes (create vs delete vs query), but there is some overlap between operate_element (which can delete/hide) and delete_element, and between the three query tools (ai_element_filter, get_current_view_elements, get_selected_elements) which all retrieve elements but with different scopes. Descriptions are detailed enough to disambiguate in most cases.
The majority of tools follow a verb_noun pattern (delete_element, create_line_based_element, get_available_family_types, etc.). One outlier is ai_element_filter, which uses an 'ai_' prefix and a noun-like structure instead of a clear verb, but it remains readable and the overall pattern is mostly consistent.
With 13 tools, the server is well-scoped for a Revit MCP. Each tool covers a distinct aspect of model interaction—querying, creating (line/point/surface), modifying, deleting, and executing custom code—without feeling bloated or insufficient.
The tool set covers core read, create, delete, and some modify operations. However, direct parameter editing or element transformation (move/rotate) is missing; operate_element only supports visual actions like color, transparency, and hide. send_code_to_revit fills gaps but is a workaround, so the surface is not fully complete for typical Revit workflows.