SolidWorks MCP bridge (alisamsam/Solidworks-MCP)MCADConfidence: Medium

A SolidWorks MCP bridge returned success JSON and even a normal-looking PDF export while the live document was wrong: a sketch asked for the Right plane silently landed on Front, and a macro call reported success=False with zero errors while never running. Only visual inspection inside SolidWorks itself revealed it.

Impact Analysis

Persona

Mechanical Designer

Team Size Impact

5x Multiplier

Prototype Delay

2 Days

Est. Annual Cost

$18,000

1 user · 1 month240 min
Rest of team960 min
Rest of year13,200 min

monthly_minutes × 12 × team_multiplier ÷ 60 × $75/hr = $18k/yr

$75/hr assumed rate.

Annual team-minutes decomposed from the reported monthly inputs.

Evidence & Sources

1 Sources

Solidworks-MCP issue #5: 9 end-to-end bugs where mock tests pass but the live SolidWorks document is wrong

github.com

→

Analyst Notes

From the 2026-10-06 pain-radar digest (finding 1): external user ran the bridge end-to-end against real SolidWorks 2024, documented 9 bugs with verbatim quotes, zero maintainer response recorded. Joins the 21+ source false-success cluster, now cross-platform (FreeCAD and SolidWorks COM). Cost model assumes every agent-run feature must be visually re-verified in the live document.