fusion-cam
Related Servers
Alternatives to fusion-cam
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to inspect and automate Autodesk Fusion 360 through MCP, providing tools for CAD modeling, CAM manufacturing, and document management.-
- AlicenseBqualityCmaintenanceConnects AI coding agents to Autodesk Fusion 360 for CAD/CAM automation, exposing 84 tools for sketching, modeling, assembly, inspection, export, and G-code post-processing through any MCP-compatible client.85MIT
- AlicenseCqualityCmaintenanceEnables an agent to define parameters in millimeters, build and validate parts or assemblies in a live Autodesk Fusion session, then export STEP, STL, 3MF, and F3D files. It also supports inspection and verification workflows before and after generated geometry is produced.33MIT
- 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
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to build and edit native CAD parts and assemblies, inspect saved geometry and measurements, retain revisions, run mechanism and interference checks, and export STEP/STL/GLB artifacts through MCP tools.MIT
- AlicenseBqualityCmaintenanceConnects AI coding agents to Autodesk Fusion 360 for CAD automation, enabling natural language control over sketching, 3D modeling, and CAM operations. It uses a Python-based bridge and a custom add-in to execute over 80 tools ranging from simple geometry creation to complex assembly and parameter management.480512 PyPI152MIT
TDQS
Scored across 16 tools
Most tools target clearly distinct phases of the CAM workflow: connection status, design inspection, setup creation, strategy/tool discovery, operation creation, generation, posting, and G-code checking. The main ambiguity is between `status` and `cam_status`, and to a lesser degree between `inspect` and `cam_status`, but the descriptions make the boundary reasonably clear.
All names use snake_case and the `cam_` prefix sensibly groups CAM-specific operations. However, the set mixes noun-style names (`status`, `inspect`, `screenshot`) with verb_noun names (`cam_create_setup`, `import_step`), and `status` versus `cam_status` is an awkward near-collision.
At 16 tools it is slightly above the typical 3-15 range, but each tool maps to a meaningful step in a complex Fusion CAM workflow. No obvious redundant tool bloats the set, though a couple of read-only status/inspection tools could potentially be consolidated.
The core pipeline is well covered: import, inspect, create setup, discover strategies/tools, add operations, generate, post, and check G-code. However, there are notable lifecycle gaps: no tools to update or delete setups/operations, no way to modify an operation's parameters after creation, and no direct save/export of the design.