Datasheet Lens

Name: Datasheet Lens
Author: turbyho

by turbyhoversion 0.5.0i★ –iRuns on your computer

Registry nameio.github.turbyho/datasheet-lens

Install

Overview

Description from the maker (original English)

Component datasheets (PDF) for LLM agents: index, search, original pages; BOM and CAD checks

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Search & AI memory

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

PyPIPython’s uv installed (for the uvx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "datasheet-lens": {
      "command": "uvx",
      "args": [
        "datasheet-lens"
      ]
    }
  }
}

Run this in your terminal

claude mcp add datasheet-lens -- uvx datasheet-lens

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "datasheet-lens": {
      "command": "uvx",
      "args": [
        "datasheet-lens"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "datasheet-lens": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "datasheet-lens"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account turbyho, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Search & AI memoryi

More stars than 0% of the other 5679 servers in this category
Published to the registry more recently than 98% of the other 5679 servers in this category
Basic checks equal to or better than 100% of the other 5679 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Datasheet Lens safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.5.0) reached the registry today.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated yesterday

Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 21 days ago

Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated 2 months ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

datasheet-lens

datasheet-lens is a central store for the datasheets of electronic components. It keeps each datasheet one time and connects it to the projects that use it. Thus each person and each AI agent of a project uses the same correct documents.

Electronics design. The project file datasheet-lens.toml in the repository of a design holds the parts of the design and their datasheets. datasheet-lens keeps this list the same as the parts of the CAD project (KiCad and other EDA tools).
Software and firmware. The developers and their AI agents get the same datasheets as the hardware team: the same document and revision, not a copy from an unknown source.
One source for the two. The hardware design and the software can use one project file, or each a project file with the same parts. The store identifies each PDF by its SHA-256, thus the two projects use the same document.
Part selection. datasheet-lens asks the official APIs of the distributors (Mouser, DigiKey) and an optional local copy of the JLCPCB parts library. A parametric search finds new parts and replacement parts by their parameters. For each part, the tool gives the stock, the prices, the lifecycle state and the links to the datasheet, the symbol, the footprint and the 3D model. The values that the design needs come from the datasheet.

An LLM agent reads the datasheets through an MCP server. The tool does not convert a datasheet to text. A conversion makes errors that look correct: lost superscripts, merged table rows, shifted columns, wrong values from graphs. datasheet-lens builds an index to find the content, and gives the original pages and regions to the model on demand. The model reads only the parts that the work needs, and reads each value from the original.

Status: in development (version 0.4). The tools work and have tests. The interfaces can change.

Features

Drill-down into a document. An index (outline, table and figure captions, page quality), a text search, a page map with element IDs, and images of an element, a region, a caption ("Table 57", with docling also when the table continues on more pages) or a full page at 300 to 600 dpi.
Central store, shared by all projects. Each user has one store (default ~/.datasheet-lens) for all design projects. Each PDF is stored one time (SHA-256), with its index, its element map, its parts and the facts that sessions read from it. A datasheet that one project added is at once available to each other project: it is not downloaded, indexed or read again. A part can have a datasheet, a manual and errata.
Facts. A value that a session read is saved with its source (document, page, element), so that a later session finds it.
Project file. datasheet-lens.toml in the repository of a design holds the parts of the design and their documents. The team gets it with the repository. project_check compares it with the parts of the CAD project.
Distributors. The ordering codes of a datasheet, and for each orderable MPN the lifecycle state, the stock and the prices from the official APIs of Mouser and DigiKey. No scraping. distributor_status tells the services of each distributor, for example which one has a parametric search.
JLCPCB assembly. An optional local copy of the JLCPCB parts library: the JLCPCB stock for the assembly and the library class (Basic, Preferred, Extended) of each part. The tool marks a part with no stock NOT IN STOCK, and gives replacements with stock and no loading fee (the same MPN; resistors, capacitors and inductors with the same parameters). project_check compares the JLCPCB (LCSC) number of each symbol with the purchase source and with the library.
Parametric search. Find new parts and replacement parts by their parameters at DigiKey or in the JLCPCB parts library, for example "N-channel MOSFET, Vdss 20 V to 40 V, gate drive 2.5 V, package 3x3". DigiKey keeps one value of a parameter at its own conditions: the result marks a filter that its data cannot decide (RDS(on) at a gate voltage of 2.5 V) NOT APPLIED, and the agent reads that value in the datasheet. The JLCPCB library lists more points of a value, and the tool applies such a condition to them.
Take a found part. adopt takes a part of a search in one step: its datasheet (from the site of the manufacturer first), the part, and its purchase source (the source and its part number). The availability check then asks for that number.
Inbox. A PDF file that a person downloads goes into the folder _inbox of the project. sync gives it to the project parts that it agrees with.
Links to datasheets and CAD files. For each MPN, the links to the datasheet, the symbol, the footprint and the 3D model (Component Search Engine, SnapMagic, Ultra Librarian). With DigiKey, also the direct links to the models of the part. The user opens the links: datasheet-lens does not download the CAD files.
Team server (optional). One shared store for a team: the documents, parts, facts and the index and element map of each document. Each person keeps a local store that works also with no connection, and that synchronizes with the server. The server (datasheet-lens[server]) has accounts with roles and tokens, and a setup wizard installs it with PostgreSQL, the Garage object store, nginx and a Let's Encrypt certificate.

Typical uses

datasheet-lens helps to manage the input documents of a design project, and to keep them in the repository. It keeps the BOM equal to the CAD project. It lets the agent check the BOM, and check the design against the original datasheets.

Keep the datasheets of a design complete and in git, the same for each person of the team.
Compare the project with the parts of the CAD project: missing, extra and different parts.
Select the concrete orderable MPN of a base part, and make sure that it can be ordered.
Find new parts or replacement parts by their parameters, then check the candidates against their datasheets.
Get the links to the datasheet, the symbol, the footprint and the 3D model of a part.
Review a schematic against the datasheets: pins, absolute maximum ratings, logic levels, application circuits.
Compare a footprint with the package drawing of the datasheet.
Read register maps, bit fields and timing values for firmware, and keep them as facts with their source.
Use the same parts in more projects: the datasheets and the facts of one project are at once available in each other project of the same user.

datasheet-lens does not read the schematic itself. The parts come from the CAD tool, its MCP server or a BOM file. See doc/use-cases.md for the steps of each use.

Installation

datasheet-lens needs Python 3.11 or newer. It works on Linux, macOS and Windows.

pipx install datasheet-lens

datasheet-lens init

datasheet-lens init makes the central store (default ~/.datasheet-lens, or the folder in the environment variable DATASHEET_LENS_HOME). It can also install docling, which gives a better element map (tables and figures). docling is optional: it needs some GB of disk. Without it, the tool uses the text layer.

claude mcp add --scope user datasheet-lens -- datasheet-lens-mcp

For a different MCP client, set the command datasheet-lens-mcp with no arguments. The server gives its instructions to the agent. See doc/installation.md and doc/mcp-server.md.

Quick start

In the root folder of the repository of the design:

datasheet-lens project init     # the project file, and a block in AGENTS.md, CLAUDE.md

datasheet-lens add PATH|URL # add a datasheet; it proposes the MPN of the part datasheet-lens sync # copy the documents into the project folder, and give the

PDF files of datasheets/_inbox/ to their parts

datasheet-lens check BOM.csv # compare the project with a BOM of the CAD project

The agent uses the same functions through the MCP server. The block in AGENTS.md or CLAUDE.md tells the agent the procedure. project init changes only the files that exist: make one of them first if you want the block.

Command	What it does
`add PATH\	URL`	Add a document to the store and to the project
`ls`, `sync`	Show the project, or synchronize its copies
`check BOM.csv`	Compare the project with a BOM (CSV) of the CAD project, and find the changes and conflicts of the fields MPN, Value and Value_Confirmed (tested only with BOM exports of KiCad and Eagle), and the JLCPCB (LCSC) numbers
`set MPN -m NEW`	Change the MPN, base part, category or manufacturer of a project part
`rm MPN`	Remove a part (or `-d DOC`, a document) from the project
`search TEXT --part MPN`	Find a text in the documents of a part
`codes DOC`	Show the orderable codes of a datasheet
`links MPN`	Show links to the datasheet, stock, symbol, footprint and 3D model (with DigiKey: direct links)
`find MPN`	Find a part at the distributors (lifecycle, stock, prices)
`pick SOURCE CATEGORY FILTER ...`	Find parts by their parameters at `digikey` or in the `jlcpcb` library, for example `pick digikey "Single FETs, MOSFETs" "vdss >= 20 V"`
`adopt SOURCE NUMBER`	Take a found part: its datasheet, the part and its purchase source, for example `adopt jlcpcb C47616` or `adopt digikey --mpn CSD16340Q3`
`jlc update`	Download or update the JLCPCB parts library (276 MB); `jlc status`, `jlc remove`
`stock`	Show the lifecycle state and the stock of each project part (by its purchase source), and the JLCPCB replacements
`key NAME`	Save the API key of a distributor (`key mouser`, `key digikey`), or the token of the team server (`key team`)
`server connect URL`	Connect the store to a team server; `server sync`, `server` (state), `server disconnect`
`dist NAME ...`	Select the distributors (globally, or `--local` for the project)

All commands and options are in doc/cli.md.

Each user has a personal API key for each distributor. Get a free Mouser key at the Mouser API Hub (the Search API key, not the Cart API key), then run datasheet-lens key mouser. Get a free DigiKey key at developer.digikey.com. The key is a Client ID and a Client Secret of a production app. Then run datasheet-lens key digikey. If you set a distributor list before, add DigiKey to it: datasheet-lens dist mouser digikey. See doc/distributors.md.

Documentation

Document	Content
doc/installation.md	Requirements, installation, `init`, docling, store location, upgrade, uninstall
doc/use-cases.md	Typical uses, step by step
doc/mcp-server.md	MCP server: registration, instructions, all tools
doc/agent-workflow.md	How an agent reads a datasheet, with an example
doc/projects.md	Project file, layout, sync, the inbox, purchase sources, team workflow, consistency with the CAD project (also the JLCPCB numbers)

| [doc

Only the beginning is shown; read the rest in the repo

Datasheet Lens

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Search & AI memoryi

Common questions

Alternatives

Context7

Codebase Memory

Exa

README from the maker

datasheet-lens

Features

Typical uses

Installation

Quick start

PDF files of datasheets/_inbox/ to their parts

Documentation