Next Everything

npx add-mcp 'https://mcp.nexteverything.io/mcp'

Next Everything MCP

Next Everything is a remote MCP server (Streamable HTTP). Your agent calls it to turn a bill of materials into a priced, orderable build: every line matched to a part in stock, priced for the number of boards you want, problems flagged before you order, and checked alternatives for anything that is out of stock or too expensive.

Today the catalog covers electronic components: the 630,000+ in-stock parts of the JLCPCB/LCSC library, refreshed daily, with full price breaks, specs, footprint availability and pinouts. For every part in your BOM we also check DigiKey and Mouser live, so you see their prices and stock side by side, and manufacturer lifecycle warnings (not recommended for new designs, end of life). PCB, 3D-printed, CNC and sheet-metal parts are coming next.

Quickstart

1. Create a free account and copy your API key from the dashboard.
2. Add the server to your client (below). The endpoint is https://mcp.nexteverything.io/mcp.
3. From the root of your project, ask: “Use Next Everything to check my BOM for 50 boards and fix anything that is out of stock.”

Client setup

Authentication is a bearer token in the Authorization header. Replace nx_live_your_key with the key from your dashboard.

Step-by-step guides: Claude Code · Claude Desktop · Cursor · Codex CLI · Windsurf · VS Code

Projects & dashboard

Your agent works inside a project, one per build. It starts with create_project and gets a project_id and a dashboard_url. Open the link (signed in with the account that owns the API key) and you see the project live: the current BOM with the chosen part, source, price and stock for every line, the problems and suggested alternatives, every step the agent took and why, the quotes, and the orders with their payment link and tracking. The page refreshes on its own while the agent works.

Every later call that passes project_id lands in the same project: searches, BOM checks, part swaps and the order. Each response from a project includes the dashboard_url, linking straight to the BOM or the order, so your agent can hand you the link at any point. If the agent calls check_bom without a project_id, the BOM goes into the empty project it created in the last two hours, or a new project is created for it. Your projects are listed under Projects in your dashboard.

Write tools take an optional reason: one line in the agent's words (“SPH0645 is obsolete, swapped for the I2S drop-in”) that shows next to the step in the activity log.

Tools

A typical session: create_project → give you the dashboard link → check_bom → review the problems and suggested alternatives with you → update_bom_line to swap, add or remove parts → place_order with the latest quote_id. The other tools help along the way. Every tool except create_project takes an optional project_id.

create_project

Starts a project for one hardware build and returns its project_id and dashboard_url.

Param	Type	Description
name	string	Short project name, e.g. OpenPocket recorder.
description	string	Optional: what is being built.
reason	string	Optional line for the activity log.

check_bom

Matches every BOM line to an orderable part, prices the whole build for N boards (price breaks and minimum order quantities applied) across JLCPCB, DigiKey and Mouser, and flags problems: out of stock, not enough stock, parts the manufacturer is phasing out, uncertain matches, an MPN and a DigiKey/Mouser number on the same line that point to different parts, no footprint, and JLCPCB extended-part fees when JLCPCB assembles the boards. Each line shows the price comparison (offers with a minimum order far above what you need are marked and listed last). Problem lines get alternatives (checked ones first, otherwise similar parts marked unverified, plus the replacement the distributor names), and unmatched lines get similar parts or a note when the item is not an electronic component we sell (magnets, screws, wire, memory cards, printed parts). Parts sold in packs are ordered as whole packs. The result lists the shipments per distributor with estimated shipping and includes a quote_id.

Param	Type	Description
bom_csv	string	The BOM as CSV/TSV text with a header row. See Supported inputs.
boards	integer	How many boards to build. Default 1.
assembly	boolean	true when JLCPCB assembles the boards: its $3 fee per extended part counts and no-fee alternatives are suggested. Default false: parts only.
minimize_shipments	boolean	Default true: lines move to fewer distributors when the shipping saved is more than the price difference (three cheap parts are not worth a separate shipment). false = the cheapest source for every line.
project_id	string	The BOM becomes this project's current BOM. Without it, the project created just before is used, or a new one.
name	string	Name for the new project when no project_id is given.
reason	string	Optional line for the activity log.

Lines are matched in this order: LCSC part number, a DigiKey or Mouser number, the exact MPN (from the named manufacturer: the same number at another company is a different part), a family name such as WS2812B (the best-stocked variant), the closest MPN, then value and package for resistors, capacitors and inductors. A part number we do not have yet is looked up live at Mouser and DigiKey before falling back to the value, and through-hole lines (axial footprints, THT, 1/4W) stay through-hole. Anything but an exact match is flagged for you to confirm, and so is a short all-digit part number with no manufacturer. A new BOM check replaces the project's earlier quotes: only the latest quote_id can be ordered.

update_bom_line

Changes the project's current BOM without sending the whole file again: swap a line's part (for example an alternative you accepted), change its quantity, designators or pack size, add or remove a line, or change how many boards to build. The whole BOM is priced again; the result has the new quote_id, the totals and shipments, all problems, the changed line and a changed line describing the edit (verbose: true returns every line). Parts you choose this way are kept on later edits and marked “chosen by you” on the dashboard.

