Verified ESPHome YAML
Every bundled example is run through upstream
esphome config on each change. The output is real
ESPHome, not a plausible guess.
Design IoT devices, honestly.
wirestudio takes a single design.json and produces
deterministic ESPHome YAML, a KiCad schematic, and a bill of
materials. Same design in, same artifacts out — every time.
56components
14boards
26example designs
MCPready
What it does
CSP pin solver
Assigns legal GPIOs automatically and surfaces boot-strap, ADC2-on-WiFi, voltage, and locked-pin conflicts before you ever flash a board.
KiCad schematic export
Emits a SKiDL script that builds a .kicad_sch
from the same netlist — no LLM placing wires, fully diffable
in git.
Parametric enclosure
Generates an OpenSCAD shell from board mount-hole and port geometry, so the box fits the design you just drew.
MCP server
Drives the design tools from Claude Code or Claude Desktop over the Model Context Protocol — on your subscription, no API keys to wire up.
Fleet handoff
Pushes finished YAML to a fleet-for-esphome add-on for compile and OTA deploy with live log streaming.
One source of truth
design.json is the only state. The generators are
pure functions of that file plus the component library — no
artifact ever round-trips back into the design.
design.json
→
pure generators
→
ESPHome YAML
ASCII pinout
KiCad schematic
BOM
No LLM sits in a compile or fetch path. Chat is a thin surface over the design-editing tools only — so a design is reproducible, diffable, and cheap to regenerate.
Open source, MIT licensed
Install it, run the HTTP API, or drive it from your editor.