chip-design-infrastructure vs io.github.oaslananka/easyeda-mcp-pro
chip-design-infrastructure is a plugin bundle for AI coding tools published by chuanseng-ng. Marketplaces we read that list it: 1 (Community GitHub marketplaces). io.github.oaslananka/easyeda-mcp-pro is an MCP server published by oaslananka. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-08. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  io.github.oaslananka/easyeda-mcp-pro | |
|---|---|---|
| Community marketplace hdl-tools/digital-chip-design-agents | Listed Version: 1.5.0 Forks (GitHub): 54 Stars (GitHub): 227 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.12.0 Downloads/month (npm): 6 742 Downloads/week (npm): 3 616 Forks (GitHub): 16 Stars (GitHub): 67 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 1.11.0 Downloads/month (npm): 6 742 Downloads/week (npm): 3 616 Forks (GitHub): 16 Stars (GitHub): 67 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | chip-design-infrastructure | io.github.oaslananka/easyeda-mcp-pro |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 227 (better) | 67 (worse) |
| Forks (GitHub) (differs) | 54 (better) | 16 (worse) |
| Last release (differs) | 2026-11-07 (worse) | 2026-11-08 (better) |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (easyeda-mcp-pro) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 68, secrets among them: 6 |
| Parts of the bundle (differs) | 3 | Not a bundle |
| Licence | MIT | MIT |
| Repository (differs) | github.com/hdl-tools/digital-chip-design-agents | github.com/oaslananka/easyeda-mcp-pro |
| Changes in the last 7 days (differs) | 1 | 16 |
| First seen (differs) | 2026-10-20 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
chip-design-infrastructure
EDA tool detection, output-filtering shell wrappers, MCP server config templates, and memory distillation for all chip-design domain agents
io.github.oaslananka/easyeda-mcp-pro
MCP server for EasyEDA Pro: PCB inspection, BOM, exports, and hardware review.
How to run each
chip-design-infrastructure As a Claude Code plugin
/plugin marketplace add hdl-tools/digital-chip-design-agents
/plugin install chip-design-infrastructure@digital-chip-design-agentsio.github.oaslananka/easyeda-mcp-pro As a local MCP server: npm package
claude mcp add --env "AI_API_KEY=<YOUR_AI_API_KEY>" --env "BRIDGE_TOKEN=<YOUR_BRIDGE_TOKEN>" --env "DIGIKEY_CLIENT_SECRET=<YOUR_DIGIKEY_CLIENT_SECRET>" --env "JLCPCB_CLIENT_SECRET=<YOUR_JLCPCB_CLIENT_SECRET>" --env "LCSC_API_KEY=<YOUR_LCSC_API_KEY>" --env "MOUSER_API_KEY=<YOUR_MOUSER_API_KEY>" --transport stdio easyeda-mcp-pro -- npx -y easyeda-mcp-proRequires: AI_API_KEY (secret), BRIDGE_TOKEN (secret), DIGIKEY_CLIENT_SECRET (secret), JLCPCB_CLIENT_SECRET (secret), LCSC_API_KEY (secret), MOUSER_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of chip-design-infrastructure publish no settings it asks for, so we do not compare settings.
What it can do: chip-design-infrastructure · What it can do: io.github.oaslananka/easyeda-mcp-pro · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.