Happy slice of mcp pizzaMCP.pizza

mcp-server-solidworks

MCP.Pizza Chef: eyfel

SolidPilot registers 46 abilities spanning sketches, extrusions, edges, ribs, sheet metal, patterns, materials, assemblies and mates, drawing sheets and dimensions, plus export to STEP, IGES, STL, PDF, DWG, and DXF. It also reads existing parts and DXF or DWG files so they can be rebuilt. This genuinely creates and modifies CAD documents, so work on copies. Windows only, and it needs a paid SolidWorks 2026 seat, the .NET build tools, and Python. No key or online account is involved.

Images/Design

Use This MCP server To

Rebuild a supplier's flat-pattern drawing into a real part Sketch and extrude a bracket by describing what I want Add holes, fillets, and chamfers without hunting through menus Export the finished part as a STEP file or PDF Compare two versions of a part and see what changed Lay out a drawing sheet with views and dimensions Set the material on a part and check its weight

README

SolidPilot

AI-driven CAD automation for SolidWorks — an MCP (Model Context Protocol) server.

SolidPilot Demo

SolidPilot lets an AI model work with SolidWorks at the CAD feature level. The goal is for the model to reason in terms of "which CAD intent am I realizing?" instead of "which API method should I call?". Intent is converted into a CAD-neutral intermediate representation, and a deterministic compiler lowers that representation into concrete SolidWorks operations.

SolidPilot is not a Claude-only plugin; it is a general bridge between SolidWorks and AI. Because MCP is an open standard, any MCP-capable AI client can connect — alongside Claude, OpenClaw, OpenAI-based agents, and local LLMs are also targeted. The architecture was designed for this extensibility from the start: the execution and planner layers do not know which client is calling them; a thin adapter per client reuses a shared bridge core. adapters/claude/ is the current implementation; supporting a new AI client means only adding a new adapter.

Repository: mcp-server-solidworks · Public name: SolidPilot · Target version: SolidWorks 2026

Core Idea

The SolidWorks API exposes thousands of methods. Presenting each one to the AI as a separate "tool" explodes context size and token cost — the economic problem that stalls similar projects.

SolidPilot solves this by raising the level of abstraction:

  • The AI produces intent at the feature level (for example, "put a hole in the top face").
  • That intent is expressed as a CAD-neutral Feature Graph IR.
  • A deterministic compiler lowers the IR into ordered, concrete SolidWorks operations.
  • A single feature therefore maps to many low-level operations, and one model call per request is enough.

Because the IR is the spine, the same machinery runs backwards: a 2D technical drawing is design intent expressed in two dimensions, so it can be read into the same IR and built.

From a 2D drawing file to a solid part

Hand SolidPilot a .DXF or .DWG — the file a supplier or a customer actually sends, with no model behind it — and it reconstructs the part:

drawing.dwg → analyze_drawing → (draw dialect: views, edge classes, chained contours,
              true-valued dimensions, bend notes) → Feature Graph IR → compiler → SolidWorks

The reader decides which of two answers the drawing warrants. When every decision the part needs is forced by the drawing itself — today, sheet-metal flat patterns — it lowers the whole part to IR on its own and analyze_drawing(mode='build') builds it in one call. When the drawing needs real engineering reading (the normal case for a machined part), it says so and hands over the structured analysis, which the model interprets under a versioned rule set (the recipe://usage/reverse resource) and builds through submit_feature_graph.

Either way the result is checked, not assumed: expected volume is computed from the drawing's own dimensions before building and read back after. Nine real drawings have been reconstructed this way so far — four in-house samples (two of them sheet metal) and five production manufacturing sheets (A4/A3/A1, 1:1 to 1:10, three different title-block templates), each verified against its own title-block weight to within 0.02% or against the original part to exact topology.

Architecture

mcp-server-solidworks FAQ

Do I need a key?
No key and no online account. What you do need is a paid SolidWorks 2026 licence, which is the real cost of using this.
Does it work on a Mac?
No. It drives SolidWorks through Windows-only plumbing, so a Windows machine is required.
Can it change my files?
Yes, extensively. It creates, edits, saves, exports, and closes documents, so point it at copies until you trust it.
Can I use this to turn a customer drawing into a model?
Yes, from DXF or DWG files. Flat sheet-metal parts can be built in one go, while machined parts need the assistant to interpret the reading first.
How hard is setup?
Hard. You install the .NET build tools, a Python environment, and a background service, then point your assistant at it.
Which apps does it work in?
Claude Desktop has the only finished connector today. The design allows other assistants to be added, but those are not shipped yet.
Is it still maintained?
Yes, very actively, with code changes landing within the past day or two.
The diagram says one-call building is only planned, is that right?
Not any more. That ability is registered and working, and the code now calls it the preferred way to create a part.
Will it work with an older SolidWorks?
It targets SolidWorks 2026, so earlier releases are not what it is built and tested against.