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.11140MIT
- 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.51 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.84542 PyPI1MIT
TDQS
Scored across 14 tools
The three search tools (search_parts, find_parts, search_datasheets) share the 'find parts' space, but the descriptions explicitly cross-reference each other and carve out distinct modes (part number/keyword vs parametric constraints vs semantic datasheet content), so misselection is unlikely. Lifecycle tools (prefetch_datasheets vs check_extraction_status vs read_datasheet) and the two-step upload pair are also clearly delineated. Only minor residual overlap between keyword search and functional search keeps it from a 5.
Every tool follows a consistent snake_case verb_noun pattern (search_parts, get_part_details, read_datasheet, compare_parts, check_design_fit, analyze_image, find_alternative, request/confirm_datasheet_upload). No casing or verb-style deviations appear.
14 tools sits squarely in the well-scoped range, and each maps to a distinct step in the component-research lifecycle (discover, extract, poll, read, compare, verify, source alternatives, upload). Nothing looks redundant or missing for the workflow size.
The surface covers discovery (three search modes), detail retrieval, datasheet reading and image analysis, comparison, design-fit checking, alternatives, BOM checking, the extraction lifecycle, and datasheet upload. Minor gaps exist (no explicit private-library listing/browsing or BOM export/order hand-off), but core CRUD/lifecycle operations for the domain are present.