A deep-dive into connecting Claude Code to Autodesk Fusion 360 via the Model Context Protocol — what's possible, what's not, and how to build it.
The 60-second verdict on whether this is worth building.
faust-machines/fusion360-mcp-server already provides 80 tools covering sketching, 3D features, assemblies, CAM, export, and more. It's MIT-licensed, actively maintained, and uses the proven BlenderMCP socket-bridge pattern. The 3D design space is wide open — parametric modeling, assemblies, materials, CAM, and export all have solid API support.
The catch: Fusion 360's Drawing/2D API is essentially non-existent. You cannot programmatically create drawing sheets, add dimensions, place views, or modify title blocks. This is confirmed by Autodesk staff on the forums as of March 2026. If technical drawings are critical to your workflow, you'll need to generate them outside Fusion (e.g., via CadQuery + DXF export).
What the API can (and cannot) do.
Languages: Python (recommended) and C++. JavaScript was deprecated.
Two modes: Scripts (run once, exit) and Add-ins (persistent, background). For MCP, you need an add-in.
Threading: Fusion is single-threaded. All API calls must execute on the main thread. Background threads communicate via CustomEvent.
Units: Everything is in centimeters internally.
Location: ~/Library/Application Support/Autodesk/Autodesk Fusion 360/API/AddIns/
| Domain | API Support | Feasibility | Notes |
|---|---|---|---|
| Sketches (2D geometry) | Full | EASY | Lines, arcs, circles, splines, constraints, dimensions |
| 3D Features | Full | EASY | Extrude, revolve, sweep, loft, fillet, chamfer, shell, boolean |
| Parametric Design | Full | EASY | Create/modify/delete parameters, read design timeline |
| Assemblies & Joints | Full | MEDIUM | Components, joints, as-built joints, rigid groups |
| Materials & Appearances | Full | EASY | Apply from material library by name |
| Surface Operations | Full | MEDIUM | Patch, stitch, thicken, ruled, trim |
| Sheet Metal | Full | MEDIUM | Flange, bend, flat pattern, unfold |
| Construction Geometry | Full | EASY | Planes, axes at offset/angle |
| Export/Import | Full | EASY | STL, STEP, F3D, IGES, OBJ |
| Inspection | Full | EASY | Distance, angle, mass, volume, CoM, interference |
| CAM/Toolpaths | Full | MEDIUM | Setups, operations, toolpath gen, G-code post |
| Drawings/2D Docs | None | NONE | No API for sheets, views, dims, annotations, title blocks |
| Generative Design | None | NONE | Confirmed by Autodesk: no API access |
| Simulation | None | NONE | Stress, thermal, modal not API-accessible |
| T-Spline/Form | Limited | HARD | Vertex-level manipulation not fully exposed |
Open, save, close, activate — react to user actions on documents.
Created, execute, preview, validate — hook into Fusion's command framework.
Fire events from background threads to main thread. Critical for the MCP bridge — this is how you safely call the API from a socket server thread.
Startup, idle, document activation — lifecycle hooks for the add-in.
How Claude Code talks to Fusion 360.
MCP Client
Tool calls
Python process
stdio transport
TCP localhost
JSON protocol
Python add-in
CustomEvent → API
Fusion 360's API can only be called from within the Fusion process. There is no external/remote API. Brian Ekins (Autodesk API Expert): "Fusion doesn't have anything built-in to the API to support this."
The solution is the BlenderMCP pattern: a persistent add-in inside Fusion runs a socket server on a background thread. The external MCP server connects as a client, sends commands as JSON, and the add-in uses CustomEvent to marshal calls to the main thread where the actual API executes.
Add-in starts TCP server on localhost. External MCP connects as client. Fast, reliable, bidirectional. Used by faust-machines.
Add-in runs Flask/BaseHTTPServer. External processes send HTTP requests. Easier to debug but more overhead. Used by sockcymbal.
Shared directory for command/response files. Add-in polls. Slowest, but works when nothing else does.
Don't build from scratch — there are 6+ projects on GitHub already.
| Category | Count | Tools |
|---|---|---|
| Scene & Query | 4 | ping, get_scene_info, get_object_info, list_components |
| Sketching | 13 | create_sketch, draw_rectangle, draw_circle, draw_line, draw_arc, draw_spline, polygon, constraints, dimensions, offset, trim, extend, project |
| 3D Features | 18 | extrude, revolve, sweep, loft, fillet, chamfer, shell, mirror, hole, circular_pattern, rectangular_pattern, thread, draft, split, offset_faces, scale, suppress, unsuppress |
| Body Operations | 4 | move, boolean, delete_all, undo |
| Direct Primitives | 4 | box, cylinder, sphere, torus |
| Surface Operations | 5 | patch, stitch, thicken, ruled, trim |
| Sheet Metal | 4 | flange, bend, flat_pattern, unfold |
| Construction | 2 | planes, axes |
| Assembly | 4 | component, joint, as_built_joint, rigid_group |
| Inspection | 5 | distance, angle, physical_properties, section_analysis, interference |
| Appearance | 1 | set_appearance |
| Parameters | 4 | get, create, set, delete |
| Export | 3 | STL, STEP, F3D |
| CAM | 7 | create_setup, create_operation, generate_toolpath, post_process, list_setups, list_operations, get_operation_info |
| Code Execution | 1 | execute_python (REPL-style arbitrary code) |
What Claude Code could do in Fusion's 3D modeling environment.
Full sketch API: create geometry on any plane or face, add constraints, apply dimensions. This is where most designs start.
Available sketch primitives: lines, arcs, circles, ellipses, splines, polygons, slots, text, construction lines, reference points, projected geometry
Constraints: coincident, collinear, concentric, equal, horizontal, vertical, midpoint, parallel, perpendicular, tangent, fix/unfix, symmetry
The full suite of 3D operations is API-accessible. Claude can build complex solid bodies step by step.
New body, join, cut, intersect. One/two sides, symmetric, to object. Taper angle support.
Full or partial revolution around an axis. All operation types.
Profile along a path. Guide rails, twist angle, scale.
Between multiple profiles. Guide rails, center line, closed loft.
Edge selection by reference. Variable radius fillet. Chamfer by distance or angle.
Hollow out a solid body. Select faces to remove. Specify wall thickness.
Union, intersect, subtract between bodies. Essential for complex geometry.
Rectangular and circular patterns. Mirror across planes.
Box, cylinder, sphere, torus — one-call creation for simple shapes.
Create multi-component assemblies with mechanical joints. More complex due to reference management.
Create new components, create occurrences (instances), organize component hierarchy. Each component has its own origin and features.
Rigid, revolute, slider, cylindrical, pin-slot, planar, ball. Define motion limits, offsets, and driven joints.
Create joints that maintain current component positions. Useful when components are already placed correctly.
Lock components together. Useful for treating sub-assemblies as single units.
This is where Claude + Fusion gets really powerful. Named parameters mean Claude can iterate on designs by tweaking values.
Claude can read and analyze the current design state — the foundation for design review and optimization.
Mass, volume, surface area, center of mass, moments of inertia
Measure between any two entities (points, edges, faces, bodies)
Check if bodies overlap — critical for assembly validation
Cut through a body with a plane, inspect cross-section
Read component tree, feature timeline, parameter values
Get overall dimensions of any body or component
The hard truth about 2D technical drawings.
Forum confirmation: "I cannot find any public API objects or methods to directly access drawing sheets or title blocks." — Autodesk Community Forums, 2026-03-31
Use CadQuery (Python parametric CAD) to generate 2D profiles and export as DXF. Not integrated with Fusion, but produces standards-compliant 2D drawings.
Export the 3D model as STEP, then use FreeCAD's TechDraw or LibreCAD to generate drawings programmatically. Multi-tool pipeline.
Theoretically possible to use OS-level UI automation (pyautogui, AppleScript) to click through Fusion's Drawing UI. Fragile, unreliable, not recommended.
Autodesk knows this is a gap. The Drawing workspace was only added to Fusion in 2021 — the API may eventually follow. No timeline.
From design to G-code — fully API-accessible.
"Set up a 3-axis milling operation for this part. Use a 6mm flat end mill, 0.5mm stepdown, conventional milling. Post-process for a Haas VF-2."
Define stock, WCS origin, fixture orientation
2D adaptive, 2D pocket, 2D contour, face, drilling, 3D adaptive, 3D contour, etc.
Calculate toolpaths for any operation
Generate G-code for specific machines (Haas, Fanuc, etc.)
Read existing setups, operations, and their parameters
Access tool library for cutter selection
Example conversations showing what's possible.
Unlike scripting, Claude maintains context. "Make it taller" works because Claude remembers which parameter controls height.
If an operation fails, Claude can read the error, diagnose it (e.g., sketch not closed, invalid geometry), and try an alternative approach.
Claude can explain why design choices matter — wall thickness vs. strength, fillet radius vs. stress concentration, material selection tradeoffs.
The execute_python tool lets Claude write arbitrary Fusion API code for operations not covered by the 80 predefined tools.
Other ways to get LLMs doing CAD.
| Tool | Type | API Quality | Drawing Support | MCP Exists? | Best For |
|---|---|---|---|---|---|
| Fusion 360 | Commercial CAD |
|
NONE | Yes (6+) | Full mechanical design + CAM |
| FreeCAD | Open-source CAD |
|
YES (TechDraw) | Yes (3+) | Free, drawings, open ecosystem |
| CadQuery | Python library |
|
DXF export | Yes (1) | Code-first parametric CAD |
| OpenSCAD | Script-only CAD |
|
NONE | Community | Simple programmatic models |
| Zoo.dev (KittyCAD) | AI-native CAD |
|
KCL-based | API-first | Text-to-CAD, AI-first workflow |
| Blender | 3D modeling |
|
N/A | Yes (BlenderMCP) | Artistic/visual 3D, not engineering |
Use Fusion 360 MCP for 3D design and CAM (where it excels), and CadQuery or FreeCAD for automated 2D technical drawings (where Fusion's API fails). Claude can orchestrate both — design in Fusion, export STEP, generate drawings in FreeCAD's TechDraw.
First text-to-CAD model generating B-Rep surfaces (not meshes). Outputs STEP files. Uses KCL (KittyCAD Language). The most promising AI-native approach.
Autodesk's own generative AI plug-in for Fusion 360. Text-based interaction for CAD modeling. Not clear if publicly available or API-accessible.
OpenSCAD-like declarative framework within Fusion 360. Functional/declarative geometry creation — a good mental model for LLM-driven design.
| Paper | Year | Key Contribution |
|---|---|---|
| Large Language Models for CAD: A Survey | 2025 | First systematic survey — taxonomy of 6 key areas |
| Text-to-CadQuery | 2025 | New paradigm for CAD generation with LLMs via CadQuery |
| Text2CAD | 2024 | Generating sequential CAD models from instructions |
| Conversational CAD | 2024 | Natural language interface for parametric 3D modeling |
| CADialogue | 2025 | Multimodal LLM-powered conversational CAD assistant |
| From Dialogue to Design | 2026 | GenAI-based automation of parametric CAD |
| Generative AI for CAD Automation | 2025 | Leveraging LLMs for CAD workflows |
| LLM4CAD | 2025 | Multimodal LLMs for 3D design (ASME) |
| MIT: LLMs in Design & Manufacturing | 2025 | How LLMs help humans in design and manufacturing |
A phased approach to building the Fusion 360 MCP integration.
faust-machines/fusion360-mcp-server. Install the add-in in Fusion. Configure Claude Code's MCP settings to point at the server. Verify with ping tool. Run in mock mode first to validate the MCP protocol without Fusion.
get_scene_info, list_components, get_object_info, get_physical_properties, parameters. Let Claude understand existing designs without modifying them. Build confidence in the bridge stability.
Everything you need to get started.
Research compiled April 2026 • Sources: Autodesk API Docs, GitHub, Autodesk Forums, arXiv, ResearchGate
Generated by Claude Code × Firecrawl