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)

SolidworksMCP-python (andrewbartels1)MechanicalSilent failureMedium confidence

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

  1. 1andrewbartels1/SolidworksMCP-python PR #229: An honest tool list: remove 33 planned tools, deprecate 8 duplicates, a verb listgithub.com

More recurring errors in SolidworksMCP-python (andrewbartels1)

See all 3 SolidworksMCP-python (andrewbartels1) errors

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.