Solidworks-MCP (ycpss91255-research) errors

6 recurring problems engineers report in Solidworks-MCP (ycpss91255-research), ranked by impact.

#82 by errors trackedMCAD

Recurring Solidworks-MCP (ycpss91255-research) errors, by impact

  1. 1Copying a 21-file SOLIDWORKS tree to another drive and opening the drawing pulled 1 document from the copy and 7 from the old location, with no prompt, so edits could land in the wrong tree.MCAD · Agent failure · 1 report74
  2. 2The MCP server found planes by their English names, so on a non-English SolidWorks no sketch could be made. Worse, "SwPlanes.get() returned the Front plane for any unknown plane name, so a typo could silently put a sketch on the wrong plane." The fix finds planes by the direction of their normal and makes an unknown name an error. Verified live with the planes renamed to Chinese. The same report exists upstream in German. The fix went straight to main first and the issue and PR were written after the fact. An agent that guesses a plane and reports success is worse than one that fails.MCAD · Agent failure · 1 report74
  3. 3The MCP server found planes by their English names, so on a non-English SolidWorks no sketch could be made. Worse, "SwPlanes.get() returned the Front plane for any unknown plane name, so a typo could silently put a sketch on the wrong plane." The fix finds planes by the direction of their normal and makes an unknown name an error. Verified live with the planes renamed to Chinese. The same report exists upstream in German. The fix went straight to main first and the issue and PR were written after the fact. An agent that guesses a plane and reports success is worse than one that fails.MCAD · Agent failure · 1 report74
  4. 4After 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.MCAD · Agent failure · 1 report66
  5. 5CloseDoc on an assembly crashes SOLIDWORKS 2023 SP5 intermittently, because SOLIDWORKS keeps a raw pointer to the API's IFeature wrapper without owning it and pywin32 frees the wrapper at the end of every execute_python script.MCAD · Agent failure · 1 report66
  6. 6A second SOLIDWORKS instance under the same Windows user cannot create its journal, so AutoRecover is off for it, and pointing the journal folder registry value elsewhere did nothing on SW 2023.MCAD · Agent failure · 1 report58

How it fails

  1. Agent failure6

Engineering tools that address these errors

Sourced from public community reports. Costs and delays on individual entries are modeled estimates, not measurements.