SolidWorks 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.
Silent failure reported against SolidworksMCP-python (andrewbartels1)
What engineers report
A silent failure reported against SolidworksMCP-python (andrewbartels1): reports success, or uses stale data, while the result is wrong or missing.
Recorded mode: agent / silent failure
Analyst note
From the Grok pain-radar digests, Nov 14-15 2026 (Nov 14 8:41 PM ET through Nov 15 1:41 AM ET digests plus the Haitch edition). Verified live 2026-11-15: issue/PR read; title and state confirmed.
What it costs a team
Modeled annual cost
$30,000
For a team of 5
Prototype delay
3 days
Modeled schedule slip per occurrence
Time lost
240 min
Per engineer per month, about 1 incidents
How the cost is modeled
240 min/month × 5 engineers × 12 months = 240 hours × $125/hour = $30,000
A modeled estimate with medium confidence. Swap in your own team size and loaded rate to size it for your team.
Engineering tools that address it
No engineering tool profile lists this error yet. Browse tools that connect to SolidworksMCP-python (andrewbartels1).
Evidence
More recurring errors in SolidworksMCP-python (andrewbartels1)
- A 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 · impact 66
- A 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 · impact 66
Sourced from public community reports. Costs and delays are modeled estimates, not measurements. Know a better source or a fix? Tell us at hello@productflo.io.