AINDF vs Ensemble
AINDF is a plugin bundle for AI coding tools published by Oleg.Design. Marketplaces we read that list it: 1 (Community GitHub marketplaces). 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
| Marketplace |  Ensemble | |
|---|---|---|
| Community marketplace 0design/ai-native-design-framework | Listed Version: 0.2.1 Forks (GitHub): 1 Stars (GitHub): 25 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
| Fact | AINDF | Ensemble |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 25 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 1 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (@hearthbyte/ensemble-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/0design/ai-native-design-framework | github.com/mpfeifer33/ensemble-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-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
AINDF
Build screens only from your design system: your agent looks up what it offers and validates every screen against it, through a local read-only MCP server.
Ensemble
AI-ready design toolkit: color palettes, typography, spacing, shadows and accessibility audits.
How to run each
AINDF As a Claude Code plugin
/plugin marketplace add 0design/ai-native-design-framework
/plugin install aindf@aindfEnsemble As a local MCP server: npm package
claude mcp add --env "ENSEMBLE_API_KEY=<YOUR_ENSEMBLE_API_KEY>" --transport stdio ensemble -- npx -y @hearthbyte/ensemble-mcpRequires: 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 AINDF publish no settings it asks for, so we do not compare settings.
What it can do: AINDF · What it can do: Ensemble · 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.