Solidworks-MCP (ycpss91255-research)MCADConfidence: Medium

After about 4 hours 50 minutes, the SOLIDWORKS MCP server died with an access violation inside Windows COM while SOLIDWORKS itself stayed up, so the MCP connection was lost and the dump cannot say which tool call or COM method was running.

Impact Analysis

Persona

Mechanical Designer

Team Size Impact

5x Multiplier

Prototype Delay

3 Days

Est. Annual Cost

$30,000

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

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

$75/hr assumed rate.

Annual team-minutes decomposed from the reported monthly inputs.

Evidence & Sources

1 Sources

ycpss91255-research/Solidworks-MCP Issue #6: MCP server process crashed in combase (0xc0000005, null channel info in IDispatch proxy) while SOLIDWORKS stayed alive

github.com

→

Analyst Notes

From the Grok pain-radar digests, Oct 27-28 2026 (Oct 27 8:41 AM ET through Oct 28 7:41 AM ET digests plus the Haitch editions). Verified live 2026-10-28: issue/PR/thread read; title and state confirmed.