cad2revit-mcp
Related Servers
Alternatives to cad2revit-mcp
No user-submitted related servers found.
Related Servers
- 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 gradedqualityAmaintenanceAI-powered control of Autodesk Revit through the Model Context Protocol, enabling natural language BIM workflows.111-
- AlicenseNot gradedqualityCmaintenanceEnables AI models to automate SolidWorks CAD at the feature level through MCP, including building parts from DXF/DWG drawings and reproducing existing parts via a deterministic compiler.1AGPL 3.0
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to control CAD applications like AutoCAD, ZWCAD, GstarCAD, and BricsCAD through natural language or direct tool calls. Supports drawing, layer and entity management, block operations, data export, and file handling via 7 unified MCP tools covering 56 CAD commands.-
- 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
- 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.136Apache 2.0
TDQS
Scored across 8 tools
Each tool maps cleanly to a distinct stage of the CAD-to-Revit pipeline: parse, detect, resolve, query, generate, run, check, and report. Although several tools mention anomalies or graph output, their actions and stage-specific purposes are clearly separated.
All tool names use lowercase snake_case with a consistent verb_noun structure, such as parse_dwg, detect_components, generate_revit_script, and check_model. The convention is predictable across the entire set.
Eight tools is well-scoped for an end-to-end CAD-to-Revit workflow, with one tool per major pipeline operation. No tool appears redundant, and the set is not so large that it becomes difficult to navigate.
The surface covers the full lifecycle from DWG parsing through component detection, ambiguity resolution, script generation, execution, validation, and reporting. Minor gaps remain, such as direct component-level inspection/editing outside ambiguity resolution and job-status or abort controls for long-running Revit operations.