Vulcan
SolidWorks AI agent that executes modeling tasks from natural-language instructions.
What it does and how it connects
Vulcan is an AI add-in that turns a plain engineering request into editable SolidWorks features, with the tagline natural language in, parametric SolidWorks geometry out. The user describes the part in the add-in panel, the model fills a typed JSON feature tree, and a C# add-in builds it with the native SolidWorks feature APIs. The result is a native feature tree the user can edit, not a mesh, a macro or a generated script.
The release track is deterministic by design: the model returns JSON, not code, and no exec call runs in the release track. The JSON contract covers extrude, cut, revolve, fillet and chamfer features, with circle, rectangle, polygon, ellipse and slot profiles, and explicit hole placement. Every response opens in an editable JSON preview, and nothing reaches SolidWorks until the user reviews and confirms the feature tree.
The system has three layers: a C# and WPF client on .NET Framework 4.8, a Python and Flask server over HTTP REST and JSON, and any OpenAI-compatible model endpoint, with the user's own key DPAPI-encrypted on their machine. The server can run locally, in Docker or behind a tunnel, and only the client needs Windows. The README badges SolidWorks 2025 and Python 3.10 or later.
Alternatives
Compare side by side- Millwright
An open-source AI workbench that drives SolidWorks through direct native tool calls with a visual feedback loop, rather than an add-in that executes a JSON feature tree.
- MecAgent
A commercial desktop copilot that acts inside the open SolidWorks session, rather than an open-source add-in that executes a JSON feature tree.
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
- 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
- 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
- Saving an assembly can trigger rebuilds that break mates and randomly alter mate dimensions.Error Index
- Large assemblies can lock up on open with the feature tree failing to populate.Error Index
Sources
Not verified
- Pricing: none stated on the repo.
- Real user voices: no real linked post read for this page.
- A named individual builder beyond the Robusr organization
Last verified November 6, 2026. Listings are informational. The evidence score measures public, verifiable evidence and is not an endorsement or a compatibility claim.