fusion360

This Fusion360 MCP Server acts as a bridge between MCP-compatible AI agents and Autodesk Fusion 360. It runs as a Python process that talks MCP over stdio to clients like Claude Code or other MCP clients, and it forwards commands to Fusion 360 over a TCP connection to the Fusion360MCP Add-in. With this setup, you can send design and automation tasks (such as creating sketches, extruding features, applying constraints, and querying scene information) from your AI agent, and the add-in executes the operations on the Fusion 360 main thread to ensure thread-safety and stable API access. The server exposes a wide range of tools (e.g., ping for health checks, get_scene_info, create_sketch, extrude, boolean_operation, export_stl, measure_distance, etc.) that enable complex CAD automation via natural or structured prompts. To use it, configure an MCP client to launch the fusion360-mcp-server in socket mode and point the client to the server so commands flow from the agent to the server and then to Fusion 360.

Prerequisites

• Python environment with uv (Python package manager) installed
• Autodesk Fusion 360 installed
• An MCP-compatible client (e.g., Claude Code, OpenCode, Codex, Cursor)

Install and set up the Fusion 360 MCP Add-in

1. Install the Add-in (development-friendly method):

./scripts/install-addon.sh

2. Manual add-in installation (example):

• macOS:

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

• Windows (PowerShell):

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

3. Start the add-in in Fusion 360: in Fusion, go to Shift+S → Add-Ins → Fusion360MCP → Run. You should see a log like "[MCP] Server listening on localhost:9876" in the TEXT COMMANDS window.

4. Connect your MCP client to the server

• The Fusion360 MCP Server is published on PyPI, so you can run it without cloning the repo.
• Claude Code example:

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

• Other MCP clients (stdio-based) connect using the stdio pathway. Typical command:

uvx fusion360-mcp-server --mode socket

5. Verification

• From your MCP client, run the ping tool. If it replies with {"pong": true}, the connection is healthy.

Uninstalling/Disconnecting

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

• The MCP server communicates over stdio with the client and exposes a TCP listener on port 9876 for the Fusion360MCP Add-in. Ensure your environment allows these connections.
• The available tools cover a broad range of Fusion 360 operations, including scene queries, sketching operations, feature creation, body operations, direct primitive shapes, surface and sheet metal operations, assembly management, inspection/analysis, appearance, parameter management, export options, and CAM/manufacturing workflows. When designing prompts for an agent, reference the tool names exactly as listed (e.g., get_scene_info, create_sketch, extrude, boolean_operation, export_step, cam_post_process, execute_code).
• If you encounter issues with the add-in listening message, verify that Fusion 360 is running and that the add-in is enabled and started in the Add-Ins panel. Check the MCP server logs for any TCP connection errors or MCP protocol mismatches.
• The environment variable configuration is optional; no specific vars are required for standard operation, but you can customize logging or behavior by injecting appropriate environment variables in your MCP client configuration if supported.
• For development workflows, the Quick Install method via symlink is recommended to allow rapid iteration on the server while testing inside Fusion 360.