Design Automation & AILIBRARY/FORUM
Sign in
All postsMCP

Giving your AI agent hands in SOLIDWORKS

Lee Herron·Jun 18, 2026·2 min read

There's a gap between an AI that describes work and an AI that does it. For design automation, that gap is the difference between a demo and a tool you'd actually keep.

The bridge is MCP — the Model Context Protocol. It's how you give an agent a set of hands: a defined list of actions it can take in a real application, with real inputs and real results coming back.

From "tell me about" to "go do"

Without MCP, an agent's help ends at advice. "You could open the assembly and suppress that feature." Thanks. With an MCP server in front of SOLIDWORKS, the same sentence becomes an action: the agent opens the assembly, suppresses the feature, rebuilds, and tells you what changed.

The server's job is to expose a small, honest set of verbs — open, configure, get mass properties, export drawing — and to be strict about them. Each verb does one thing, validates its inputs, and reports what actually happened. No verb should ever guess.

Small surface, strict contract

The temptation is to expose everything. Resist it. A good MCP server for CAD is a curated surface:

  • Few verbs, clearly named. export_drawing beats a general "run this macro."
  • Every call validated. Bad inputs get rejected with a reason, not a silent no-op.
  • Results are data, not prose. The agent needs {mass: 4.2, units: "kg"}, not "it weighs about four kilos."

That discipline is what makes an agent trustworthy enough to leave alone with your files.

What it unlocks

Once the hands exist, the workflows compose themselves. "Configure this part for the three sizes we quote, export a drawing of each, and drop the mass into the quote." That's four tools chained by an agent — and it's the kind of tedious, error-prone sequence a human is glad to hand off.

The point was never to replace the engineer. It's to stop making the engineer do the click-work a machine should have been doing all along.

The solidworks-mcp server in the marketplace is where we'd start — it's the smallest thing that turns an agent from a talker into a doer.

#mcp#solidworks#agents

Get new posts by email

Occasional field notes on design automation and AI. No spam.

Keep reading

AI QuotingFrom RFQ to priced quote in one passMost quoting time isn't spent pricing — it's spent turning a messy RFQ into something a ruDriveWorksYour DriveWorks rules belong in a table, not nested IFsA nested IF that's six levels deep is a bug waiting for a deadline. Move the logic into a