SolidworksMCP-TS (vespo92)
A TypeScript MCP server for SolidWorks that routes simple operations through direct COM calls and complex ones through auto-generated VBA macros.
What it does and how it connects
SolidworksMCP-TS is a Node.js MCP server for automating SolidWorks via COM interop, connecting AI assistants such as Claude Desktop to SolidWorks for CAD automation tasks. It requires Windows 10 or 11, SolidWorks 2021 to 2025, and Node.js 20 or later, and it exposes SolidWorks operations as MCP tools over stdio.
Its routing layer handles a limitation of Node.js COM bridges: methods with 13 or more parameters often fail via direct COM calls. Simple operations with 12 parameters or fewer go through a direct COM call with winax, complex operations are executed through an auto-generated VBA macro, and failed operations fall back automatically with error context.
The README labels the project alpha and experimental, and states that most tools have not been validated against a live SolidWorks instance, with basic operations such as sketch planes and simple extrusions demonstrated. Its tool categories cover modeling, sketch, and drawing, including extrusions, revolves, sweeps, lofts, fillets, chamfers, constraints, and drawing views and dimensions.
What engineers report
The MCP tool mcp_solidworks_batch_run_macros fails validation because its input schema declares an array parameter without an items definition.
2026-08-11Read the original
Alternatives
Compare side by side- solidworksmcp-python (andrewbartels1)
A Python MCP server with 154 tools for SolidWorks parts, assemblies, and drawings through COM, with agent orchestration utilities, rather than a TypeScript server with a VBA macro fallback.
- Solidworks-MCP (alisamsam)
A Python MCP server with 22 tools for SolidWorks parts, sketches, and features, rather than a TypeScript server with a 13 parameter COM routing layer.
- 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
- 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.