Fusion360 MCP Server

Beta — This project is under active development. APIs and tool behavior may change between releases. Use at your own discretion. Feedback and bug reports welcome via GitHub Issues.

MCP server that connects AI coding agents to Autodesk Fusion 360 for CAD automation.

Tested with Claude Code. Works with any MCP-compatible client — OpenCode, Codex, Cursor, or anything that speaks the Model Context Protocol.

How it works

Any MCP Client ←(stdio MCP)→ This Server ←(TCP :9876)→ Fusion360MCP Add-in ←(CustomEvent)→ Fusion Main Thread

Two components:

1. MCP Server (this repo) — Python process that speaks MCP protocol to Claude and forwards commands over TCP
2. Fusion360MCP Add-in (installed in Fusion's AddIns folder) — runs inside Fusion 360, executes API calls safely on the main thread

Prerequisites

• uv (Python package manager)
• Autodesk Fusion 360
• An MCP-compatible client (Claude Code, OpenCode, Codex, Cursor, etc.)

Installation

1. Install the Fusion 360 Add-in

Download the latest add-in from Releases, or clone the repo and copy the Fusion360MCP/ directory into Fusion's AddIns folder:

macOS:

cp -r Fusion360MCP ~/Library/Application\ Support/Autodesk/Autodesk\ Fusion\ 360/API/AddIns/

Windows (PowerShell):

Copy-Item -Recurse Fusion360MCP "$env:APPDATA\Autodesk\Autodesk Fusion 360\API\AddIns\"

Then start it in Fusion: Shift+S → Add-Ins → Fusion360MCP → Run

You should see [MCP] Server listening on localhost:9876 in the TEXT COMMANDS window.

2. Connect your MCP client

The MCP server is published on PyPI — no need to clone this repo.

Claude Code

claude mcp add fusion360 -- uvx fusion360-mcp-server --mode socket

Other MCP clients

The server runs over stdio, so any MCP-compatible client can launch it. The command is:

uvx fusion360-mcp-server --mode socket

{
  "mcpServers": {
    "fusion360": {
      "command": "uvx",
      "args": [
        "fusion360-mcp-server",
        "--mode", "socket"
      ]
    }
  }
}

3. Verify

Call the ping tool from your client. If it returns {"pong": true}, everything is connected.

Uninstalling

1. Remove the fusion360 entry from your MCP client config
2. Stop the add-in in Fusion (Shift+S → Add-Ins → Fusion360MCP → Stop)
3. Delete the add-in folder from Fusion's AddIns directory

Available Tools (80)

Scene & Query

Sketching

Features

Body Operations

Direct Primitives

Surface Operations

Sheet Metal

Construction Geometry

Assembly

Inspection & Analysis

Appearance

Parameters

Export

CAM / Manufacturing

Code Execution

MCP Protocol Features

• Tool annotations — each tool is tagged with readOnlyHint, destructiveHint, and idempotentHint so MCP clients can auto-approve safe operations
• Resources — fusion360://status, fusion360://design, fusion360://parameters for passive state inspection
• Resource templates — fusion360://body/{name}, fusion360://component/{name} for dynamic entity lookup
• Prompts — create-box, model-threaded-bolt, sheet-metal-enclosure workflow templates
• Structured errors — tool results include isError=True when the add-in reports failures
• Mock mode — --mode mock returns plausible test data without Fusion running (all responses include "mode": "mock")

Development

uv sync --dev       # install deps
uv run pytest -v    # run tests
uv run ruff check   # lint

Notes

• All Fusion API units are centimeters (Fusion's internal unit).
• One operation per tool call. Batching multiple operations crashes the add-in.
• Commands time out after 30 seconds.
• Add-in logs to ~/fusion360mcp.log.

Acknowledgements

Inspired by BlenderMCP — the socket bridge architecture originated there.

Also built on ideas from the existing Fusion 360 MCP ecosystem:

• ArchimedesCrypto/fusion360-mcp-server
• Joe-Spencer/fusion-mcp-server
• JustusBraitinger/FusionMCP
• zkbkb/fusion-mcp
• mycelia1/fusion360-mcp-server
• sockcymbal/autodesk-fusion-mcp-python

License

MIT