Fusion 360 MCP
Related Servers
Alternatives to Fusion 360 MCP
No user-submitted related servers found.
Related Servers
- AlicenseCqualityCmaintenanceEnables MCP-compatible assistants to control Autodesk Fusion for mechanical modeling, assembly editing, CAM workflows, inspection, and model export through Fusion's native MCP endpoint.391MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP-compatible coding agents to inspect and automate Autodesk Fusion designs through a local add-in, with whole-task approval, recovery checkpoints, undoable transactions, and geometry validation.Apache 2.0
- AlicenseAqualityBmaintenanceEnables LLM agents to build and modify parametric 3D models in Autodesk Fusion 360 through sketches, solid features, construction geometry, inspection tools, and in-Fusion Python execution. It connects MCP clients to a local Fusion add-in with status checks, error reporting, and unit-aware operations.154MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to operate Autodesk Fusion 360 through MCP with serialized command dispatch, safe spacing, and the ability to target open inactive documents.MIT
- AlicenseBqualityCmaintenanceConnects AI coding agents to Autodesk Fusion 360 for CAD/CAM automation, exposing 84 tools for sketching, modeling, assembly, inspection, export, and G-code post-processing through any MCP-compatible client.85MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that gives AI agents genuine 3D spatial understanding of Autodesk Fusion 360, enabling exact measurements, collision analysis, and free-space placement search, plus Fusion-native parametric authoring for clean, human-editable models.MIT
TDQS
Scored across 98 tools
Most tools target distinct operations, but several clusters overlap: export vs export_stl/step/f3d, set_appearance vs set_color, split_body vs split_face, render_view vs start_render vs export_view_sheet, and get_scene_info vs get_object_info vs list_components. The individual descriptions clarify boundaries, but with 98 tools an agent faces real misselection risk between these near-neighbors.
The surface is predominantly snake_case verb_noun (create_sketch, get_parameters, set_parameter) with a well-executed cam_ prefix group. Deviations include bare-verb modeling commands (extrude, fillet, sweep, loft), noun-style oddballs (boolean_operation, flat_pattern), and create_polygon breaking the draw_* sketch convention. Largely predictable, but not uniform.
At 98 tools, this nearly doubles the rubric's 50+ threshold for extreme mismatch. While Fusion 360 is a genuinely broad CAD/CAM domain, the surface could be consolidated substantially (e.g., one create_primitive with a type parameter, export as the sole export entry point, fewer measurement tools), making the count far more than an agent can effectively navigate.
Coverage is impressively broad across sketching, solid and surface modeling, sheet metal, CAM, rendering, parameters, measurement, and import/export. Minor gaps exist: no save/open/new document management, no individual body or feature deletion (only delete_all), no mesh-to-solid conversion, and drawing automation is experimental. Core design-to-manufacture workflows are fully covered.