프로토타입 · 미리 보기: 공식 레지스트리의 모든 서버를 담고 있으며 30분마다 동기화해요. 리뷰와 계정 기능은 다음 단계에서 열려요.
PopNx MCPAI를 쓰는 사람을 위한 MCP 서버 · 쉬운 말로 설명해요

Datasheet Lens

제작자: turbyho버전 0.4.0i★ –i내 컴퓨터에서 실행
레지스트리 이름io.github.turbyho/datasheet-lens

설치

개요

제작자가 쓴 설명(영어 원문)

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

PopNx MCP의 세 기둥

이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.

할 수 있는 일

이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.

  • 연결 방식: 내 컴퓨터에서 실행
  • 전송 방식: stdio
  • 카테고리: 검색 및 AI 기억

설치

쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.

설치하기 전에

  • 기본 점검: 1개 중 1개 통과
  • 내 컴퓨터에서 내 사용자 계정의 권한(파일, 네트워크, 앱)으로 실행돼요.
  • 레지스트리에 입력해야 할 키가 나와 있지 않아요.

필요한 것

  • PyPIPython의 uv 설치(uvx 명령어용)

어떤 앱을 쓰세요?

위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.

Claude Desktop → Settings → Developer → Edit Config를 열고 claude_desktop_config.json에 이 내용을 붙여 넣으세요

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

터미널에서 이 명령어를 실행하세요

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

Cursor에서 열기

또는 설정을 직접 복사하기

프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요

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

브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.

VS Code에서 열기

또는 설정을 직접 복사하기

프로젝트의 .vscode/mcp.json에 붙여 넣으세요

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

브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.

이 서버는 내 컴퓨터에서 실행되는데, ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요. 다른 앱을 고르세요.

선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.

이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.

할 수 있는 일

내 컴퓨터에서 실행돼요. 설치하면 AI 앱에 도구 목록이 나타나요.

기본 점검i

누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 7일 점검

  • ✓ 통과

    제작자와 저장소 일치

    레지스트리 이름이 GitHub 계정 turbyho 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요

  • … 아직 점검 안 함

    계속 관리되고 있음

    아직 GitHub에서 이 저장소를 읽어 오지 않았어요

  • … 아직 점검 안 함

    라이선스 있음

    아직 GitHub에서 이 저장소를 읽어 오지 않았어요

  • – 해당 없음

    엔드포인트 응답

    내 컴퓨터에서 실행되는 서버라 인터넷 엔드포인트가 없어요

  • – 해당 없음

    OAuth로 로그인

    내 컴퓨터에서 실행되며, 대신 로컬 설정을 사용해요

  • … 아직 점검 안 함

    도구 설명에 숨겨진 지시 없음

    내 컴퓨터에서 실행돼요. 도구 목록은 인터넷 엔드포인트가 있는 서버에서만 읽을 수 있어요

검색 및 AI 기억 카테고리의 다른 서버와 비교i

  • 이 카테고리의 다른 서버 5650개 중 0%보다 스타가 많아요
  • 이 카테고리의 다른 서버 5650개 중 99%보다 최근에 레지스트리에 공개됐어요
  • 기본 점검 결과가 이 카테고리의 다른 서버 5650개 중 100%와 같거나 더 좋아요

레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.

자주 묻는 질문

Datasheet Lens, 안전한가요?

해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.

어떤 키나 코드가 필요한가요?

레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.

내 컴퓨터에서 실행되나요, 클라우드에서 실행되나요?

내 컴퓨터에서 실행돼요. AI 앱이 필요할 때 실행하고, 데이터는 제작자의 서버를 거치지 않아요(서버 자체가 온라인 서비스를 호출하는 경우는 제외).

아직 관리되고 있나요?

GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(0.4.0)은 오늘 레지스트리에 올라왔어요.

어떤 앱에서 쓸 수 있나요?

Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. 내 컴퓨터에 Python (uv)도 있어야 해요.

대신 쓸 수 있는 건 뭐가 있나요?

같은 카테고리에는: Context7, Codebase Memory, Exa

대안

같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.

카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i

Context7

제작자: upstash

Up-to-date docs for AI agents

컴퓨터 또는 클라우드★ 64,224MIT어제 업데이트
설치

Codebase Memory

제작자: DeusData

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

내 컴퓨터에서 실행★ 48,148MIT21일 전 업데이트
설치

Exa

제작자: exa-labs

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

클라우드에서 실행★ 5,213MIT지난달 업데이트
설치

제작자의 README

README 열기

제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.

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.

Register the MCP server (stdio) in Claude Code:

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.

CommandWhat it does
`add PATH\URL`Add a document to the store and to the project
ls, syncShow the project, or synchronize its copies
check BOM.csvCompare 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 NEWChange the MPN, base part, category or manufacturer of a project part
rm MPNRemove a part (or -d DOC, a document) from the project
search TEXT --part MPNFind a text in the documents of a part
codes DOCShow the orderable codes of a datasheet
links MPNShow links to the datasheet, stock, symbol, footprint and 3D model (with DigiKey: direct links)
find MPNFind 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 NUMBERTake a found part: its datasheet, the part and its purchase source, for example adopt jlcpcb C47616 or adopt digikey --mpn CSD16340Q3
jlc updateDownload or update the JLCPCB parts library (276 MB); jlc status, jlc remove
stockShow the lifecycle state and the stock of each project part (by its purchase source), and the JLCPCB replacements
key NAMESave the API key of a distributor (key mouser, key digikey), or the token of the team server (key team)
server connect URLConnect 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

DocumentContent
doc/installation.mdRequirements, installation, init, docling, store location, upgrade, uninstall
doc/use-cases.mdTypical uses, step by step
doc/mcp-server.mdMCP server: registration, instructions, all tools
doc/agent-workflow.mdHow an agent reads a datasheet, with an example
doc/projects.mdProject file, layout, sync, the inbox, purchase sources, team workflow, consistency with the CAD project (also the JLCPCB numbers)

| [doc

앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요

PopNx에게 묻기