WireStudio gives AI agents a path from enclosure design to a 3D-print queue
Version 0.40.0 connects its ESPHome design workflow to print-warden and writes KiCad 8 schematics directly; the printer's own start policy still decides when a job runs.
WireStudio 0.40.0 lets an MCP-connected AI client turn a generated electronics enclosure into a queued 3D-print job. Its October 18 release adds a Print tab and tools to inspect print-warden, submit an enclosure and check the resulting job. It is a concrete bridge from the application’s ESPHome device-design workflow to a printer service, rather than a claim that a chatbot has independently manufactured a working device.
The design reaches the queue; start policy stays with the printer
WireStudio generates an OpenSCAD shell and uploads the .scad file to print-warden. Wall thickness, clearance and standoff adjustments travel as OpenSCAD overrides so the warden can render and slice the submitted design. Operators configure PRINT_WARDEN_URL and a token when the warden requires one.
WireStudio does not call a print-start operation. The warden can offer the job to an operator’s phone or start it under its configured auto_start policy. Consequently, the integration is neither a promise of fully autonomous fabrication nor a guarantee that every print always requires a manual tap.
The same release adds direct, deterministic KiCad 8 schematic output and connector pins that can join other components’ nets. It also fixes previously unconnected board pins for supported ESP32-WROOM-32, ESP-12E and WeMos D1 mini symbols. Boards represented by generic headers still lack that pin mapping and remain floating with a warning, according to the release notes. Schematic generation needs the server’s KiCad symbol libraries; rendering and electrical checks use kicad-cli.
Claude can be the client or the embedded model
WireStudio is a standalone, MIT-licensed application, not a new model or an ESPHome-affiliated product. Its embedded Claude sidebar requires an Anthropic API key. Alternatively, Claude Code or another compatible MCP host can drive the server through a bearer-authenticated connection, with model usage billed under the client’s account rather than a second embedded-agent API call.
The tagged MCP guide documents installing from a repository checkout with pip install -e . and starting python -m wirestudio.api; package metadata requires Python 3.11 or later. The Docker quickstart still names 0.35.0, so that example alone does not establish an installation of the newly reported 0.40.0 features.
The service can save and modify designs and, when configured, reach hardware integrations. MCP has its own token; the separate REST interface needs WIRESTUDIO_API_TOKEN before exposure beyond a private network, the deployment guide says. Printer, server and model costs depend on the user’s setup. The maintainer documents the features and checks; AITrending has not run a physical print or independently validated the resulting circuitry.
