SheetsData MCP
SheetsData MCP
Electronic component datasheets for AI agents — specs, pinouts, package data on demand. No PDFs required.
SheetsData is an MCP server that gives AI agents instant, structured access to electronic component data. One tool call returns the pinout. Another returns electrical specs. No PDFs. No uploads. No context window stuffing.
Beta — SheetsData is currently in public beta. APIs, pricing, and features may change. See Disclaimer below.
Demo
Agent: read_datasheet("TPS54302", section="pinout")
→ Pin table: BOOT(6), EN(5), FB(4), GND(1), SW(2), VIN(3)
Agent: check_design_fit("TPS54302", input_voltage=12, output_current=2)
→ PASS — all parameters within datasheet limits
Agent: "What's the maximum SPI clock frequency for the STM32G030?"
→ Uses read_datasheet to find electrical specs — returns 32 MHz
Agent: find_alternative("TPS54302", constraints="in_stock")
→ MP2315, TPS54331 ranked by package/spec matchThe agent never sees a PDF. The engineer never uploads one.
Related MCP server: NewSpace Market MRD
Tools
Tool | Description |
| Search for components by part number or keyword. Results merged by MPN with pricing and stock. |
| Semantic search across all extracted datasheets. Natural language queries like "low-noise LDO with PSRR above 70dB". |
| Batch warm-up extraction for up to 20 parts. Fire-and-forget — reduces wait times. |
| Poll extraction progress after prefetch or read_datasheet. |
| Full component details — specs, parameters, pricing, and stock. |
| Structured datasheet sections (summary, pinout, electrical, abs_max, package) or semantic search within a datasheet. |
| Compare 2–5 parts side by side on real datasheet specs. |
| Validate operating conditions against datasheet limits. PASS/FAIL/WARNING per parameter. |
| Find alternative/substitute components by specs, package, or availability. |
| Vision AI analysis of datasheet images — graphs, package drawings, pin diagrams. |
| Request a signed URL to upload a datasheet PDF when we don't have one ( |
| Confirm an upload: verifies SHA-256, validates PDF, checks MPN on first page, charges the upload fee, and queues extraction. Datasheets are private to your org. |
Prompts
Built-in prompt templates that guide the agent through common hardware engineering tasks:
Prompt | Description |
| Walk through selecting a component: define requirements, search candidates, compare specs, validate design fit. |
| Review a bill of materials: look up each part, check stock and lifecycle, flag risks, suggest alternatives. |
| Deep-dive into a specific part: summarize, extract pinout, electrical specs, absolute max ratings, and application circuit. |
| Validate a design: check each component against operating conditions, flag out-of-spec parameters. |
| Find second-source alternatives for a part: match package, specs, and availability across providers. |
| Check electrical and protocol compatibility between two ICs on a shared bus (SPI, I2C, UART). Verifies VOH/VOL vs VIH/VIL, flags level-shifter needs, extracts protocol config (SPI mode, I2C address, pull-up values). |
| Extract register map, init sequence, and protocol details from a peripheral IC datasheet. Generates a firmware integration guide with register writes, transaction examples, and common pitfalls. |
| Thermal and derating analysis: compare operating conditions against abs max AND recommended limits, estimate junction temperature, check SOA derating curves, flag exposed-pad requirements. |
Resources
Data the server exposes for agent context:
Resource | Description |
| Recommended tool workflow for component selection — search, evaluate, read datasheet, validate, compare. |
| The 8 most common datasheet interpretation mistakes — abs max confusion, typical vs worst-case, thermal derating, voltage levels, I2C/SPI gotchas, decoupling, exposed pads, lifecycle risks. |
| Hardware design review checklist covering power supply, signal interfaces, component selection, and firmware integration. |
Authentication — pick OAuth, fall back to API key
SheetsData supports two auth paths. Use whichever works best for your client; both bill against the same org.
OAuth 2.0 | API key | |
Best for | Interactive MCP clients (Claude Desktop, Cursor, etc.) | CI, scripts, headless agents, or clients that don't speak MCP OAuth |
What you do | Click Connect in your client → log in here → done | Generate a key in the dashboard, paste as a |
Setup | Just paste a URL | Paste a URL + a header |
Discovery | n/a | |
Spec compliance | PKCE-mandatory, dynamic client registration (RFC 7591), refresh-token rotation | RFC 6750 Bearer |
Revoke | Per-client, from | Delete the key |
Recommended: OAuth. It's a single URL paste, no copy-pasting secrets, and you can yank a connected app from the dashboard at any time.
Quickest paths (one-click install)
If you use Cursor or VS Code you can install with a single click — the editor will pre-fill the SheetsData server config and prompt you to authorize on first use.
For everything else, copy the snippet from the right section below.
Install
Claude Desktop
Open Claude Desktop → Settings → Connectors → Add custom connector at the bottom of the list.
Field | Value |
Name |
|
URL |
|
Click Add. Claude Desktop will open a browser tab to the SheetsData consent screen — pick the org to authorize, and you're done. Tools appear in Claude immediately.
Note: The
claude_desktop_config.jsonfile does not support the OAuth flow on Claude Desktop. The Connectors UI is the right path for OAuth — only fall back to the JSON config if you want to use an API key instead.
Open Claude Desktop → Settings → Developer → Edit Config, then add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"sheetsdata": {
"url": "https://mcp.sheetsdata.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}Restart Claude Desktop. Get a key from sheetsdata.com/dashboard/keys.
Claude Code
claude mcp add sheetsdata --transport http "https://mcp.sheetsdata.com/mcp"Claude Code will print a one-time OAuth URL — open it, authorize, done.
claude mcp add sheetsdata \
--transport http \
"https://mcp.sheetsdata.com/mcp" \
--header "Authorization: Bearer YOUR_API_KEY"Cursor
Click the Install in Cursor badge above, or add to .cursor/mcp.json:
{
"mcpServers": {
"sheetsdata": {
"url": "https://mcp.sheetsdata.com/mcp"
}
}
}Restart Cursor → MCP panel → SheetsData → Connect.
{
"mcpServers": {
"sheetsdata": {
"url": "https://mcp.sheetsdata.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}VS Code (GitHub Copilot)
Click the Install in VS Code badge above, or add to .vscode/mcp.json:
{
"servers": {
"sheetsdata": {
"type": "http",
"url": "https://mcp.sheetsdata.com/mcp"
}
}
}VS Code will prompt you to authorize on first use.
{
"servers": {
"sheetsdata": {
"type": "http",
"url": "https://mcp.sheetsdata.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}Windsurf
Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"sheetsdata": {
"url": "https://mcp.sheetsdata.com/mcp"
}
}
}Restart Windsurf and click Connect on the SheetsData entry.
{
"mcpServers": {
"sheetsdata": {
"url": "https://mcp.sheetsdata.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}Amp (Sourcegraph)
Add to your Amp settings:
{
"amp.mcpServers": {
"sheetsdata": {
"url": "https://mcp.sheetsdata.com/mcp"
}
}
}Amp will run the OAuth flow on first use.
{
"amp.mcpServers": {
"sheetsdata": {
"url": "https://mcp.sheetsdata.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}Cline
Cline doesn't yet support the MCP OAuth flow — use an API key.
In VS Code, open Cline → gear icon → MCP Servers:
{
"mcpServers": {
"sheetsdata": {
"url": "https://mcp.sheetsdata.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
},
"disabled": false
}
}
}Zed
Zed doesn't yet support the MCP OAuth flow — use an API key.
Add to Zed settings.json:
{
"context_servers": {
"sheetsdata": {
"settings": {
"url": "https://mcp.sheetsdata.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}
}Continue.dev
Continue doesn't yet support the MCP OAuth flow — use an API key.
Add to ~/.continue/config.yaml:
mcpServers:
- name: sheetsdata
url: https://mcp.sheetsdata.com/mcp
headers:
Authorization: "Bearer YOUR_API_KEY"npx (stdio proxy for any client)
For clients that only support stdio transport:
SHEETSDATA_API_KEY=your_key npx @sheetsdata/mcpNeed an API key?
Sign up at sheetsdata.com/signup (30 seconds, free credits)
Go to Dashboard → API Keys
Click Create key, copy the token, paste it into your config
You can also manage OAuth-authorized apps from the same page — see who has connected, when, and revoke any of them with one click.
Recommended Workflow
1. search_parts → Find candidates by keyword or part number
2. get_part_details → Evaluate pricing, stock, parameters
3. read_datasheet → Get detailed specs (pinout, electrical, package)
4. check_design_fit → Validate against your operating conditions
5. find_alternative → Find substitutes if needed
6. compare_parts → Side-by-side comparison of finalistsSupport
Email: support@octoco.ltd
Website: sheetsdata.com
Disclaimer
SheetsData is currently in public beta. Data is extracted from publicly available manufacturer datasheets using automated tools including AI. It may contain errors, omissions, or inaccuracies.
SheetsData and Octoco Ltd provide this data on an "as is" basis and make no warranties, express or implied, regarding the accuracy, completeness, or fitness for any particular purpose. Always verify critical specifications against the official manufacturer datasheet before making design, purchasing, or manufacturing decisions.
By using this service, you acknowledge that:
Extracted data may differ from the original manufacturer datasheet
SheetsData is not a substitute for reviewing official documentation
Octoco Ltd is not liable for any damages, losses, or design failures arising from the use of this data
Features, APIs, and pricing are subject to change during the beta period
For terms of use, see sheetsdata.com/terms.
License
MIT
Available Tools
14 toolsanalyze_imageAnalyze Datasheet ImageARead-onlyIdempotentInspect
Costs 5¢ per call. Reads a datasheet image with vision AI: a graph, package drawing, pin diagram or schematic that read_datasheet returned. Pass the image_key from that response (the storage path in the image URL), optionally with a question. For exact electrical values prefer read_datasheet's text tables; use this for what only the picture shows (package dimensions, pin assignments, curve trends, approximate values off a curve). Example: analyze_image(part_number='IRFZ44N', image_key='images/abc123.png', question='What is the drain current at Vgs=5V?')
Inputs: image_key (required), part_number (required), question.
check_bomCheck BOMARead-onlyIdempotentInspect
Costs 2¢ per call. Check up to 20 BOM lines for lifecycle, stock against quantity, observed single-distributor sourcing, datasheet status and stale/missing prices. Accepts MPNs or LCSC numbers; duplicate MPN quantities are aggregated. Uses exact identities, catalogue snapshots and available distributor details. Unknown remains unknown; single_source does not prove only one supplier exists. Compact columns/rows by default; verbose returns objects. No extraction.
Inputs: lines (required), verbose.
check_design_fitCheck Design FitARead-onlyInspect
Costs 5¢ per call. Checks your operating conditions against the part's absolute maximum ratings and recommended operating conditions; returns PASS / WARNING / FAIL / INSUFFICIENT_DATA per condition and overall. Conditions by part type: converters and LDOs take input_voltage, output_voltage, output_current, ambient_temp, efficiency; MOSFETs take supply_voltage (VDS), output_current (ID), ambient_temp, power_dissipation; logic ICs take supply_voltage (VCC). Verdicts:
PASS: inside the recommended range, or at or below the derated limit. By default input_voltage and supply_voltage must stay at or below 80% of the absolute-maximum rating when no recommended maximum is known (inside a recommended range is a PASS), and output_current at or below 80% of its tightest rating; derating_pct changes this. Zero headroom on a rated current always warns. This is a screening policy; derating_reference cites the reliability guidance and its limits. Each check reports margin_pct against the raw limit, derating_pct and derated_limit.
WARNING: within the limit but above the derated limit, above the recommended maximum but below the absolute maximum, or within 10% of an absolute maximum that isn't derated.
FAIL: outside the range or over the limit.
INSUFFICIENT_DATA: not safely checkable, usually an ambient_temp that could not be turned into a junction-temperature check. It never counts as a PASS. Each check has limit_type (max / min / range / fixed); checks read from the datasheet text (source='llm') carry source_quote, the row the limit came from. A condition with no limit is listed in unmatched and holds the overall verdict at WARNING. If the ratings came from a different MPN than you asked for, resolved_as and data_quality_warning lead the response. Temperature: ambient_temp is never silently compared with a junction limit. When the part's own dissipation is known, the tool estimates Tj = Ta + Pd × RθJA (RθJA from the datasheet's thermal table) and judges Tj against the junction limits, reported as 'temperature (junction est.)'. Pd by part type: LDO (Vin - Vout) × Iout; switching converter Vout × Iout × (1/η - 1), which needs efficiency; anything else, pass power_dissipation (for a MOSFET, ID² × RDS(on)). Without these the check is INSUFFICIENT_DATA and its note says what to pass. Current ratings are read at ambient_temp (a MOSFET's 25 °C drain current is derated towards its maximum junction temperature). temperature_basis says which basis was used. Stored parameters answer instantly; anything else is read from the datasheet's ratings tables (validation_method says which). A part not yet extracted starts extraction and returns status='extracting' (not charged). A datasheet nobody has read before usually takes 1-3 minutes, 5 or more for a large one or a busy queue. These are estimates, not deadlines. Not for: transient or full thermal analysis (the junction estimate is a steady-state screen), MOSFET SOA curves (analyze_image the SOA graph), passives with no ratings table. Example: check_design_fit('TPS54302', input_voltage=24, output_voltage=5, output_current=2.5, ambient_temp=70, efficiency=0.92)
Inputs: part_number (required), efficiency, ambient_temp, derating_pct, +6 more.
check_extraction_statusCheck Datasheet StatusARead-onlyIdempotentInspect
Free. Extraction status of 1-20 parts. A part being read reports current_step, elapsed_seconds, estimated_remaining_seconds with a range, and poll_after_seconds; a failed one reports its error; a part that isn't ready may list related_ready part numbers whose datasheet is readable now. A datasheet nobody has read before usually takes 1-3 minutes, 5 or more for a large one or a busy queue. These are estimates, not deadlines. A part whose PDF is still being looked for reads 'resolving'. Not final. Keep polling while the status is 'resolving', 'queued', 'pending' or 'extracting' (after poll_after_seconds); stop at 'ready', 'failed', 'no_source' or 'unsupported'. datasheet_status: 'ready' → read it; 'extracting' / 'queued' / 'pending' / 'resolving' → poll check_extraction_status; 'not_extracted' → prefetch_datasheets; 'no_source' / 'unsupported' → request_datasheet_upload. Full list in the server instructions.
Inputs: part_numbers (required).
compare_partsCompare PartsARead-onlyIdempotentInspect
Costs 2¢ per call. Compares 2-5 parts you already know side by side in one call (find candidates with search_parts or find_alternative first). Returns each part's details (per-provider specs, price breaks and links, the cached datasheet summary), a comparison table of parameters × parts built from each part's own provider data, and per-part flags: lifecycle (obsolete, NRND, last-time-buy), stock, datasheet_status, and resolved_as when a lookup landed on a different MPN. compact=true returns only the flags and the table, a much shorter answer; add include_summaries=true for the summaries. Never starts extraction: prefetch_datasheets first if you need summaries. If any input is not a real part number, the whole call is rejected with a 'rejected' map; a valid MPN no provider knows still gets a column, with an error. Example: compare_parts(['TPS54302', 'LM2596', 'MP2359']) datasheet_status: 'ready' → read it; 'extracting' / 'queued' / 'pending' / 'resolving' → poll check_extraction_status; 'not_extracted' → prefetch_datasheets; 'no_source' / 'unsupported' → request_datasheet_upload. Full list in the server instructions.
Inputs: part_numbers (required), compact, include_summaries.
confirm_datasheet_uploadConfirm Datasheet UploadADestructiveInspect
Costs 10¢ per call. That is the upload fee, charged only when the file passes its checks. Confirms an upload started with request_datasheet_upload: pass its upload_token. The server re-hashes the uploaded bytes, checks it is a PDF with the MPN on the first page, adds it to your organisation's private library and queues extraction. Success returns document_id, mpn, sha256, file_size_bytes and status='pending'; poll check_extraction_status with the MPN. A datasheet nobody has read before usually takes 1-3 minutes, 5 or more for a large one or a busy queue. These are estimates, not deadlines. Failures (not charged): 'upload_not_found' (no bytes yet; retry the PUT), 'sha256_mismatch' (re-hash and re-request), 'invalid_pdf', 'mpn_not_in_pdf' (wrong file, or scanned image-only), 'token_expired' (older than 15 minutes; start again).
Inputs: upload_token (required).
find_alternativeFind Alternative PartsARead-onlyIdempotentInspect
Costs 2¢ per call. Finds alternative and second-source parts for an MPN that is out of stock, end of life or too expensive, ranked by match_score with match_notes. Candidates come from provider search and from parts with the same function in our own datasheet index; they must do the same job (an accelerometer is not offered for a 6-axis IMU) and are compared on named electrical specs. Each has a lifecycle, stock and datasheet_status; obsolete and NRND parts rank last. Constraints: 'same_package' (fuzzy: SOT-23 ≡ SOT23, SOIC-8 ≡ SOP-8), 'in_stock', 'jlcpcb'. They are never relaxed silently: a candidate that fails one is left out of alternatives, removed_by_constraints counts what each removed, and when that leaves too few, relaxed_matches lists the best ones with the constraints they failed. When nothing matches at all, the call returns error_type 'not_found' (not charged) with the parts that would match without the constraints, under matches_without_constraints. The part's own family is also searched among datasheets already read (e.g. CH340C for CH340G). A score is similarity, not verified pin or electrical compatibility: check pinout and limits before substituting. Eval boards and modules are excluded. compact=true gives shorter rows (no per-source data or price breaks) and leaves out the reference part's summary unless include_original_summary=true. For a head-to-head of candidates you already have, use compare_parts. Example: find_alternative('TPS54302', constraints=['same_package', 'in_stock']) datasheet_status: 'ready' → read it; 'extracting' / 'queued' / 'pending' / 'resolving' → poll check_extraction_status; 'not_extracted' → prefetch_datasheets; 'no_source' / 'unsupported' → request_datasheet_upload. Full list in the server instructions.
Inputs: part_number (required), limit, compact, constraints, +1 more.
find_partsFind Parts by SpecARead-onlyIdempotentInspect
Free. Find candidates by function and numeric specs with units, package or stock. Example: query='buck converter', constraints=[{parameter:'vin_max',op:'>=',value:'24 V'}, {parameter:'iout',op:'>=',value:'2 A'}]. Also accepts vds, rds_on, canonical parameter names and text constraints (interface contains I2C). Uses catalogue/JLCPCB parameters and DigiKey parametric filters when configured. Ranks pass/fail/unknown evidence; unknown is unverified. Values retain sources and test conditions. Compact columns/rows by default; verbose returns objects. Does not validate design fit.
Inputs: query (required), limit, package, verbose, +2 more.
get_part_detailsGet Part DetailsARead-onlyInspect
Free. Full details for one part: provider specs, price, stock and lifecycle, the per-MPN structured values (specialized_specs), the cached datasheet summary, and datasheet_status with available_sections when ready. If any of it is for a different MPN than you asked for (an orderable variant, a base part, a sibling's datasheet), resolved_as and data_quality_warning at the top of the response say so, and prose written for another part is labelled as such at the start of datasheet_summary (family_summary with compact=true): trust specialized_specs for numbers. prefetch_datasheet=true starts extraction at no extra charge. Use after search_parts to drill into one result. datasheet_status: 'ready' → read it; 'extracting' / 'queued' / 'pending' / 'resolving' → poll check_extraction_status; 'not_extracted' → prefetch_datasheets; 'no_source' / 'unsupported' → request_datasheet_upload. Full list in the server instructions.
Inputs: part_number (required), compact, verbose, provider, +1 more.
prefetch_datasheetsPrefetch DatasheetsARead-onlyInspect
Free. Starts background extraction for up to 20 parts at once, e.g. a BOM, so they are ready before you read them. Returns immediately with each part's status. A datasheet nobody has read before usually takes 1-3 minutes, 5 or more for a large one or a busy queue. These are estimates, not deadlines. Poll check_extraction_status (free). A part without a known datasheet comes back 'queued' while we look for its PDF, and reads 'resolving' until the search ends; only then is 'no_source' final: check the part number, or attach the PDF with request_datasheet_upload (org-private). The Free plan has a daily cap on new datasheets ('trial_limit'). MPNs or LCSC numbers only; resolve value-only BOM rows with search_parts first. Example: prefetch_datasheets(['TPS54302', 'ADS1115', 'LP5907']) datasheet_status: 'ready' → read it; 'extracting' / 'queued' / 'pending' / 'resolving' → poll check_extraction_status; 'not_extracted' → prefetch_datasheets; 'no_source' / 'unsupported' → request_datasheet_upload. Full list in the server instructions.
Inputs: part_numbers (required).
read_datasheetRead DatasheetARead-onlyInspect
Costs 2¢ per call. Reads a part's datasheet. Section mode (default): start with section='summary' for an overview and available_sections, then ask for any section by name; names come from the datasheet's own headings (e.g. 'register_map', 'i2c_interface'); an unknown name returns the nearest section names and pages. Use max_chars and the returned next_offset to continue a long read. Search mode (mode='search' with a query): semantic search within this datasheet, for targeted questions such as a register bit field or an I2C address. Prefer specific sections to section='all', which can fill your context. The first read of a new part starts extraction and returns status='extracting' (not charged). A datasheet nobody has read before usually takes 1-3 minutes, 5 or more for a large one or a busy queue. These are estimates, not deadlines. For microcontrollers, register-level programming detail usually lives in a separate reference manual, not the datasheet; available_sections shows what is present. datasheet_status: 'ready' → read it; 'extracting' / 'queued' / 'pending' / 'resolving' → poll check_extraction_status; 'not_extracted' → prefetch_datasheets; 'no_source' / 'unsupported' → request_datasheet_upload. Full list in the server instructions.
Inputs: part_number (required), mode, limit, query, +3 more.
request_datasheet_uploadRequest Datasheet UploadAInspect
Free. The upload fee is charged by confirm_datasheet_upload, after the file is checked. Gives a signed URL to upload a datasheet PDF we don't have: use it when datasheet_status is 'no_source' (once the search has finished: not while it is 'resolving') or 'unsupported'. Three steps:
Call this with the MPN, the file's SHA-256 and its byte size; you get upload_url, upload_method ('PUT'), upload_headers and an upload_token.
Upload the bytes:
curl -X PUT -H 'Content-Type: application/pdf' --data-binary @file.pdf "$UPLOAD_URL"(plus any upload_headers).Call confirm_datasheet_upload with the upload_token. Checked at confirm (nothing charged if a check fails): a parseable PDF, the SHA-256 and size you declared, and the MPN or its stem on the first page (scanned image-only PDFs fail this). Max 50 MB; the part's datasheet, not a dev-kit manual, schematic or app note. Uploaded datasheets are private to your organisation. Tokens expire after 15 minutes; request a new one if needed.
Inputs: size_bytes (required), part_number (required), expected_sha256 (required), manufacturer.
search_datasheetsSearch DatasheetsARead-onlyIdempotentInspect
Costs 2¢ per call. Semantic search across every datasheet already extracted (not every part that exists), for spec-based discovery such as 'low-noise LDO with PSRR above 70dB'. Returns matching chunks with part_number and a 0-100 relevance_score. To find a specific part by number, use search_parts.
Inputs: query (required), limit, section_type.
search_partsSearch PartsARead-onlyIdempotentInspect
Free. Start here. Searches components by part number or keyword (e.g. 'STM32F103', 'buck converter 3A') across JLCPCB, Mouser and DigiKey in parallel. Results are merged by MPN with indicative price and stock per source and a datasheet_status. For an MPN query, eval boards and dev kits come back separately as related_kits. Parts in your organisation's private library whose MPN, manufacturer, description, type, category or tag matches are appended with source='private_library' and their tags. For spec-based discovery in plain language, use search_datasheets. datasheet_status: 'ready' → read it; 'extracting' / 'queued' / 'pending' / 'resolving' → poll check_extraction_status; 'not_extracted' → prefetch_datasheets; 'no_source' / 'unsupported' → request_datasheet_upload. Full list in the server instructions.
Inputs: query (required), limit, providers.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 14 tools
The three search tools (search_parts, find_parts, search_datasheets) share the 'find parts' space, but the descriptions explicitly cross-reference each other and carve out distinct modes (part number/keyword vs parametric constraints vs semantic datasheet content), so misselection is unlikely. Lifecycle tools (prefetch_datasheets vs check_extraction_status vs read_datasheet) and the two-step upload pair are also clearly delineated. Only minor residual overlap between keyword search and functional search keeps it from a 5.
Every tool follows a consistent snake_case verb_noun pattern (search_parts, get_part_details, read_datasheet, compare_parts, check_design_fit, analyze_image, find_alternative, request/confirm_datasheet_upload). No casing or verb-style deviations appear.
14 tools sits squarely in the well-scoped range, and each maps to a distinct step in the component-research lifecycle (discover, extract, poll, read, compare, verify, source alternatives, upload). Nothing looks redundant or missing for the workflow size.
The surface covers discovery (three search modes), detail retrieval, datasheet reading and image analysis, comparison, design-fit checking, alternatives, BOM checking, the extraction lifecycle, and datasheet upload. Minor gaps exist (no explicit private-library listing/browsing or BOM export/order hand-off), but core CRUD/lifecycle operations for the domain are present.
Maintenance
Related MCP Connectors
Turn datasheets into source-backed JSON contracts, pinout matrices, and KiCad CAD for AI agents.
Search real parts with datasheet-provenance specs, check compatibility and compose priced BOMs.
IC datasheet search: parametric part finding, spec lookup, price comparison — grounded in real PDFs.
Structured, cited, real-world data from 300+ sources and the open web for your AI agents.
Related MCP Servers
- AlicenseAqualityAmaintenanceEnables searching and filtering over 1.5 million electronic components across JLCPCB, Mouser, and DigiKey using parametric queries and smart parsing. It supports finding alternative parts, accessing pinout data, and downloading KiCad footprints directly through AI coding assistants.17150MIT
- AlicenseNot gradedqualityBmaintenanceSpacecraft component specifications read from vendor datasheets (2,500+ products, 24 categories): search by engineering requirements, compare, budget mass and power, read datasheet digests and facts, find data gaps, and assemble a bus around parts you lock. Every value cites its datasheet page; missing data is named, never guessed.46 npm1MIT
- AlicenseAqualityCmaintenanceEnables AI assistants to search millions of electronic components and ICs, retrieve specifications, compare alternates, and submit turnkey BOM procurement requests.4MIT
- AlicenseAqualityBmaintenanceConnects AI assistants to a ~960,000-product electronics catalog across 955 categories, enabling keyword and parametric-filter search, stock and price lookups, substitute finding, BOM cost checking, and datasheet download/reading. Runs locally and requires no API key, membership, or fee.1141 npm31MIT