SolidworksMCP-python (andrewbartels1) errors
3 failures reported against SolidworksMCP-python (andrewbartels1), sorted by how they fail and ranked by impact.
#220 by errors trackedMechanical
Recurring SolidworksMCP-python (andrewbartels1) errors, by impact
- 1A merged drawing-package tool made every SolidWorks drawing call in one COM burst, crashing SolidWorks 2026 during its idle refresh; a live sign-off also found the DWG NO. field running across the A3 title block.Mechanical · Wrong design output · 1 report 366
- 2A SolidWorks MCP server's docs tool silently starts a hidden SolidWorks instance that holds a licence seat, and its error hint gives agents a confident wrong diagnosis for member-not-found errors.Mechanical · Silent failure · 1 report 566
- 3SolidWorks MCP server removes 33 tools that only ever returned not_supported An agent saw a long tool list where a third of it was placeholders. A live check showed design tables don't work through COM on SolidWorks 2026. save_file used to overwrite an existing file silently. The fix is an honest tool list plus path checks before SolidWorks is asked to do anything.Mechanical · Silent failure · 1 report66
How it fails
Engineering tools that address these errors
Sourced from public community reports. Costs and delays on individual entries are modeled estimates, not measurements.