Open Design vs Roast My Design System
Open Design is an MCP server published by feimacode. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). Roast My Design System is an MCP server published by gregkozakiewicz. Marketplaces we read that list it: 3 (Official MCP Registry, npm registry (MCP servers), Community GitHub marketplaces). As of our marketplace pass on 2026-10-28. 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 |  Open Design |  Roast My Design System |
|---|---|---|
| Official MCP Registry | Listed Version: 0.3.0 Downloads/month (npm): 1 026 Downloads/week (npm): 244 Forks (GitHub): 3 Stars (GitHub): 15 Not marked · First seen |
Listed Version: 10.2.1 Downloads/month (npm): 12 915 Downloads/week (npm): 494 Forks (GitHub): 1 Stars (GitHub): 28 Not marked · First seen |
| npm registry (MCP servers) | Listed Version: 0.3.0 Downloads/month (npm): 1 026 Downloads/week (npm): 244 Forks (GitHub): 3 Stars (GitHub): 15 Not marked · First seen |
Listed Version: 10.2.1 Downloads/month (npm): 12 915 Downloads/week (npm): 494 Forks (GitHub): 1 Stars (GitHub): 28 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 | Open Design | Roast My Design System |
|---|---|---|
| Marketplaces that list it (differs) | 2 (worse) | 3 (better) |
| Stars (GitHub) (differs) | 15 (worse) | 51 (better) |
| Forks (GitHub) (differs) | 3 (better) | 1 (worse) |
| Last release (differs) | 2026-10-24 (better) | 2026-10-16 (worse) |
| Where it runs (differs) | On your machine (@feimacode/open-design-agent-kit-mcp) | On your machine (roast-my-design-system) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Hooks it runs (differs) | Not published | 3 |
| Parts of the bundle (differs) | Not a bundle | 6 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/feimacode/open-design-agent-kit | github.com/gregkozakiewicz/roast-my-design-system |
| Changes in the last 7 days (differs) | 2 | 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
Open Design
Design skills, design systems and artifact tools: landing pages, decks, prototypes, posters, more.
Roast My Design System
Audit your Design System and serve your Agent the rules that keep AI-written UI on-system.
How to run each
Open Design As a local MCP server: npm package
claude mcp add --env "OPEN_DESIGN_FIGMA_TOKEN=<YOUR_OPEN_DESIGN_FIGMA_TOKEN>" --transport stdio open-design -- npx -y @feimacode/open-design-agent-kit-mcpRequires: OPEN_DESIGN_FIGMA_TOKEN (secret)
Roast My Design System As a local MCP server: npm package
claude mcp add --transport stdio roast-my-design-system -- npx -y roast-my-design-system --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
The marketplaces of Roast My Design System publish no settings it asks for, so we do not compare settings.
What it can do: Open Design · What it can do: Roast My Design System · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). 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.