free beta
Make PCBs with AI
Your coding agent writes SKiDL. eda-MCP turns that circuit intent into a reviewable KiCad 9 PCB, then keeps previews, routing/DRC feedback, and handoff files visible for human review.
how this works
your agent writes SKiDL, eda mcp validates the result, and the board moves through placement review, floorplanning, routing, and handoff as needed.placement review
simple boards can get to a useful preview quickly, so you can check the shape and part layout before asking for manufacturing outputs.floorplanning
medium boards can use real-size blocks derived from footprints, then a human moves those blocks in the browser and reruns the design with concrete constraints.KiCad handoff
tight routing, dense connectors, awkward mechanics, or power copper may need manual KiCad work. eda mcp should make that handoff clean.why eda-MCP
I had more PCB ideas than time to lay them out, and I particularly disliked drawing schematics. SKiDL gave agents a strong circuit-intent layer; I like it and have contributed significantly to improve generated KiCad schematics, but I do not own the project. eda-MCP is the next layer: it carries that intent into physical placement, routing, DRC feedback, previews, and handoff files.
how it works
- Describe the board. Start with a small adapter, breakout, LED board, regulator, sensor input, MOSFET switch, or simple control board.
- Write SKiDL. Your agent searches KiCad parts and captures circuit intent in Python.
- Validate first. Symbols, pins, footprints, common SKiDL mistakes, and policy issues are checked before a longer run.
- Place and route from the circuit. Connectivity, footprint geometry, DRC feedback, and EE locality rules inform the layout. For example, keep a critical decoupling capacitor close to the IC it supports.
- Add physical intent. Move real-size blocks in the hosted editor when visible placement or mechanics matter, then rerun with concrete constraints.
- Inspect and hand off. Review the preview, report, routing feedback, and files before deciding what comes next.
when to place it yourself
Use human layout intent for controls, screens, LEDs, jacks, panel connectors, mounting and alignment constraints, service bands, sensors, or separate power, analog, and digital regions. This is a strength: it keeps the agent from guessing coordinates in prose.
Move footprint-derived blocks, express locality and mechanics, then feed the constraints back into the run.
what you get back
KiCad 9 is the primary output. Depending on the run: schematic and PCB files, previews, design-review reports, routing and DRC feedback, a KiCad review zip, Gerbers and drill files when appropriate, and an EasyEDA-loadable zip.
Tight boards may still need hand tuning in KiCad. Good first boards are LED/resistor boards, sensor inputs, regulator breakouts, MOSFET switches, adapters, simple connector boards, and small control boards. Avoid RF, mains, battery-safety, dense high-current, large-panel, or failure-critical boards as first runs.
eda-MCP makes reviewable PCB artifacts; it does not approve hardware for manufacture. Before ordering, soldering, or powering anything, inspect the schematic, PCB, DRC report, critical parts, power paths, footprints, and mechanics.
a good first prompt
Start with placement review. Once the board shape, parts, connectors, and obvious layout issues look sane, move toward routing or manufacturing outputs.
first success: led + resistor
known_good Routed corpus-pass seed. Tiny, boring, and public-safe.
Caveat: routed and manufacturable in the corpus fixture, but still inspect the preview, report, and artifacts yourself. Do not order hardware from this example.
request access
Free during beta. Generated hardware requires human review before manufacture or use.
hardware safety privacy beta terms
controlled beta. personal tokens. no automatic ordering yet. generated hardware requires human review before manufacture or use.