How justusbraitinger/autodesk-fusion-360-mcp-server works
Project Type and Purpose
• This is an integration project (“Fusion MCP Integration”) combining:
• A local MCP server (Server/MCP_Server.py) that hosts AI-driven “tools” and prompt definitions via HTTP/SSE.
• A Python-based Autodesk Fusion 360 add-in (MCP/MCP.py + MCP/commands + MCP/lib) that bridges incoming HTTP calls into Fusion’s API.
• Goal: Allow conversational CAD in Fusion 360 by routing user prompts (from Claude Desktop or VS Code) through the MCP protocol into Fusion and back.
File Structure Analysis
Top-level
• LICENSE, README.md
• MCP/ ← Fusion add-in directory
– MCP.py, config.py
– commands/ ← shared tool modules (entry.py in subfolders commandDialog, paletteSend, paletteShow)
– lib/fusionAddInUtils/ ← event & utility helpers
• Server/ ← standalone MCP server
– MCP_Server.py (defines server, tools, prompts)
– config.py, requirements.txt
• Patterns:
• “MCP” folder houses code loaded both in Fusion add-in and by the server (tool definitions).
• Server folder hosts the actual HTTP/SSE service.
• Commands subfolders map one-to-one with “tools” (e.g., sketch tools, modify tools, analysis tools).
README Insights
• Server.py: “Defines MCP server, tools, and prompts; handles HTTP calls to Fusion add-in.”
• MCP.py: “Fusion Add-in using custom event handler & task queue because Fusion API is not thread-safe.”
• External integrations: Claude Desktop, VS Code Copilot Chat via MCP.