Claude drove Fusion 360 through a chat window and built a real clock case

A clock that sets itself, and a case designed by AI

Lee Hutchinson wanted a clock that never needed setting. He built one with a Raspberry Pi, systemd timers for time sync, and some rusty Python helped along by Claude Code. So far, so normal for a maker project.

The twist came with the enclosure. Hutchinson is not a mechanical engineer and he does not enjoy Autodesk Fusion's interface. Instead of gritting his teeth and modeling the case by hand, he wired large language models into Fusion's new MCP server feature and asked them to do it.

Local model first, then Claude

He started with a local Qwen model. On the first attempt it got most of the way to a usable part but made mistakes on the rest. A second pass with Anthropic's Claude models finished the job. Hackaday's verdict: it worked, kind of, which for a first real test of LLM-driven CAD is a stronger result than many expected.

Hutchinson wrote up the full build, including the assembly headaches, over at Ars Technica.

Why this matters for makers

CAD has long been the wall that stops many would-be makers. You have an idea, then you spend a weekend learning a modeling tool just to draw a bracket. If a model can take a plain-language request and produce a printable part, that wall gets a lot lower.

The results are not yet production-grade. Hutchinson still had to fix things by hand. But the direction is clear: the gap between 'I can describe a part' and 'I have a file to print' is shrinking, and Fusion's MCP hook is one of the first mainstream signs of it.