Check your whole BOM from your AI assistant
Export your BOM, ask your assistant to check it, and in one call you get every line matched to a real part, the build priced for the number of boards you want, and a list of what will stop you from ordering. It works in Claude Code, Cursor, Codex, Windsurf, VS Code and the Claude app through the Next Everything MCP server.
What the check flags
- Out of stock, or not enough stock for your board count.
- Parts the manufacturer is phasing out: not recommended for new designs, or end of life.
- Uncertain matches, such as a value-only line or a short part number without a manufacturer, for you to confirm.
- Missing footprints, and JLCPCB extended-part fees when JLCPCB assembles the boards.
Each problem line comes with checked alternatives, and the whole build is priced across JLCPCB, DigiKey and Mouser with price breaks and minimum order quantities applied.
Which BOM files work
CSV, TSV or semicolon-separated exports from KiCad, Altium, EasyEDA/JLCPCB and hand-made spreadsheets. Columns such as Designator, Quantity, MPN, Manufacturer, Value, Footprint, LCSC Part, DigiKey and Mouser part numbers and DNP are recognised. A line needs at least a part number or a value. Excel files and schematics are not read yet: export the BOM as CSV first.
Fix it in place
Accept an alternative and your assistant swaps the line with update_bom_line; the build is priced again and you get a new quote. Every step shows on a live project page with the current BOM, prices, stock and the reason for each change. When it is right, your assistant can order it.
Try asking
- “Check bom.csv for 50 boards and fix anything that is out of stock.”
- “Which parts in this BOM are end of life or not recommended for new designs?”
- “What does this build cost for 10, 100 and 1000 boards?”
Connect your assistant
Setup takes about a minute: create a free account, copy your key and add one snippet to your client. Step-by-step guides: Claude Code · Claude Desktop · Cursor · Codex CLI · Windsurf · VS Code.