ToolBB-0123

datasheet-to-symbol-lib: Claude builds KiCad symbols from datasheet PDFs

datasheet-to-symbol-lib has Claude read a component datasheet and build a KiCad symbol library through the kipart MCP server. It first writes each pinout, including alternate pin functions, to a JSON part description that a script checks. The README reports no errors in 245 pins across three test parts, against seven in KiCad's official symbols.

Open original source github.com · Dave Vandenbout

Claimed
Why this evidence label?

The author describes it but shows no evidence we could check yet.

How we check entries
Preview image for datasheet-to-symbol-lib: Claude builds KiCad symbols from datasheet PDFs
The source's own preview image, from github.com.

Briefing

verify_jpd.py checks pin counts against the package, duplicate pin numbers, invalid KiCad pin types and supply pins not typed as power before anything is built. The MCP tools then run jpd2spd, spd2csv and kipart to write the .kicad_sym file, and a cmpparts tool diffs the result against an existing library. The README says the workflow is written for Claude Opus 5 reading datasheet pages through PDF vision, with pdfplumber as a fallback.

The comparison with KiCad's official symbols was run by Claude Code at the author's prompt. Besides the seven errors, it found the official PIC18 symbol omits 140 pin functions across 65 pins. In an earlier manual check of 20 to 30 mismatches, the author found one generated error, an extra alternate pin name WKUP1.

From the GitHub API

Repository facts

Repository facts for devbisme/datasheet-to-symbol-lib, from the GitHub API
Repositorydevbisme/datasheet-to-symbol-lib
Stars7
LanguagePython
Last push3 Sep 2026 56 d ago

Tags

Agent
Interface

Report a problem with this entry