Param	Type	Description
project_id	string	Required. The project to change.
line	integer	Line number from lines_detail. Omit to add a new line.
part	string	New part: MPN, LCSC code, or a Mouser/DigiKey number (pins that listing).
manufacturer	string	Manufacturer of the new part, when the MPN exists at several.
qty	integer	Quantity per board. 0 = do not populate.
refdes	string	Designators, e.g. R1,R2.
pack_size	integer	Pieces in one orderable unit (5 for a 5-pack); 1 = sold per piece.
remove	boolean	Remove the line.
boards	integer	New number of boards to build.
assembly	boolean	Switch JLCPCB assembly on or off for this BOM.
minimize_shipments	boolean	Switch buying from fewer distributors on or off.
verbose	boolean	Return every BOM line, not only the changed one.
reason	string	Optional line for the activity log.

find_parts

Searches in-stock parts by part number (typos tolerated), words, category, package, manufacturer and electrical specs. A part number that is not in the catalog is looked up live at Mouser and DigiKey, like check_bom does. Values written in the query are read as specs: resistor 33 ohm 1/4W axial searches 33 Ω through-hole resistors of at least 1/4 W. Returns stock, the unit price at your quantity, key specs and footprint availability.

Param	Type	Description
query	string	An MPN, an LCSC code (C2557), a Mouser or DigiKey number, or words with values such as n-channel mosfet or 10uF ceramic capacitor 16V.
category	string	e.g. MOSFETs, LDO, Crystals.
filters	array	Spec filters, all must hold: {"param": "rds_on", "op": "<=", "value": "10mΩ"}. Values are SI numbers or text with a unit.
package	string	e.g. 0603, SOT-23. Axial, Radial or THT = any through-hole package.
manufacturer	string	Name or common abbreviation (TI, ST).
qty	integer	Quantity to price at. Default 1.
no_assembly_fee	boolean	Only JLCPCB basic/preferred parts (no $3 setup fee).
sort	enum	best_match (default), price or stock.
project_id	string	Optional: logs the search in the project.

Range specs (supply_voltage, vin, vgs_th, frequency, operating_temp) take covers (the range includes the value), <= (the whole range at or below) or >=. Your agent sees the full list of spec keys in the tool definition.

get_part

Everything about one part: all specs, every offer with its full price ladder, datasheet, pinout, footprint availability and its recent stock trend (with a warning when it keeps going out of stock).

Param	Type	Description
part	string	MPN, LCSC code, or Mouser/DigiKey number.
manufacturer	string	Only that company's part is returned: the same number at another company is a different part.
qty	integer	Quantity to price at. Default 1.
project_id	string	Optional: logs the lookup in the project.

find_alternatives

Compatible replacements, checked spec by spec: value, polarity, voltage, current, tolerance, dielectric and more, depending on the part type. Each result shows the comparison and a confidence: high when every rule was verified, medium when a spec could not be read. Parts only Mouser or DigiKey sell are checked too: their specs come from the distributor's parameters and description. Part types without rules return similar in-stock parts from the same category (with the same value for resistors, capacitors and inductors), clearly marked as unverified. When the distributor names a replacement, it is listed as distributor_suggested_replacement.

Param	Type	Description
part	string	MPN, LCSC code, or Mouser/DigiKey number of the part to replace.
qty	integer	Units needed: alternatives must have this much stock.
same_package	boolean	Keep the same package so the PCB does not change. Default true. Pin order is not compared yet: check the pinout before swapping.
no_assembly_fee	boolean	Only JLCPCB basic/preferred alternatives.
project_id	string	Optional: logs the lookup in the project.

place_order

Requests an order for a quote. Your agent always asks you first. Nothing is charged by this call: the team re-checks live stock and prices and emails you a payment link, which also shows on the project's dashboard. The order joins the project the quote belongs to, and the response links to it.

Param	Type	Description
quote_id	string	The latest one from check_bom or update_bom_line.
note	string	Anything we should know: deadline, allowed substitutions.
reason	string	Optional line for the activity log.

order_status

Status, history, payment link and shipment tracking for an order, and waiting_on: who the next step is with (the team confirming stock, you paying, the distributors shipping). Without order_id it lists your recent orders, or all orders of one project.

Param	Type	Description
order_id	string	Optional: one order.
project_id	string	Optional: list only this project's orders.

Supported inputs

check_bom reads BOM exports as CSV, TSV or semicolon-separated text: KiCad, Altium, EasyEDA/JLCPCB and hand-made spreadsheets. It recognises columns such as Designator / Reference, Quantity, MPN / Manufacturer Part Number, Manufacturer, Value / Comment, Footprint / Package, LCSC Part, Digikey / Digi-Key Part Number, Mouser / Mouser Part Number, Pack size and DNP. A Digikey or Mouser number pins that exact listing, which is the surest way to get a module or breakout board right. A line needs at least an MPN, an LCSC, DigiKey or Mouser number, or a value.

Excel files, schematics and mechanical files (STEP, STL, DXF, Gerbers) are not read yet: export the BOM as CSV and your agent passes it in.

Ordering & payment

Quotes are in US dollars and valid for 24 hours. They cover the parts at the quantity you order, with price breaks and minimum order quantities applied, and JLCPCB assembly fees only when you ask for assembly; shipping is shown as an estimate per distributor (est_shipping_usd, est_total_usd) and confirmed by the team; import duties are not included yet. Prices come from the daily catalog refresh, and the team re-checks live stock and price before sending the payment link, so you pay once and only for what can be delivered.

Limits & errors

Tool problems come back as an error result with a plain message your agent can act on, for example an unknown spec key, a quote that has expired or was replaced by a newer one, or a project_id that does not belong to your account.

Code	Meaning
401	Missing or invalid API key.
413	Request larger than 2 MB (split a very large BOM).
503	The API key could not be checked right now. Retry shortly.