ICBOMS MCP Server
Related Servers
Alternatives to ICBOMS MCP Server
No user-submitted related servers found.
Related Servers
- 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
- 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
- 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.15147MIT
- FlicenseAqualityDmaintenanceEnables AI assistants to search JLCPCB's 450K+ electronic component catalog with real-time stock levels and pricing, supporting keyword search, filtering, and detailed component information.49-
- 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.46 npm1MIT

PCBEditor MCP Serverofficial
AlicenseNot gradedqualityCmaintenanceEnables AI assistants to turn plain-language requests into complete, routed and design-rule-checked printed circuit boards, including engineering review, part search and inventory use, and export to Gerber, KiCad, BOM and pick-and-place files.MIT
TDQS
Scored across 4 tools
Each tool serves a clearly distinct function: searching, retrieving detailed facts, comparing components, and handling procurement. There is no overlap in their purposes, so an agent can reliably choose the correct tool for a given task.
All tools share the 'icboms_' prefix and most follow a verb_noun pattern (search_components, get_product_facts, compare_parts). The exception is 'procurement_rfq', which uses a noun_noun structure, creating a minor inconsistency that still remains understandable.
With only 4 tools, the server is tightly scoped and each tool is essential to the component lifecycle (search, detail, compare, procure). This is well within the ideal range and does not feel sparse or overloaded.
The tool set covers the main workflows for electronic component sourcing: discovery, specification retrieval, comparison, and procurement. A minor gap is the lack of an explicit list or batch operation for managing BOMs, but this is not a critical absence for the stated domain.