MCP server for Revit - Python
Related Servers
Alternatives to MCP server for Revit - Python
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI clients to interact with Autodesk Revit for building design, editing, analysis, clash detection, MEP, interop, documentation, and model persistence via 48 tools.MIT
- 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
- AlicenseAqualityBmaintenanceEnables AI assistants to execute designer-confirmed code and reusable capability packs inside a running Autodesk Revit instance.529 PyPI1MIT
- 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.1330 npm475MIT
- AlicenseAqualityFmaintenanceEnables AI to interact with Revit via MCP, allowing data retrieval and element creation, modification, and deletion.1330 npmMIT
- 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.1530 npm1-
TDQS
Scored across 33 tools
Most tools target distinct Revit operations, but several boundaries are blurry: get_revit_status vs get_revit_model_info, list_revit_views vs get_revit_view, and especially multiple batch creation tools for walls, footings, and foundations. Descriptions help, but an agent could still misselect among the structural batch tools or between generic and specialized operations.
Most tool names use snake_case with an action-oriented verb and clear object, such as open_document, save_document, list_levels, and batch_create_structural_slabs. There are minor deviations and long compound names like modify_or_delete_elements and finalize_and_join_structure, but the overall convention is readable and predictable.
At 33 tools, the surface is heavy for a single MCP server and exceeds the typical well-scoped range. Several highly specialized batch creation and QA tools could likely be consolidated or parameterized, making the set harder for an agent to navigate.
The server covers a broad Revit structural workflow: launch, document lifecycle, model inspection, views, families, PDF parsing, batch creation, duplicate checking, visual QA, modification, and geometry joining. Minor gaps remain around broader editing operations such as parameter updates or sheet/view creation, but execute_revit_code provides an escape hatch.