← Back to Index
FreeCAD MCP bridge (neka-nat/freecad-mcp)MCADConfidence: Medium

When an agent fans out parallel create calls through the FreeCAD MCP bridge, the shared connection races: the first object is created even though its call reports failure, and the second object is silently never created with the status still showing healthy.

Impact Analysis

Persona
Mechanical Designer
Team Size Impact
5x Multiplier
Prototype Delay
1 Days
Est. Annual Cost
$13,500
  • 1 user · 1 month180 min
  • Rest of team720 min
  • Rest of year9,900 min

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

$75/hr assumed rate.

Annual team-minutes decomposed from the reported monthly inputs.

Evidence & Sources

2 Sources
freecad-mcp PR #165: isolate one connection per RPC call to fix the create_object race
github.com
→
freecad-mcp issue #160: silent create/drop race reported by bridge user
github.com
→

Analyst Notes

From the 2026-10-07 pain-radar digest (findings 2): maintainer fixed the same day with 14 new concurrency tests. The failure shape is general to single-threaded CAD engines (FreeCAD, SolidWorks), not just this bridge. Cost model assumes the engineer must manually reconcile every parallel call against live model state.