I started dabbling with the Fusion MCP a couple of months ago and found that to be a much more pleasant way to interact with it. But then I realized I was just using Fusion as a rendering engine, which was terribly overkill.
So I built Nurb.
You just describe what you want ("Make an adapter that connects my shop vac hose to the dust port on my table saw") and it asks for clarification, does web searches for part measurements/details and then generates an interactive viewer as well as optimized STL files to print.
The whole system hangs on the convention that a part is a function, and its keyword defaults are its parameters. That concept drives the CLI, the viewer’s sliders, the tests, and the agent’s interface. There’s no schema, no project file, no init step. A project is any directory with a parts/ folder.
Under the hood it’s build123d on the OCCT kernel, so parts are B-rep solids with working chamfers, fillets, and STEP export, not meshes. That also means the model already knows the API, since build123d is in every training set.
The agent can’t see, so nurb check is its eyes. Printability rules (overhangs, thin walls, slivers, stability) run against the exact solid and come back as text with coordinates, so the agent can fix what it can’t look at. The rules were calibrated by porting my real parts catalog from Fusion.
It’s source-available under FSL-1.1-MIT. Install is a one-liner on https://nurb.dev, which also sets up the necessary SKILL.md file for you.
Works great with all major LLMs!