pixelband vs io.github.oaslananka/easyeda-mcp-pro
pixelband is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑30.
pixelband is a plugin bundle for AI coding tools published by Furqan Khan. No marketplace we read lists it any more. 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. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Community marketplace furqan-khan07/pixelband | Removed on 2026-10-30 Version: 0.5.0 Forks (GitHub): 0 Stars (GitHub): 17 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.11.2 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 | pixelbandno longer listed · | io.github.oaslananka/easyeda-mcp-pro |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 17 | 67 |
| Forks (GitHub) (differs) | 0 | 16 |
| Last release (differs) | Not published | 2026-11-08 |
| 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 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/furqan-khan07/pixelband | github.com/oaslananka/easyeda-mcp-pro |
| Changes in the last 7 days (differs) | 0 | 15 |
| First seen (differs) | 2026-10-19 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of pixelband
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Generate authentic pixel art - sprites, animations, and tilesets - from any MCP client
-
Generate, edit, style-match, turn, and animate game-ready pixel art at exact sizes.
-
Pixel art and sprite animation for agents: JSON recipes to PNG, APNG, GIF and sprite sheets.
-
Forge pixel art sprites, animations, tilesets and game assets with Google Gemini.
-
Generate pixel art sprites, animations, 8-direction rotations and palettes for games.
-
Find a tested AI image or video prompt — toy, LEGO, plushie, portrait, poster — and render it.
What each says it does
pixelband
Animated pixel-art scenes or your own image above the prompt, reacting to Claude. Zero tokens.
io.github.oaslananka/easyeda-mcp-pro
MCP server for EasyEDA Pro: PCB inspection, BOM, exports, and hardware review.
How to run each
pixelband
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
io.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-pro
Requires: 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 pixelband publish no settings it asks for, so we do not compare settings.
What it can do: pixelband · 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.