Integrates with a live Autodesk Fusion session to run Python scripts, look up the Fusion API, inspect designs, validate bodies and interferences, capture multi-angle screenshots, produce photoreal renders, export CAD files, roll back changes, and invoke Fusion UI commands.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@fusionwright Design a 24-inch oak slat cabinet and give me the cut list."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Let an AI build in Autodesk Fusion for you.
An open-source MCP server that connects an AI assistant (Claude, ChatGPT, Cursor, anything that speaks MCP) to your live Fusion session. You describe what you want; the AI writes the Fusion code, looks at the result from several angles, measures and verifies it with Fusion's own kernel, fixes its mistakes, then renders it and exports files you can print, machine or send on. It is not tied to any kind of object: brackets, enclosures, gears, jigs, furniture, product mock-ups, anything solid.
examples/flange_fusion_run.py, run through fusion_run in a live Fusion document: sketch, extrude, join, cut. The script checks Fusion's volume (37.542 cm3) against the hand-computed value (37.542 cm3), then fusion_look took this picture.
"Make an 80 x 50 x 25 mm enclosure for a PCB with four screw posts and vent slots, then export a STEP and an STL."
"Model an M6 flange bracket with a 4-hole bolt circle, check it, and show me from the front."
"Take the part open in Fusion, find any invalid bodies or interferences and fix them."
"Add a 2 mm fillet to every outside edge and render it in brushed aluminium."
"Build a 24-inch bookcase from 3/4 inch plywood and give me every part as its own component."
The loop that makes it dependable: write code, look at it, measure it against the arithmetic, repair, repeat. Executable CAD is often not correct CAD (research), and a validation loop sharply improves results, so the tools are built around checking the work.
Related MCP server: furniture-designer-mcp
Autodesk Fusion on macOS (tested) or Windows (untested). The free Personal-use tier works.
Python 3.10+ and an MCP client.
It only uses Autodesk's documented public API and a legitimately licensed Fusion; it does not touch licensing.
Install the bridge add-in (once): run ./scripts/install_addin.sh, then in Fusion press Shift+S, pick FusionBridge, click Run (tick Run on Startup to make it automatic).
Register the server with your client.
Claude Desktop (claude_desktop_config.json):
{ "mcpServers": { "fusionwright": {
"command": "uvx",
"args": ["--from", "git+https://github.com/Cocoloco20/fusionwright", "fusionwright"] } } }Claude Code: claude mcp add fusionwright -- uvx --from git+https://github.com/Cocoloco20/fusionwright fusionwright
Ask. Exports land in ~/fusionwright-projects/ (override with FUSIONWRIGHT_HOME).
A small surface on purpose: fewer, higher-level tools beat dozens of thin wrappers.
Tool | Purpose |
| Is Fusion reachable? Which document is open? |
| Look up the real Fusion API (class members with docs) before writing code |
| Run Python inside Fusion (helpers predefined); returns a rollback checkpoint |
| Undo everything after a checkpoint |
| Compact design state: sizes, volume, invalid bodies, timeline problems |
| Kernel validation: body validity, timeline health, interference, expected size |
| Screenshots from iso / front / back / left / right / top / bottom |
| Photoreal render with Fusion's local renderer |
| STEP, STL, F3D, OBJ, 3MF, IGES, SAT (local files only) |
| Run any of Fusion's ~3,000 UI commands by id, or search them |
Inside fusion_run the names app, ui, design, root, adsk, P3, VI, FO, IN, coll() and board() are predefined; assign your answer to result. Fusion works in centimetres internally.
File | What it shows |
sketches, extrude / join / cut, picking profiles by area, checking against hand arithmetic |
Contributions of more examples (enclosures, gears, sheet metal, assemblies, anything) are welcome.
Autodesk's official Fusion MCP (announced May 2026) is a thin scripting bridge: read / screenshot, run a script, undo / redo. fusionwright adds a verification layer (kernel checks, multi-angle images, rollback checkpoints, an API lookup, UI-command access).
Community Fusion MCPs expose dozens of low-level CAD operations (the biggest lists 89 tools) and mostly stop there. fusionwright is deliberately small and runs its bridge on an authenticated loopback port.
See SECURITY.md. In short: loopback only, bearer token (~/.fusion-bridge-token, mode 0600), Host-header guard, request-size cap; fusion_run blocks file deletion, network access and cloud saves by default and returns a rollback checkpoint. It is a safety net, not a sandbox: code you let an AI run inside Fusion is powerful. Save your work first.
9 unit tests: the add-in's HTTP layer with a stubbed Fusion (token, host guard, size cap, error tracebacks) and a real stdio MCP round trip (tool list, safety guard, error messages).
Live tests against a real Fusion (pytest tests/integration): build a part and verify sizes, volume and interference with the kernel, views that must differ from each other, 5 export formats, a real render, rollback, API lookup, UI-command search, and a full MCP client round trip that returns images.
A 30-case capability suite (tests/integration/capability_suite.py) covering sketches, constraints, extrude / cut / revolve / sweep / loft, fillet / shell / chamfer / hole, patterns, booleans, components and joints, parameters, timeline edits, materials, measurement, 8 export formats, STEP re-import, CAM setup creation, configurations, rendering and more.
See docs/COVERAGE.md for what the Fusion API can and cannot do and docs/GOTCHAS.md for API traps found along the way.
Fusion-native drawings (adsk.drawing) can only be created from a design saved to your Autodesk cloud, so they are not automated here. Verify every dimension before cutting, printing or machining.
"Everything a human can do in Fusion" is not literally achievable through its API. fusion_ui_command and fusion_run cover a great deal, but some interactions (some drag gestures, cloud workflows) remain manual.
Adapter for Autodesk's official Fusion MCP as an alternative transport · more verified examples · driving models from Fusion user parameters · MCP Apps live 3D preview · MCP Tasks for long renders · a cross-model evaluation suite.
fusionwright is an independent project, not affiliated with or endorsed by Autodesk, Anthropic or OpenAI. "Autodesk" and "Fusion" are trademarks of Autodesk, Inc.
MIT licensed. Contributions welcome.
Look up the real Fusion API. Pass an exact class name (e.g. 'ExtrudeFeatureInput') to list its members with docs, or keywords (e.g. 'rectangular pattern') to find classes. Use this before writing fusion_run code.
Inputs: query (required), limit.
Validate the design: body validity, timeline health, body-to-body interference (kernel), and optionally the overall X/Y/Z size in inches. Returns pass/fail plus the reasons.
Inputs: tolerance_in, expected_size_in.
Export the active design to step, stl, f3d, obj, 3mf, iges or sat. Local file only (never the cloud).
Inputs: format (required), path.
Compact state of the active design: counts, overall size (in), volume, timeline problems, invalid bodies. detail='full' adds per-body boxes and user parameters.
Inputs: detail.
Screenshot the active Fusion viewport from named views: iso, front, back, left, right, top, bottom.
Inputs: views, width, height.
Photoreal render of the active design with Fusion's local renderer (quality 25-100; higher is slower).
Inputs: width, height, quality.
Delete every timeline item after checkpoint (a value returned by fusion_run).
Inputs: checkpoint (required).
Run Python inside Fusion's main thread (90 s limit). Predefined: app, ui, design, root, adsk, P3, VI, FO, IN,
coll(), board(name,x,y,z,sx,sy,sz) in inches. Set result to return data. Returns a checkpoint you can pass to
fusion_rollback. Dangerous operations (file deletion, network, cloud save) are blocked by default.
Inputs: code (required), label.
Check that Fusion and the bridge add-in are reachable; report the active document.
Inputs: no named parameters.
Run any of Fusion's ~3,000 UI commands by id (what a menu click does), or search ids/names with search.
Dialog commands stay open in Fusion until finished.
Inputs: id, search.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 10 tools
Most tools have clearly distinct roles: run vs. rollback vs. render vs. export vs. look are unambiguous, and fusion_api is clearly scoped to doc lookup. The one soft overlap is the diagnostic trio fusion_status / fusion_inspect / fusion_check, all of which report document and timeline health, though their descriptions differentiate reachability, summary state, and validation. fusion_run vs. fusion_ui_command is also a mild boundary (Python vs. UI command id) but the descriptions clarify it.
Every tool uses the same fusion_ prefix followed by a single lowercase verb or noun, in consistent snake_case (fusion_status, fusion_run, fusion_rollback, fusion_inspect, fusion_check, fusion_look, fusion_render, fusion_export). No camelCase or verb-style mixing appears anywhere in the set.
Ten tools sits squarely in the ideal range and each one maps to a distinct stage of the CAD workflow: connectivity, API research, execution, rollback, inspection, validation, visualization, rendering, export, and UI automation. None feel redundant padding, and no obvious capability is left to a missing tool.
The surface covers the full create-modify-verify-visualize-export lifecycle, with fusion_run serving as a general escape hatch for anything not exposed directly. Minor gaps remain: there is no explicit save or document open/create tool, so persisting work or switching documents must be done through fusion_run or UI commands. These are workable but not obvious from the tool list.
Parametric 3D CAD for AI agents: build print-ready parts, check them, export STL, 3MF or STEP.
Text-to-CAD: build exact STEP or 3MF/STL on the server, each stated requirement measured.
A browser 3D CAD for your AI: it scripts real-size models, uCAD builds them and returns pictures.
Write, check and render parametric laser-cutting designs in KerfScript, as SVG or DXF.