Crossprobe
Reference Part libraries

Part libraries

The parts you can place, and the parts an assistant can build a board from. KiCad's standard libraries are all there. Crossprobe adds libraries from other publishers for parts KiCad doesn't have, and credits them wherever they are used.

Updated 15 Nov 2026. 3 min read.

Library Who can use it Licence
KiCad's standard libraries Everything: the part pickers and the MCP servers CC BY-SA 4.0, with KiCad's exception for designs made with them
Seeed Studio XIAO Series Everything CC BY-SA 4.0
A project's own libraries That project Yours
A maker's files carried in a design That design Whatever the maker's is

KiCad's standard libraries

In the browser app and on the hosted MCP server, a pinned release of KiCad's symbol, footprint and 3D model libraries. On the local MCP server, the libraries of the KiCad installed on your computer.

Seeed Studio XIAO Series

Symbols and footprints for Seeed Studio's XIAO boards, to put a XIAO on a carrier board as a part: nRF52840, ESP32-C3, C5, C6 and S3, RP2040, RP2350, SAMD21, MG24, RA4M1 and others, each as a through-hole (-DIP) and a surface-mount (-SMD) footprint, plus XIAO add-on boards. The library's nickname is Seeed_Studio_XIAO_Series. Search for "XIAO" in the part picker, or ask your assistant for one.

Which symbol goes with which footprint:

Mounting Symbol Footprint
On pin headers, or soldered through the 14 edge holes XIAO-Add-On (14 pins: D0 to D10, 3V3, GND, VBUS) The board's -DIP footprint, such as XIAO-nRF52840-DIP
Soldered flat onto the carrier The board's -SMD symbol, which also has the pads under the board The -SMD footprint of the same name

Every pin of these symbols is passive, so ERC cannot tell which pins supply power. A design built through the MCP server lists the rails for you; in the editor, add a power flag to the rails the XIAO feeds or is fed from.

On boards with an antenna of their own, such as the nRF52840, the antenna is at the end away from the USB connector. Keep copper and parts clear under that end, or ask for a notch in the board there.

The licence. The library is published by Seeed Studio under CC BY-SA 4.0 (source). It asks for attribution, and for adaptations of the library to be shared under the same licence. A board built through the MCP server credits the library in a line of text on the schematic, in the build report, and in the project's library tables. Unlike KiCad's own libraries, this licence has no exception that says a design made with the library is not an adaptation of it. Whether a board that uses these footprints must itself be shared alike is yours to decide; the credit is there so that the question isn't missed.

The footprints carry warnings of their own in DRC: silkscreen drawn over their pads and small text. KiCad reports the same. A build report lists them apart from the board's own results.

A project's own libraries

A project can hold its own symbols and footprints, listed in sym-lib-table and fp-lib-table beside the project file, as in KiCad. The symbol and footprint editors write there, and parts from them come first in the pickers.

A board built through the MCP server gets the symbols and footprints it used from outside KiCad's libraries as project libraries. KiCad then opens the project anywhere without asking for a library it doesn't have.

A maker's files carried in a design

For a part that is in none of these libraries, such as a module from a small maker or a chip newer than the KiCad release, an assistant building a board can fetch the maker's own KiCad files and carry them in the design. See Build a board from requirements.

  • The files are a .kicad_sym symbol and a .kicad_mod footprint, in KiCad 6 format or later.
  • The schematic gets a line saying where they came from and under which licence. If the assistant didn't say, the line reads "licence not stated" and the report asks for it.
  • Nobody at Crossprobe has checked such files. Compare the pins and pads with the part's datasheet before you order boards.