Fusion360 MCP Server
Related Servers
Alternatives to Fusion360 MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables AI coding agents to drive Autodesk Fusion 360 over the Model Context Protocol, exposing 92 tools for sketching, modeling, querying, measuring and exporting CAD geometry through natural language. Includes an in-Fusion add-in that executes API calls safely on Fusion's main thread, with stdio transport compatible with any MCP client.892MIT
- AlicenseBqualityDmaintenanceConnects AI coding agents to Autodesk Fusion 360 for CAD automation, enabling natural language control over sketching, 3D modeling, and CAM operations. It uses a Python-based bridge and a custom add-in to execute over 80 tools ranging from simple geometry creation to complex assembly and parameter management.80467 PyPI143MIT
- 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
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact programmatically with Autodesk Fusion 360 for creating parametric 3D models through simple API calls.18-
- AlicenseAqualityCmaintenanceEnables 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.15MIT
- 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
TDQS
Scored across 96 tools
Most tools have clearly distinct purposes with rich descriptions, e.g. add_joint vs create_as_built_joint is explicitly differentiated. However, there are overlapping clusters: export vs export_stl/export_step/export_f3d (a unified wrapper duplicating three primitives), create_box vs create_box_parametric, and draw_circle vs draw_circles (batch). These overlaps slightly muddy selection.
Nearly the entire surface follows a consistent snake_case verb_noun pattern (create_sketch, draw_line, split_body, cam_create_setup). Minor deviations like the bare 'export' wrapper and 'ping' are cosmetic and do not break readability.
96 tools far exceeds a workable set, even for a broad CAD domain. While sketching, modeling, surfaces, sheet metal, CAM, measurement, and export are genuine sub-domains, several tools (export family, box family) could be consolidated, and the sheer count risks decision fatigue and misselection.
Coverage is impressive across sketching, solid/surface modeling, sheet metal, assembly/joints, parameters, measurement, CAM, and export, giving near-full lifecycle support. Minor gaps exist: no explicit delete_body/delete_component, mirror is body-only, and there is limited feature-editing / timeline-inspection beyond undo and suppress.