This Fusion 360 MCP server exposes a set of tools that map natural language prompts to Fusion 360 API actions. It accepts tool calls via its API and generates Python scripts that can be executed inside Fusion 360 to perform operations such as drawing sketches, creating geometry, and applying modifications like extrudes or fillets. The server is designed to parse a sequence of tool calls (either a single tool or multiple tools in order) and produce a corresponding Fusion 360 Python script that reproduces the requested steps in a single workflow.

You can interact with the server in two modes: standard HTTP API mode and MCP mode. In HTTP mode, you can query available tools, call a single tool, or call multiple tools in sequence. In MCP mode, the server reads tool instructions from stdin and writes the resulting script to stdout, enabling it to be integrated into larger MCP pipelines and automation setups. The available endpoints include GET / to verify the server is running, GET /tools to list tools, POST /call_tool to execute one tool, and POST /call_tools to execute a sequence of tools. Tools are organized into categories such as Create, Modify, and Export, each exposing Fusion 360 actions like CreateSketch, DrawRectangle, Extrude, Fillet, and ExportBody. The server outputs Python scripts that you can run in Fusion 360’s Script Editor to realize the requested design changes.

Prerequisites:

• Python 3.9 or higher installed on your system
• Autodesk Fusion 360 installed (for testing the generated scripts)
• Internet access to install Python dependencies (via pip)

Installation steps:

1. Clone the repository: git clone https://github.com/yourusername/fusion360-mcp-server.git cd fusion360-mcp-server

2. Create and activate a Python virtual environment (optional but recommended): python -m venv venv

   On Windows

   venv\Scripts\activate

   On macOS/Linux

   source venv/bin/activate

3. Install dependencies: pip install -r requirements.txt

4. Run the server (MCP mode): cd src python main.py --mcp

   The server will be ready to accept MCP-style input on stdin and emit scripts to stdout

5. For HTTP API access (optional): cd src python main.py

   Access http://127.0.0.1:8000 for API endpoints

Notes:

• Ensure Fusion 360 is installed and available when running the generated scripts inside Fusion 360.
• If you modify tool definitions, update src/tool_registry.json and the script templates accordingly.

Tips and caveats:

• The server generates Fusion 360 Python scripts; you can customize or extend templates in SCRIPT_TEMPLATES as you add new tools.
• If a tool requires specific parameters (e.g., plane, dimensions), ensure you provide sensible defaults or validate inputs before sending API requests.
• In MCP mode, scripts are written to stdout; you can redirect output to a file or pipe it to Fusion 360 for automation.
• Common issues include mismatched parameter names or missing Fusion API context (e.g., running the script outside Fusion 360). Verify tool definitions align with the generated script logic.
• Check the tool registry at src/tool_registry.json for supported tools and their parameter schemas. Each tool references a Fusion API doc link for guidance.
• When integrating with Cline or other MCP clients, configure the mcpServers section in your MCP settings with the correct command and arguments to point to the local script.