fusion360-mcp
Related Servers
Alternatives to fusion360-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables LLM agents to build and modify parametric 3D models in Autodesk Fusion 360 through sketches, solid features, construction geometry, inspection tools, and in-Fusion Python execution. It connects MCP clients to a local Fusion add-in with status checks, error reporting, and unit-aware operations.154MIT
- AlicenseCqualityCmaintenanceEnables MCP-compatible assistants to control Autodesk Fusion for mechanical modeling, assembly editing, CAM workflows, inspection, and model export through Fusion's native MCP endpoint.391MIT
- AlicenseBqualityBmaintenanceEnables AI coding agents to drive Autodesk Fusion 360 over the Model Context Protocol, exposing 92 tools for sketching, modeling, querying, measuring and exporting CAD geometry through natural language. Includes an in-Fusion add-in that executes API calls safely on Fusion's main thread, with stdio transport compatible with any MCP client.892MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to inspect and automate Autodesk Fusion 360 through MCP, providing tools for CAD modeling, CAM manufacturing, and document management.-

Fusion Agent Harness MCPofficial
AlicenseBqualityCmaintenanceExposes CAD design tools (box, cylinder, shell, etc.) via MCP, allowing AI agents and clients like Claude to create and manipulate parametric CAD models in Autodesk Fusion or a simulator.61Apache 2.0- AlicenseNot gradedqualityDmaintenanceEnables natural language 3D modeling in Fusion 360 through an MCP server that translates user commands into Fusion 360 API calls. Supports creating, editing, and managing 3D objects, executing Python code, and capturing model views through conversational interactions.1MIT
TDQS
Scored across 15 tools
Each tool maps to a distinct step in the modeling pipeline (sketch → draw → extrude/revolve → modify → export), and descriptions explicitly state ordering constraints. Minor overlap exists between f360_hole and f360_hole_pattern (a pattern could be expressed as a single hole), and between f360_create_parameter and f360_set_parameter, though the create-vs-update semantics are stated.
All tools share a consistent f360_ prefix with snake_case naming and a verb-first style (create_sketch, draw_rectangle, export_step, set_parameter). A few names drop the verb and read as nouns/feature names (f360_hole, f360_shell, f360_fillet, f360_hole_pattern), which is a minor but noticeable deviation.
15 tools sit at the top of the well-scoped band and every one corresponds to a concrete modeling, parameter, or export operation with no filler. The surface is coherent for a bridge-based CAD scripting server.
The surface covers the happy path (sketch, extrude/revolve, fillet/shell, hole, parameters, STEP/STL export) but has notable gaps: extrude cannot cut/join/intersect, there are no boolean or pattern-of-feature operations, no selective edge/face picking, and no document save or model inspection tools. Agents attempting real part modeling will hit dead ends beyond simple prismatic geometry.