solidworksmcp-python (andrewbartels1)
A Python MCP server that drives SolidWorks on Windows through COM automation for modeling, sketching, drawings, analysis, and export, with agent orchestration utilities.
What it does and how it connects
solidworksmcp-python is a Python MCP server for SolidWorks automation with 154 tools, plus an optional agent and prompt-testing layer for AI-assisted workflows. It drives SolidWorks through the COM API with pywin32 on Windows 10 and 11, requires Python 3.13 or later, and is tested on SolidWorks 2026.
The README demo builds a 100 by 50 by 10 mm AISI 1020 mounting plate with four M5 clearance holes from a single prompt, then stacks two plates 10 mm apart, checks the result, and draws the assembly with a BOM, in 58 recorded tool calls. Each result is checked against a hand calculation for volume, mass, the 10 mm gap, and the BOM quantity.
Coverage spans sketching, extrusions, materials, verification, assemblies, and fully dimensioned drawings. The project also ships a documentation site with a walkthrough of the demo, including the agent plan and every call with its arguments, and a live test that replays the demo against SolidWorks.
Alternatives
Compare side by side- SolidworksMCP-TS (vespo92)
A TypeScript MCP server that routes simple SolidWorks operations through direct COM calls and complex ones through auto-generated VBA macros, rather than a 154 tool Python server.
- Solidworks-MCP (alisamsam)
A Python MCP server with 22 tools for SolidWorks parts, sketches, and features, rather than a 154 tool server with agent orchestration utilities.
- mcp-server-solidworks (eyfel)
Raises agent input to feature-level intent compiled into SolidWorks operations through a CAD-neutral intermediate representation, rather than exposing raw API calls as tools.
- solidworks-automation-skill (wzyn20051216)
An agent skill plus MCP toolkit for SolidWorks with a self-review loop that treats tool success as different from task success.
- MecAgent
A separate commercial desktop copilot that acts inside the open SolidWorks session, rather than an open source MCP server.
Recurring errors it addresses
Error Index entries this tool is built to reduce or work around.
- A shipped SolidWorks agent skill called interference-check API methods that do not exist (InterferenceDetection, GetInterference(index), GetComponents) and called Done() before computing, so its core validation step could never complete on a real machine. The check silently never ran.Error Index
- On SolidWorks 2016, the set_dimension tool reports success for a sketch dimension change the sketch cannot solve. The dimension stores the new value while the solver rejects it, the geometry does not move, the sketch is left no_solution, and check_errors reports nothing. Measured probes showed the mass and every segment unchanged against the ok:true answer.Error Index
- 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.Error Index
- Large assemblies can lock up on open with the feature tree failing to populate.Error Index
- Saving an assembly can trigger rebuilds that break mates and randomly alter mate dimensions.Error Index
Sources
Not verified
- No independent user voice found: recent issues are by the maintainer.
- Pricing: none stated on the repo.
Last verified November 6, 2026. Listings are informational. The evidence score measures public, verifiable evidence and is not an endorsement or a compatibility claim.