\n Sign up & connect via OAuth · \n API key (fallback) · \n Website\n
\n\n## Demo\n\n```\nAgent: read_datasheet(\"TPS54302\", section=\"pinout\")\n→ Pin table: BOOT(6), EN(5), FB(4), GND(1), SW(2), VIN(3)\n\nAgent: check_design_fit(\"TPS54302\", input_voltage=12, output_current=2)\n→ PASS — all parameters within datasheet limits\n\nAgent: \"What's the maximum SPI clock frequency for the STM32G030?\"\n→ Uses read_datasheet to find electrical specs — returns 32 MHz\n\nAgent: find_alternative(\"TPS54302\", constraints=\"in_stock\")\n→ MP2315, TPS54331 ranked by package/spec match\n```\n\nThe agent never sees a PDF. The engineer never uploads one.\n\n## Tools\n\n| Tool | Description |\n|------|-------------|\n| `search_parts` | Search for components by part number or keyword. Results merged by MPN with pricing and stock. |\n| `search_datasheets` | Semantic search across all extracted datasheets. Natural language queries like \"low-noise LDO with PSRR above 70dB\". |\n| `prefetch_datasheets` | Batch warm-up extraction for up to 20 parts. Fire-and-forget — reduces wait times. |\n| `check_extraction_status` | Poll extraction progress after prefetch or read_datasheet. |\n| `get_part_details` | Full component details — specs, parameters, pricing, and stock. |\n| `read_datasheet` | Structured datasheet sections (summary, pinout, electrical, abs_max, package) or semantic search within a datasheet. |\n| `compare_parts` | Compare 2–5 parts side by side on real datasheet specs. |\n| `check_design_fit` | Validate operating conditions against datasheet limits. PASS/FAIL/WARNING per parameter. |\n| `find_alternative` | Find alternative/substitute components by specs, package, or availability. |\n| `analyze_image` | Vision AI analysis of datasheet images — graphs, package drawings, pin diagrams. |\n| `request_datasheet_upload` | Request a signed URL to upload a datasheet PDF when we don't have one (`datasheet_status` = `no_source` or `unsupported`). Free — fee is only charged on confirm. |\n| `confirm_datasheet_upload` | 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. |\n\n## Prompts\n\nBuilt-in prompt templates that guide the agent through common hardware engineering tasks:\n\n| Prompt | Description |\n|--------|-------------|\n| `component-selection` | Walk through selecting a component: define requirements, search candidates, compare specs, validate design fit. |\n| `bom-review` | Review a bill of materials: look up each part, check stock and lifecycle, flag risks, suggest alternatives. |\n| `datasheet-deep-dive` | Deep-dive into a specific part: summarize, extract pinout, electrical specs, absolute max ratings, and application circuit. |\n| `design-validation` | Validate a design: check each component against operating conditions, flag out-of-spec parameters. |\n| `second-source` | Find second-source alternatives for a part: match package, specs, and availability across providers. |\n| `interface-check` | 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). |\n| `firmware-kickstart` | 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. |\n| `thermal-review` | Thermal and derating analysis: compare operating conditions against abs max AND recommended limits, estimate junction temperature, check SOA derating curves, flag exposed-pad requirements. |\n\n## Resources\n\nData the server exposes for agent context:\n\n| Resource | Description |\n|----------|-------------|\n| `sheetsdata://workflow` | Recommended tool workflow for component selection — search, evaluate, read datasheet, validate, compare. |\n| `sheetsdata://tips/datasheet-pitfalls` | 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. |\n| `sheetsdata://tips/design-review-checklist` | Hardware design review checklist covering power supply, signal interfaces, component selection, and firmware integration. |\n\n## Authentication — pick OAuth, fall back to API key\n\nSheetsData supports two auth paths. Use whichever works best for your client; both bill against the same org.\n\n| | **OAuth 2.0** | **API key** |\n|---|---|---|\n| Best for | Interactive MCP clients (Claude Desktop, Cursor, etc.) | CI, scripts, headless agents, or clients that don't speak MCP OAuth |\n| What you do | Click *Connect* in your client → log in here → done | Generate a key in the dashboard, paste as a `Bearer` header |\n| Setup | Just paste a URL | Paste a URL + a header |\n| Discovery | Automatic via [RFC 8414](https://datatracker.ietf.org/doc/html/rfc8414) / [RFC 9728](https://datatracker.ietf.org/doc/html/rfc9728) | n/a |\n| Spec compliance | PKCE-mandatory, dynamic client registration ([RFC 7591](https://datatracker.ietf.org/doc/html/rfc7591)), refresh-token rotation | RFC 6750 Bearer |\n| Revoke | Per-client, from `/dashboard/keys` | Delete the key |\n\n> **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.\n\n## Quickest paths (one-click install)\n\n**Claude Desktop** — download the `.mcpb` bundle from the latest [GitHub release](https://github.com/octoco-ltd/sheetsdata-mcp/releases/latest) and drag-and-drop it into the Claude Desktop window. The install dialog will surface every tool the bundle provides before confirming. Leave the API key field blank to use OAuth (recommended) — Claude Desktop will open a browser tab on first use to authorize. No JSON editing.\n\n[](https://github.com/octoco-ltd/sheetsdata-mcp/releases/latest)\n\n**Cursor** or **VS Code** — single-click install pre-fills the config and prompts to authorize on first use.\n\n[](cursor://anysphere.cursor-deeplink/mcp/install?name=SheetsData&config=eyJ1cmwiOiJodHRwczovL21jcC5zaGVldHNkYXRhLmNvbS9tY3AifQ==)\n[](vscode:mcp/install?%7B%22name%22%3A%22sheetsdata%22%2C%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A//mcp.sheetsdata.com/mcp%22%7D)\n\nFor everything else, copy the snippet from the right section below.\n\n## Install\n\n### Claude Desktop\n\n**Easiest — drag-and-drop the bundled extension.** Download the latest `sheetsdata-x.y.z.mcpb` from the [Releases page](https://github.com/octoco-ltd/sheetsdata-mcp/releases/latest) and drop the file onto the Claude Desktop window. Claude shows the list of tools the bundle provides and installs it. Leave the API key field blank to use OAuth (recommended) — a browser tab opens on first use to authorize. No JSON editing, no `npm install`.\n\n**Or — add a remote connector via the UI.** Open Claude Desktop → **Settings** → **Connectors** → **Add custom connector** at the bottom of the list.\n\n| Field | Value |\n|---|---|\n| Name | `SheetsData` |\n| URL | `https://mcp.sheetsdata.com/mcp` |\n\nClick **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.\n\n> **Note**: The `claude_desktop_config.json` file 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.\n\n