AI Agents for CAD — Let Claude Build Real 3D Models

Connect Claude Code, Claude Desktop or Cursor to OwlCAD over MCP and let an agent build real parametric CAD, check it through a kernel, and export STL or 3MF.

Let an AI agent build real, editable CAD.

Connect Claude Code, Claude Desktop, or Cursor to OwlCAD and ask for a part. The agent authors a genuine parametric model, checks it through a real CAD kernel, looks at a render of it, and hands you a print-ready file, and an OwlCAD project you can open and edit.

Uses no AI credits · Works with any MCP client · Free in-page bridge

Headless, or driving the editor you already have open

They are different jobs. Pick by whether a browser is in the loop — an agent working on its own wants the server; an agent working alongside you wants the bridge.

MCP server — no browser needed

For tool-calling agents: Claude Code, Claude Desktop, Cursor, or any MCP client. The agent authors, checks, renders and exports without a browser anywhere, then hands you a link into the editor to finish.

  • Point your client at https://mcp.owlcad.com with an access token. Pro plan, because the hosted kernel does the work.

In-page bridge — an agent at the wheel

For browser agents: Claude in Chrome, computer-use loops, anything driving a real page. The viewport is a WebGL canvas with no accessibility tree, so clicking it means guessing pixel coordinates and errors compound. The bridge replaces that with direct calls, and a screenshot call so the agent can see what it actually did. Every edit is an ordinary undoable command, so Ctrl+Z takes back anything it does.

  • Open /app?agent=1. Free: it runs in your own browser, so there is no token and no plan to buy. An agent can inspect any editor session; the parameter is what lets it EDIT, and only for that tab.

Not a mesh generator — a CAD tool it can drive

The difference that matters: your agent is not guessing at a surface. It builds the same parametric tree the OwlCAD editor uses, and it can check its own work.

Author a real parametric model

Shapes, booleans, fillets, patterns and mechanisms: the same node tree the editor edits. Dimensions stay editable afterwards, so you can take over where the agent left off.

Check its own geometry

A CAD kernel runs on every call and reports whether the shape is watertight, how many triangles it has, and its exact size in millimetres. A model that computes to nothing is caught, not delivered.

Look at what it made

It can render the model from named views and actually see the picture. That is the only way an agent can tell a shape that computes from a shape that is right — the failure everything else misses.

Check it will print

Overhangs, thin walls, and whether it fits a named printer’s build volume, the checks you would otherwise only discover in your slicer.

Export a print-ready file

STL, 3MF, or OBJ, handed straight back to the agent. Or skip the file: it saves a normal OwlCAD project and gives you the link.

Work with what you already have

Point it at a project you saved earlier, or hand it an STL to import and build on. It picks up your work instead of starting over each time.

Give your agent a CAD tool.

Create an access token, point your MCP client at OwlCAD, and ask it for a part. The MCP server needs a Pro plan. Or open /app?agent=1 and let a browser agent drive the editor, free. Neither route spends AI credits.

Frequently asked questions

Can Claude or ChatGPT actually build 3D models?

With OwlCAD connected, yes. OwlCAD runs an MCP server, so an agent like Claude Code, Claude Desktop, or Cursor can author a real parametric model, evaluate it through a CAD kernel, look at a rendered image of it, check it for printability, and export a print-ready STL or 3MF, all without a browser.

Is this the same as an AI mesh generator?

No. A mesh generator hands back a surface you cannot meaningfully edit. Here the agent authors the same parametric node tree the OwlCAD editor uses, so the result opens as an ordinary project with editable dimensions, history and booleans. You can take over at any point.

Does it use AI credits?

No. The agent you are already talking to writes the model itself, and OwlCAD does the geometry, so no OwlCAD AI credits are spent. The MCP server needs a Pro plan because the hosted CAD kernel is doing real work on every call; the in-page bridge is free.

Do I need a Pro plan?

For the MCP server, yes: the hosted CAD kernel runs on our machines on every call. For the in-page bridge, no: open the editor at /app?agent=1 and an agent can drive it in your own browser, free and with no token, because the geometry runs on your machine. Neither route spends AI credits.

How does the agent know if the model is actually right?

It can check. The evaluate tool runs the real CSG kernel and reports whether the shape is watertight, its triangle count, and its exact size; render returns images the agent can look at, which is the only way it can tell a shape that computes from a shape that is correct; print_check reports overhangs, thin walls, and whether it fits a named printer.

What do I get at the end?

An ordinary OwlCAD project in your dashboard, with a preview image, that you can open and edit like anything else, plus an STL, 3MF or OBJ export if you want the file directly.

OwlCAD · Features · Pricing · Gallery · For schools · AI agents · MCP server · STL editor · STL viewer · 3MF editor · 3MF viewer · OBJ editor · DXF editor · STEP viewer · OBJ viewer · GLB viewer · AI 3D generator · Model customizer · Customizers gallery · Compare all · vs TinkerCAD · vs Onshape · vs Fusion 360 · vs FreeCAD · vs SelfCAD · vs OpenSCAD · All resources · Getting started · Video tutorials · Help center · Buy me a coffee ☕ · Contact · Open editor · Credits · Privacy · Terms