MCP server for electronic component datasheets — specs, pinouts, package data on demand. No PDFs required. Requires an API key configured via environment variable or headers as shown in examples.
bom-review | Review a bill of materials: look up each part, check stock and lifecycle, flag risks, suggest alternatives. |
datasheet-deep-dive | Deep-dive into a specific part: summarize, extract pinout, electrical specs, absolute max ratings, and application circuit. |
design-validation | Validate a design: check each component against operating conditions, flag out-of-spec parameters. |
second-source | Find second-source alternatives for a part: match package, specs, and availability across providers. |
Data the server exposes for agent context:
| Resource | Description |
|---|---|
sheetsdata://providers | List of active component data providers (JLCPCB, Mouser, DigiKey, Nexar) and their current status. |
sheetsdata://workflow | Recommended tool workflow for component selection — search, evaluate, read datasheet, validate, compare. |
Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
Add to .cursor/mcp.json in your project root:
Or use the deep link: cursor://anysphere.cursor-deeplink/mcp/install?name=SheetsData&config=...
Add to your VS Code settings.json:
Add to ~/.codeium/windsurf/mcp_config.json:
In VS Code, open Cline MCP Settings and add:
Add to Amp settings:
Add to Zed settings.json:
Add to ~/.continue/config.yaml:
For clients that only support stdio transport:
Or with the --api-key flag:
MIT