autodesk-inventor-mcp
Related Servers
Alternatives to autodesk-inventor-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables AI assistants to control Autodesk Inventor via COM automation for part modeling, assembly constraints, drawing views, and more.5-
- AlicenseNot gradedqualityAmaintenanceEnables AI agents on Windows to build parts from JSON recipes, create and verify whole assemblies in a single call, check mass, center of mass, mates and interference, produce drawings with BOM, balloons and sections, work with sheet metal, and import/export STEP, IGES, PDF and DXF files. All edits run with automatic backups and verified rollback so user files are never left broken.12 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables an MCP-capable AI client to drive a locally installed, licensed Autodesk Inventor through its COM API for local modeling tasks. It supports creating and updating a rectangular plate and a parametric quickchanger concept assembly, opening and inspecting parts and assemblies, and returning viewport previews.MIT
- AlicenseNot gradedqualityAmaintenanceEnables an AI assistant to drive an already-running SOLIDWORKS session over its COM API, so it can build sketches, solid features, reference geometry, assemblies, mates, and engineering drawings, then inspect the result through topology listings, mass properties, measurements, and screenshots returned as images.1Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI-driven control of Autodesk Navisworks via COM, supporting model tree browsing, property queries, searching, isolation, recoloring, and screenshots without a .NET add-in.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables natural-language control of Autodesk Inventor to create parametric parts, sketches, holes, and sheet-metal features, and to inspect, save, or export models.MIT
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: status for connection/document discovery, model_info for body/feature overview, smallest_faces for defect hunting, face_neighbors for adjacency context, unwrap_try for testing unwrap operations, and script as an explicit escape hatch. There is no overlap in intent, and descriptions clarify when to use each.
Most names follow a consistent lower_snake_case convention (model_info, smallest_faces, face_neighbors, unwrap_try), with only 'status' being a bare noun rather than a verb_noun pattern. The convention is readable and nearly uniform.
Six tools is well-scoped for an Inventor COM bridge: each tool covers a specific analysis or discovery need, and the script tool prevents the surface from ballooning. No tool feels redundant or missing from the core set.
The surface covers connection status, model orientation, defect detection, neighbor inspection, unwrap testing, and arbitrary COM scripting, which handles the apparent mesh/unwrap analysis domain well. Gaps include no direct face repair or exclusion tools, but the script escape hatch mitigates most dead ends.