Design
sheetsdata.com
Provides electronic component search, BOM validation, design-fit checks, and datasheet upload confirmation for hardware design workflows.
ENDPOINT 1
https://mcp.sheetsdata.com/mcp
MCP server metadata
- Name
- sheetsdata
- Version
- 1.0.5
SheetsData gives you instant access to electronic component data — specs, pinouts, package info, and more — extracted from manufacturer datasheets. No PDFs needed. ## Workflow 1. `search_parts` to find candidates by keyword or part number 2. `get_part_details` or `compare_parts` to evaluate options 3. `read_datasheet` for detailed specs (pinout, electrical, package, etc.) 4. `check_design_fit` to validate against design constraints 5. `read_datasheet` with mode='search' for any remaining questions about a specific part 6. `analyze_image` when you need data from a graph, package drawing, or pin diagram ## Tips - Use manufacturer part numbers (MPNs) like "TPS54302" or LCSC numbers like "C2837938". - `search_datasheets` is best for broad spec-based discovery across all parts (e.g. "low-noise LDO with PSRR above 70dB"). - `read_datasheet` with section="all" returns all sections at once. - 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. Start it early with `prefetch_datasheets`. Poll check_extraction_status (free) after poll_after_seconds (15-60 s); datasheets already read answer in about a second. - When a response carries `resolved_as` / `data_quality_warning`, the data is for a different MPN than you asked for; say so and confirm before relying on it. - When `read_datasheet` returns sections with images, use `analyze_image` to extract data from graphs, package drawings, pin diagrams, or schematics. Pass the image_key from the image URL. ## Prices Charged to your organisation per call: check_extraction_status, find_parts, get_part_details, prefetch_datasheets, request_datasheet_upload and search_parts are free; check_bom 2¢, compare_parts 2¢, find_alternative 2¢, read_datasheet 2¢, search_datasheets 2¢, analyze_image 5¢, check_design_fit 5¢ and confirm_datasheet_upload 10¢ per call. Each tool description starts with its price. A call that fails, or that returns status 'extracting', is not charged. ## datasheet_status values - 'ready': extracted and indexed; use read_datasheet, search_datasheets or analyze_image. - 'extracting' / 'in_progress' / 'queued' / 'pending': extraction running or scheduled. 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) after poll_after_seconds (15-60 s); datasheets already read answer in about a second. Stop at 'ready' or 'failed'. A response that says 'extracting' is not charged. - 'resolving': we are still looking for the datasheet's PDF (distributors, then a web search; under a minute a part, longer for a big batch). Not final: keep polling check_extraction_status. - 'not_extracted': known part, datasheet not fetched yet. Start it with prefetch_datasheets (up to 20 parts, free) or read_datasheet (starts on first read). If the response lists related_ready part numbers, their datasheet is readable now; check it covers your part. - 'no_source': the search for a public datasheet has finished and found none for this MPN. Check the part number (search_parts), or retry prefetch_datasheets later. Otherwise upload the PDF with request_datasheet_upload + confirm_datasheet_upload (private to your organisation). - 'unsupported': the PDF can't be extracted (scanned image-only, encrypted or corrupt). Upload a text-based PDF with request_datasheet_upload. - 'failed' / 'error': extraction errored; the response carries the reason. Retry with prefetch_datasheets or contact support. - 'rejected': the input wasn't a real MPN (a value like '100nF', a description or a reference designator). Fix the input. - 'deduplicated': another part in the family has the same datasheet; its content is served under that part's MPN. - 'trial_limit': the Free plan's daily allowance of new datasheets is used up; datasheets already read stay available. ## Important: valid part numbers - Always pass specific manufacturer part numbers (MPNs), not bare values or descriptions. - Valid: "STM32F446RCT6", "TPS54302DDCR", "GRM155R71C104KA88D", "C2837938" - NOT valid: "100nF", "10K", "4.7uF", "0603 resistor", "LED red", "R1", "C5", "U3" - Bare component values (100nF, 10K, 300ohm) are NOT part numbers — they will waste extraction resources and return wrong results. Use `search_parts` first to find the MPN. - BOM reference designators (R1, C5, U3) are circuit labels, not part numbers. - Test points (TP1, TP_GPIO_1), fiducials (FID1), mounting holes (MH1), and other mechanical BOM items are PCB features, not components — never pass these. - Do NOT concatenate MPNs with LCSC numbers (e.g. "SMAJ24A-C148222"). Pass the MPN ("SMAJ24A") or LCSC number ("C148222") separately. - Board/module names (e.g. "CM5IO_ComputeModule5") are not MPNs. - When processing a BOM, skip rows that only have values/descriptions and no MPN column. Also skip test points, fiducials, mounting holes, and other non-component items. ## Important: managing context size - Prefer requesting specific sections from `read_datasheet` (e.g. "summary", "pinout", "electrical") rather than "all". The "all" option returns the entire datasheet and can easily fill your context window. - Start with "summary" to get an overview, then fetch specific sections as needed.
Known tools 14
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.sheetsdata]
url = "https://mcp.sheetsdata.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"sheetsdata": {
"type": "http",
"url": "https://mcp.sheetsdata.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: sheetsdata
Remote MCP URL: https://mcp.sheetsdata.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"sheetsdata": {
"url": "https://mcp.sheetsdata.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"sheetsdata": {
"type": "http",
"url": "https://mcp.sheetsdata.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "sheetsdata",
"transport": "streamable-http",
"url": "https://mcp.sheetsdata.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.