dsh-fusion360
Drives Fusion 360 from DeepSeek Harness with 13 MCP tools, including arbitrary Fusion API Python.
What it does and how it connects
dsh-fusion360 drives Autodesk Fusion 360 from DeepSeek Harness. From a chat the user can query the model, change parameters, export files, and run arbitrary Fusion API Python. Fusion 360 has no headless mode and its API is single-threaded, so the project is a two-part bridge: an MCP server over stdio talks JSON over loopback TCP to a Fusion 360 add-in that runs on Fusion's primary thread.
The README states the project was vibe-coded end to end by DeepSeek Harness itself, with the agent driving a live Fusion 360 through the bridge it was still writing. It drove 15 modeling commands against real Fusion and checked each result against its closed-form volume, and it documents 17 places where its recall of the Fusion API disagreed with reality, corrected from the actual error text. The docs include a measured verification table, Fusion API notes, and DSH compatibility notes.
Alternatives
Compare side by side- lambdacad-mcp
Drives an AutoLISP CAD through a LISP file bridge, rather than driving Fusion 360 through an add-in on its primary thread.
- solidifai
A desktop build123d studio with a live viewport, rather than a bridge that drives a running Fusion 360.
- harnesscad
A verifier-first harness for CAD operation streams, rather than a bridge into a live Fusion session.
- manifold3d-mcp
A Copilot and Claude Code plugin for parametric 3D printing models, rather than a bridge that drives Fusion 360.
- freecad-mcp (blwfish)
An MCP server that drives FreeCAD directly with 32 tools, rather than a bridge into Fusion 360.
Recurring errors it addresses
Error Index entries this tool is built to reduce or work around.
- Cloud-first file model makes local file control, rename/move/backup workflows feel alien and risky.Error Index
- General UI/UX is described as confusing and hostile for routine work.Error Index
- ChatGPT's Computer Use agent cannot drive Autodesk Fusion 360: selecting Always allow does not stick, a later window-state request fails with 'Computer Use was not approved to use fusion360', and the requested CAD design could not be created. Desktop logs recorded three allow-persist-always approvals with no persisted entry in the config.Error Index
- STEP carries geometry only and sketch DXF only 2D profiles, so moving a Fusion design to another parametric CAD tool loses its intent. The proposal is a JSON export of user parameters, the feature timeline, sketch constraints and component transforms, with the STEP kept as the reference to check the rebuild against by volume and bounding box.Error Index
Sources
Not verified
- Pricing: none stated on the repo.
- Real user voices: no real linked post read for this page; the repo has no open issues.
- No GitHub releases exist, so latest release fields are null.
- The one-liner's 13 MCP tools figure is stated in the README's Tools section and in the repository description.
- A named individual builder beyond the repository owner handle Leaveing00001
Last verified November 6, 2026. Listings are informational. The evidence score measures public, verifiable evidence and is not an endorsement or a compatibility claim.