Revit MCP Automation
Related Servers
Alternatives to Revit MCP Automation
No user-submitted related servers found.
Related Servers
- 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.1524 npm1-
- AlicenseBqualityAmaintenanceAsk, check and change live Revit models from Claude, Cursor or any MCP client. One undo per change, read-only switch. Revit 2022-2027.797MIT
- AlicenseAqualityBmaintenanceEnables AI assistants to execute designer-confirmed code and reusable capability packs inside a running Autodesk Revit instance.51MIT
- AlicenseNot 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.MIT
- AlicenseAqualityFmaintenanceEnables AI to interact with Revit via MCP, allowing data retrieval and element creation, modification, and deletion.1324 npmMIT
- 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 maps to a distinct step in the managed-Revit lifecycle: status probe, model open, dialog inspection, dialog interaction, and result retrieval. The only mild overlap is between get_revit_automation_status and get_revit_operation_result, though the descriptions make clear one reports instance state and the other reports an async operation's outcome.
All five tools use snake_case with a predictable verb_noun pattern (get_/open_/click_) and a consistent revit namespace segment. No mixing of conventions or vague verbs.
Five tools is tightly scoped to the stated purpose of driving a separate managed Revit instance and resolving its dialogs. Each tool earns its place as a distinct phase of that workflow.
The dialog-handling lifecycle is closed-loop (detect, click, retrieve result) and status/open are present, but there is no way to close or reset the managed instance and no tool to actually issue a model operation whose result would be retrieved. Agents depend on external tools for anything beyond opening a file.