Ext Ops Panel
Open dashboard
Comparison

the-design-library vs Ensemble

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). Ensemble is an MCP server published by hearthbyte.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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

Where each is published
Marketplacethe-design-libraryEnsemble
Claude Code: claude-plugins-community Listed
Version: 2.2.0
Forks (GitHub): 0
Stars (GitHub): 10
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
Downloads/month (npm): 337
Downloads/week (npm): 337
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

the-design-library vs Ensemble
Factthe-design-libraryEnsemble
Marketplaces that list it11
Stars (GitHub) (differs)10 (better)0 (worse)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@playwright/mcp)On your machine (@hearthbyte/ensemble-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Hooks it runs (differs)2Not published
Parts of the bundle (differs)15Not a bundle
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/zeta92/design-library-plugingithub.com/mpfeifer33/ensemble-mcp
Changes in the last 7 days00
First seen (differs)2026-10-122026-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

the-design-library

In its own words, on Claude Code: claude-plugins-community:

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.

Ensemble

In its own words, on Official MCP Registry:

AI-ready design toolkit: color palettes, typography, spacing, shadows and accessibility audits.

How to run each

the-design-library As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install the-design-library@claude-community

Ensemble As a local MCP server: npm package

Claude Code
claude mcp add --env "ENSEMBLE_API_KEY=<YOUR_ENSEMBLE_API_KEY>" --transport stdio ensemble -- npx -y @hearthbyte/ensemble-mcp

Requires: ENSEMBLE_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 the-design-library publish no settings it asks for, so we do not compare settings.

What it can do: the-design-library · What it can do: Ensemble · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built