openisd-mcp
Related Servers
Alternatives to openisd-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables 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.84138 PyPI1MIT
- AlicenseAqualityBmaintenanceProvides AI agents with instant, structured access to electronic component datasheets, pinouts, and electrical specifications without requiring PDF uploads. It enables seamless part searching, design validation, and side-by-side component comparisons across major hardware providers.1476 npm12MIT
- AlicenseAqualityDmaintenanceEnables AI agents to perform unit-aware engineering calculations with automatic unit conversion, dependency resolution, and access to 500+ units across 75+ categories through the CalcsLive calculation engine.315 npmMIT
- AlicenseAqualityBmaintenanceConnects AI assistants to a ~960,000-product electronics catalog across 955 categories, enabling keyword and parametric-filter search, stock and price lookups, substitute finding, BOM cost checking, and datasheet download/reading. Runs locally and requires no API key, membership, or fee.1141 npm31MIT

TiresVote MCPofficial
AlicenseAqualityCmaintenanceEnables agents to search a public tire catalog and professional tire test data — finding tire models, checking their known size variants, comparing 2-4 models, and collecting cited test results — through 12 read-only tools and four workflow prompts over stdio.12MIT- AlicenseNot gradedqualityCmaintenanceEnables agents to create, read, update, and validate editable analog/RF circuit schematic projects (including a five-transistor OTA template), wiring and moving components by pin name, running topology checks, exporting SVG or SPICE/Spectre netlists and normalized JSON, and opening the browser editor with a project loaded. It also exposes the component library's exact pins and defaults so drawings stay netlist-correct.MIT
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: searching, loading, designing, simulating, adding, and evaluating. There is no overlap or ambiguity in what each tool does.
Most tools follow a verb_noun pattern (e.g., search_drivers, get_driver, design_box, add_driver, evaluate_design). The single exception is 'simulate', which is a bare verb but still clear and consistent in style.
Six tools cover the core workflow of speaker design (search, load, design, simulate, add, evaluate) without bloat. Each tool earns its place and the set feels well-scoped for the server's purpose.
The surface covers the main lifecycle: discovery, loading, design creation, simulation, custom additions, and full evaluation. Minor gaps exist (e.g., no update or delete for drivers), but these are non-essential and the core domain is well covered.