the-design-library vs Supericons
the-design-library is a plugin bundle for AI coding tools published by zeta92. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Supericons is an MCP server published by curlymolelabs. Marketplaces we read that list it: 2 (Official MCP Registry, Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-19. 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 | ||
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 2.2.0 Forks (GitHub): 0 Stars (GitHub): 10 Not marked · First seen |
Listed Version: 2.0.0 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
| Official MCP Registry | Not listed | Listed Version: 0.4.22 Downloads/month (npm): 2 620 Downloads/week (npm): 702 Forks (GitHub): 0 Stars (GitHub): 1 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 | the-design-library | Supericons |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 10 (better) | 1 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@playwright/mcp) | Remote server or your machine |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 2 | Not published |
| Parts of the bundle (differs) | 15 | 2 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/zeta92/design-library-plugin | github.com/curlymolelabs/supericons |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen (differs) | 2026-10-12 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 3 days ago |
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
the-design-library
A full design suite for Claude Code: 58 brand design systems (Stripe, Linear, Vercel, Google, Anthropic and more) + 5 curated skills for UI/UX generation, accessibility auditing, motion design, web guidelines, and the full design lifecycle. Auto-activates relevant skills based on your project type.
Supericons
Multilingual semantic SVG icon search with previews for AI coding agents. 20,000+ icons.
How to run each
the-design-library As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install the-design-library@claude-community
Supericons As a remote MCP server
claude mcp add --transport http supericons https://mcp.supericons.dev/mcp
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Supericons 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: the-design-library · What it can do: Supericons · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.