szlcsc-mcp
Related Servers
Alternatives to szlcsc-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceMCP server for JLCPCB/LCSC component search, live stock and pricing, datasheets, and PCB/3D printing ordering via authenticated API.281MIT
- FlicenseAqualityBmaintenanceAn MCP server that picks JLCPCB/LCSC parts for KiCad circuits with assembly cost in mind, automating part selection, stock risk checks, and quantity-tiered pricing.81-
- AlicenseBqualityCmaintenanceEnables MCP clients to control JLCPCB EDA (嘉立创 EDA) for PCB and schematic design operations through a bridge and plugin architecture.38MIT
- AlicenseAqualityAmaintenanceMCP servers for KiCad schematic, PCB, symbol, footprint, and project automation, enabling AI-assisted electronic design via tools for read/write, analysis, and exports.1095MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server for controlling KiCad EDA software, enabling schematics, PCB design, manufacturing outputs, design checks, and library management through any MCP-compatible AI assistant.MIT
- AlicenseNot gradedqualityBmaintenanceLocal Model Context Protocol server that exposes EasyEDA Pro design capabilities as MCP tools, enabling project inspection, schematic editing, PCB design, validation, and manufacturing exports through natural language.MIT
TDQS
Scored across 25 tools
Most tools are cleanly separated by domain and action: search, parametric search, get, compare, alternatives, download, Altium import, and library management each have distinct purposes. A few adjacent pairs such as download_parts vs sync_datasheets and library_status vs library_audit require careful description reading, but the boundaries are mostly clear.
All tools share the szlcsc_ prefix and the majority follow a domain_action pattern such as get_part, library_add, and altium_import. A handful of noun-style names like eda_assets, altium_status, and healthcheck prevent the set from being fully uniform.
At 25 tools, the server sits at the upper edge of the heavy range and is larger than typical MCP servers. The count is understandable given the broad scope covering online search, artifact downloads, Altium conversion, and local library management, but it still feels slightly heavy.
The tool set covers the full workflow from online discovery and comparison to datasheet/EDA download, Altium conversion, and long-term local library management with audit and repair. The main gap is lifecycle management: parts can be added, merged, and synced, but there is no explicit tool to remove a part from the library.