pixasso vs UI Design to Code
pixasso is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.
pixasso is a plugin bundle for AI coding tools published by Erebuzzz. No marketplace we read lists it any more. UI Design to Code is an MCP server published by Kinglions. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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 |  UI Design to Code | |
|---|---|---|
| Community marketplace erebuzzz/pixasso | Removed on 2026-10-15 Version: 1.0.4 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.12 Downloads/month (npm): 370 Downloads/week (npm): 28 Forks (GitHub): 0 Stars (GitHub): 0 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 | pixassono longer listed · | UI Design to Code |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 1 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (ui-design-to-code-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 4 | Not a bundle |
| Licence | MIT | MIT |
| Repository (differs) | github.com/erebuzzz/pixasso | github.com/kinglions/ui-design-to-code-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-13 | 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 pixasso
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Build frontend on autopilot. Pixel-perfect Figma-to-code with autonomous refinement.
-
Web development tools including frontend design workflows
-
Multi-agent web dev pipeline — UX research and design critique around the build, plus the designer ↔ frontend contract: freeze approved mockups into a canonical oracle, port them…
-
Design-time UX and visual tooling: build and review UI/UX designs in Penpot with design systems, component patterns, and accessibility checks, and create original poster, art, and…
-
designer-skill-mcp io.github.PyModel/designer-skill-mcp
UI design MCP: design references, intent routing, anti-slop static detector and gate. No API key.
-
Jev-powered design approval loop: the agent renders, measures, judges and fixes UI until the gate approves
What each says it does
pixasso
Complete end-to-end frontend engineering and design orchestrator across 16 foundational pillars.
UI Design to Code
Design-to-code artifact pipeline for UI screenshots, Figma node data, and visual review.
How to run each
pixasso
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
UI Design to Code As a local MCP server: npm package
claude mcp add --transport stdio ui-design-to-code-mcp -- npx -y ui-design-to-code-mcpCommands 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
Neither one's marketplaces publish the settings it asks for.
What it can do: pixasso · What it can do: UI Design to Code · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.