inventor-mcp-server
Related Servers
Alternatives to inventor-mcp-server
No user-submitted related servers found.
Related Servers
- 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
- FlicenseNot gradedqualityBmaintenanceEnables AI assistants to control Autodesk Inventor via COM automation for part modeling, assembly constraints, drawing views, and more.4-
- 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 gradedqualityCmaintenanceEnables controlling Autodesk Fusion 360 from any MCP-compatible AI client through natural language. Exposes tools for creating sketches, drawing rectangles and circles, extruding, revolving, filleting, shelling, drilling holes and bolt-circle patterns, managing user parameters, and exporting STEP/STL files, plus batch generation of parametric variants.MIT
- AlicenseNot gradedqualityFmaintenanceMCP server for parametric 3D modeling in Autodesk Inventor, enabling natural language control of sketching, extrusion, hole features, and sheet metal operations.47MIT
- AlicenseNot gradedqualityDmaintenanceEnables natural language 3D modeling in Fusion 360 through an MCP server that translates user commands into Fusion 360 API calls. Supports creating, editing, and managing 3D objects, executing Python code, and capturing model views through conversational interactions.1MIT
TDQS
Scored across 82 tools
Tool categories overlap heavily: face location is split across list_faces/find_face/assembly_faces, edge lookup across list_edges/find_edge/list_component_edges, and hole creation across hole/hole_linear/cut_on_face/sheet_metal_cut. Descriptions usually clarify when to use which, but the number of near-neighbors makes misselection plausible.
All names are lower_snake_case and readable, but the convention is mixed: many use verb_noun (create_part, list_faces, draw_line) while many are noun-only (bom, properties, status, extrude, hole, flange, flat_pattern). The inconsistency is tolerable but makes the set less predictable.
82 tools is far above the practical range for an agent-facing MCP server; even though CAD is broad, numerous niche tools (frame_members, sweep_rotation, content_center, surface_to_solid) add selection load. Consolidation into tool families or a few dispatcher tools would improve usability.
The surface covers create/edit/assemble/export/drawing/BOM/material/document-management and includes an execute_python escape hatch, so most CAD workflows are supported. However, there is no explicit open_document or close_document tool and some work-feature operations rely on execute_python, leaving lifecycle gaps.