SheetsData MCP
Related Servers
Alternatives to SheetsData MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables AI assistants to search millions of electronic components and ICs, retrieve specifications, compare alternates, and submit turnkey BOM procurement requests.4MIT
- 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.11125MIT
- 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.30 npm1MIT
- FlicenseNot gradedqualityCmaintenanceEnables searching for electronic components, comparing prices across distributors, checking availability, and retrieving datasheets through the Nexar/Octopart API with specialized tools for resistors, capacitors, inductors, semiconductors, crystals, and connectors.11-
- AlicenseNot gradedqualityDmaintenanceEnables natural language search and exploration of KiCad component symbol libraries with fast full-text search across 20,000+ components including metadata like datasheets, footprints, and descriptions.MIT
- AlicenseAqualityAmaintenanceEnables AI agents to turn natural-language hardware prompts into deterministic schematics and netlists, query live LCSC parts data, validate designs, calculate trace impedance, and estimate PCBA BOM costs through stdio MCP tools and resources.202,176 PyPI1MIT
TDQS
Scored across 12 tools
Most tools have clearly distinct purposes and the descriptions explicitly state when to use one over another (e.g. search_parts vs search_datasheets, read_datasheet vs analyze_image, compare_parts vs get_part_details). The only mild overlap is within the 'component discovery' cluster (search_parts, get_part_details, compare_parts, find_alternative), but the guidance differentiates them well enough that misselection is unlikely.
Every tool follows a clean verb_noun snake_case pattern (search_parts, read_datasheet, compare_parts, find_alternative, analyze_image, check_design_fit, prefetch_datasheets, request_datasheet_upload, confirm_datasheet_upload). No camelCase or stylistic mixing; the convention is fully predictable.
12 tools is well within the ideal 3-15 range for a component-datasheet/part-data server. Each tool (search, read, compare, alternative, design-fit, image analysis, prefetch/status, two-step upload) occupies a distinct, non-redundant role.
The surface covers the core lifecycle well: discovery (search_parts/search_datasheets), drill-down (get_part_details), comparison (compare_parts), sourcing (find_alternative), validation (check_design_fit), datasheet reading/extraction, and an upload fallback path for missing datasheets. Minor gaps exist (no BOM-level assembly tool, no way to retrieve the raw PDF, no org-private-library management), but these are workable around via existing tools.