SheetsData docs

How to connect SheetsData to your AI tool, what each tool does, and how a datasheet gets from a manufacturer’s PDF into your agent’s answer.

Connect

SheetsData is a remote MCP server at https://mcp.sheetsdata.com/mcp. Add it to your AI tool and sign in when it asks; there’s nothing to install. For scripts and CI, or a client without MCP sign-in, use an API key.

In Claude, open Customize → Connectors, click + Add, then Add custom connector. On Team and Enterprise plans an owner adds it under Organization settings → Connectors → Add → Custom → Web.
Name it SheetsData, paste the server URL below and click Continue.
Under OAuth client, keep Use Claude's published identity (Recommended), or choose Register automatically. Click Add, then Connect, and sign in to SheetsData in the browser tab that opens.

Server URL

https://mcp.sheetsdata.com/mcp

Claude docs

The setup page in your dashboard also covers Amp, Cline, Zed and Continue. For Claude Desktop there is a one-file install: the .mcpb bundle.

Tools

Your agent chooses the tool; you don’t call them by hand. Prices are per call and the same on every plan; a plan’s included usage is spent first.

Tool	Per call	What it does	Takes
search_parts	Free	Finds parts by number or keyword across JLCPCB, Mouser and DigiKey, with stock and price from each.	query; limit (per distributor, default 20); providers: all, jlcpcb, mouser or digikey
check_extraction_status	Free	Reports how far a datasheet that is still being read has got.	part_numbers (1–20)
request_datasheet_upload	Free	Gives your agent a private link to upload a PDF we couldn't find, or one of your own.	part_number, expected_sha256, size_bytes (up to 50 MB); manufacturer (optional)
find_parts	Free	Finds parts that meet numeric specs, such as voltage, current and package.
prefetch_datasheets	Free	Starts reading up to 20 datasheets at once, so a whole BOM is ready before you ask about it.	part_numbers (1–20)
search_datasheets	2¢	Searches every datasheet we have read by meaning, such as “LDO with PSRR above 70 dB”.	query; section_type (optional, e.g. electrical_characteristics); limit (default 15)
get_part_details	Free	Returns a part's key parameters, package and datasheet status.	part_number; provider (optional); prefetch_datasheet (optional)
check_bom	2¢	Checks up to 50 BOM lines for lifecycle, stock against quantity and sourcing.
find_alternative	2¢	Suggests drop-in and functional substitutes for a part.	part_number; constraints: in_stock, same_package, jlcpcb (optional); limit (default 5)
compare_parts	2¢	Lines up two or more parts side by side on the specs that differ.	part_numbers (2–5)
read_datasheet	2¢	Returns any section of a datasheet as text and tables, or searches within one datasheet.	part_number; section (default summary) or mode: search with a query; limit for search
analyze_image	5¢	Reads values off a datasheet figure: a graph, a package drawing or a pin diagram.	part_number, image_key (from a read_datasheet image link); question (optional)
check_design_fit	5¢	Checks your operating conditions against the part's absolute maximum and recommended ratings.	part_number plus any of input_voltage, output_voltage, output_current, supply_voltage, ambient_temp, switching_frequency (kHz)
confirm_datasheet_upload	10¢	Checks an uploaded PDF, reads it and adds it to your organisation's private library.	upload_token (from request_datasheet_upload)

Examples

Find a part

search_parts({ "query": "TPS54302", "providers": "jlcpcb", "limit": 3 })

TPS54302  Texas Instruments  4.5V to 28V input, 3A, synchronous step-down
          package DDC (SOT-23-THIN, 6)  datasheet_status: ready

Read one section of a datasheet

read_datasheet({ "part_number": "TPS54302", "section": "abs_max" })

## 5.1 Absolute Maximum Ratings
|                     |      | MIN  | MAX | UNIT |
| Input voltage, VI   | VIN  | -0.3 | 30  | V    |
| Input voltage, VI   | EN   | -0.3 | 7   | V    |
| Output voltage      | SW   | -0.3 | 30  | V    |
| Operating junction temperature, TJ | | -40 | 150 | °C |

Section names come from the datasheet's own headings; start with section: "summary" to list them.

Search inside one datasheet

read_datasheet({ "part_number": "STM32F446RCT6", "mode": "search", "query": "I2C1 SCL pin" })

