pixasso vs UI Factory
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 Factory is an MCP server published by Evozim. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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 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: 1.0.0 No figure published 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 Factory |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 1 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (ui-factory-mcp.vercel.app/api/mcp) |
| Transport (differs) | Not stated | SSE |
| 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 (differs) | MIT | Not stated |
| Repository (differs) | github.com/erebuzzz/pixasso | Not stated |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-13 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 402 (2 days ago) |
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.
-
A virtual design team for Claude Code, Cursor, Windsurf, Gemini CLI, and Copilot — 18 roles, 32 commands, 11,000+ lines of expert design knowledge. Your agency's design brain…
-
Design on a canvas that Claude can read and write to — built on web standards.
-
Figma design platform integration. Access design files, extract component information, read design tokens, and translate designs into code. Bridge the gap between design and…
-
All in one skills about software design, UI/UX
-
Generates and implements design directions for product design problems. Explores alternatives, makes code changes, and wires the app so you can see results immediately.
What each says it does
pixasso
Complete end-to-end frontend engineering and design orchestrator across 16 foundational pillars.
UI Factory
Generates React components and design frameworks from visual layouts.
How to run each
pixasso
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
UI Factory As a remote MCP server
claude mcp add --transport sse ui-factory https://ui-factory-mcp.vercel.app/api/mcp --header "payment-signature: <YOUR_PAYMENT_SIGNATURE>"Requires: payment-signature header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only UI Factory has a remote endpoint we check. How we check endpoints
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 Factory · 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.