Docs

Get started

Pick the way in that fits how you work. They all run the same engine, so a board started in one opens in the others.

1. In the browser

   Open the app and press New board, open a demo or drop a KiCad project (a .kicad_pcb, a zip or a folder). Nothing to install, no sign-up: the engine runs in the tab.

   https://app.pcbkit.io

   Open the app

2. With Claude Code

   Add the marketplace and install the plugin, then ask for a board in any folder. The project is that folder: the files are written there and git keeps the history. The agent opens the board in your browser and you watch every call.

   claude plugin marketplace add pcbkit-io/plugins
   claude plugin install pcbkit@pcbkit

3. With Codex

   The same repository is a Codex marketplace.

   codex plugin marketplace add pcbkit-io/plugins
   codex plugin add pcbkit@pcbkit

4. In Claude or ChatGPT

   Add a custom connector in the settings with this address. The board opens inside the conversation.

   https://mcp.pcbkit.io/mcp

5. In your terminal

   The pcbkit command routes, checks, renders and exports a KiCad project where it is, offline, in JSON for scripts and agents. macOS, Linux and Windows; release 2026.10.31. Then, in a board's folder:

   curl -fsSL https://pcbkit.io/install.sh | sh
   pcbkit check      # the verdict in levels
   pcbkit route      # place, route and fill
   pcbkit export     # the zip for the fab

   github.com/pcbkit-io/cli

6. In CI

   Check a KiCad repository on every push. Start with require: layout and move to ready once the parts carry order codes.

   - uses: pcbkit-io/verify@v0
     with:
       project: hardware/main-board
       require: layout

   github.com/pcbkit-io/verify

Your first board

Ask in plain words, with what matters to you: A USB-C board with an RP2040, a button and an LED that blinks every 2 seconds, as small as you can. The agent writes the design, builds it and tells you what it decided. Then try move the connector to the left edge, run the firmware or is it ready to order?

Read more

• The PCBKit language: units, nets and pins, parts, blocks, intent, the standard library and the grammar.
• The board format: what lives where in a project, footprints, rules, checks and recipes.
• Verification: the levels, what a pass says and what it does not.
• For agents: the commands, generated from the tool itself.