The passages that mention I2C1_SCL, with the pin tables around them.

Check a design against the datasheet

check_design_fit({ "part_number": "MP1584EN", "input_voltage": 28,
                  "output_current": 3, "switching_frequency": 1500 })

overall: PASS
input_voltage        28 V     PASS  "Supply Voltage VIN | 4.5V to 28V"
output_current       3 A      PASS  "providing 3A output with current mode control"
switching_frequency  1500 kHz PASS  "Programmable Switching Frequency from 100kHz to 1.5MHz"

Each check quotes the datasheet line it was judged against. An ambient temperature on its own is never reported as a clean pass; see the tool's notes on junction temperature.

How a datasheet is read

The first time anyone asks about a part we haven’t read, it goes through these steps. That usually takes 1 to 3 minutes, and a large datasheet can take 5 or more. After that it’s cached for everyone and comes back in about a second. prefetch_datasheets starts the reading early, for a whole BOM at once.

1
Find the PDF
From the distributor listings (JLCPCB, Mouser, DigiKey and Nexar), then a web search.
2
Download and check it
A PDF we've already read, byte for byte, is reused rather than read twice.
3
Convert it
Docling, on a GPU, turns pages into text and tables. PDFs with real text aren't OCR'd.
4
Read the structure
Gemini and Claude models pick out the pinout, ratings, package and a summary, and check the PDF really covers the part you asked for.
5
Index it
Sections are embedded for search, so search_datasheets can find a part by what it does.

Private parts

Datasheets for custom parts, in-house designs or anything under NDA can go into your organisation’s private library. They are read like public ones, only your team’s keys can see them, and search_parts returns them next to public results.

Through your agent, on any plan: request_datasheet_upload gives it an upload link (PDFs up to 50 MB) and confirm_datasheet_upload checks and reads the file.
From the dashboard, on Pro and Team: up to 20 PDFs at once, up to 100 MB each, with tags and notes. Go to your part library.
Your own datasheets cost 10¢ each to upload, with no storage fee.

Limits

Plan	Requests a minute	Requests a day	New datasheets a day
Free	30	500	10
Pro	100	3,000	No cap (fair use)
Team	120	5,000	No cap (fair use)
Enterprise	120+	5,000+	No cap (fair use)

Datasheets that have already been read don’t count toward the daily new-datasheet limit. Need more? Tell us what you’re building.

Billing

Free includes $2 of usage every month, with no card. It refills each month and stops, with an upgrade link, when it runs out.
Pro is $20 a month, billed to your card, and all of it is usage. Past $20 you pay list prices, up to a monthly spend cap you set.
Team is $60 a month of usage pooled across up to 10 people, invoiced monthly. Enterprise pricing and limits are agreed with you.

Prices are in US dollars; cards are charged in rand by Paystack, with 15% VAT for South African billing addresses. All the numbers are on the pricing page, and your balance and invoices are under Billing.

Troubleshooting

“Insufficient balance”: This month’s Free usage is spent. Move to Pro, or wait for next month’s refill. Finding parts keeps working.
“Rate limit exceeded”: You’ve reached your plan’s requests a minute or a day (see Limits). Wait a minute, or ask us about higher limits.
“No datasheet found” (status no_source): We looked and couldn’t find a public PDF. While we’re still looking the status is resolving, so wait for that to finish first. Then try the base part number, or upload the PDF yourself through your agent (Private parts).
“Extraction failed” or status unsupported: The PDF was damaged, encrypted or a scan without text. Upload a clean, text-based copy; your organisation’s agents will use it instead.
The datasheet is for a different part: We check every PDF against the part you asked for and set aside ones that don’t match. If one gets through, tell us at support@sheetsdata.com.
My client won’t connect: Sign in again from your client; the authorisation may have been revoked. You can see and revoke connected apps under API keys. With an API key, check it’s still active there, then restart your client after any config change.

API keys

Create keys under Dashboard → API keys. A key is shown once, when you create it.
Send it as Authorization: Bearer YOUR_API_KEY, or set SHEETSDATA_API_KEY for the @sheetsdata/mcp package.
Revoke a key there as soon as you stop using it, and keep keys out of repositories and client-side code.

Support

Email support@sheetsdata.com, use the contact form, or open an issue on GitHub. SheetsData is built by Octoco, an engineering consultancy in South Africa.