onsystem vs Roast My Design System
onsystem is an MCP server published by dgesteves. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). 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-26. 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 |   onsystem |  Roast My Design System |
|---|---|---|
| Official MCP Registry | Listed Version: 0.10.0 Downloads/month (npm): 1 272 Downloads/week (npm): 610 Forks (GitHub): 3 Stars (GitHub): 73 Not marked · First seen |
Listed Version: 10.2.1 Downloads/month (npm): 12 915 Downloads/week (npm): 494 Forks (GitHub): 1 Stars (GitHub): 27 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 10.2.1 Downloads/month (npm): 12 915 Downloads/week (npm): 494 Forks (GitHub): 1 Stars (GitHub): 27 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 | onsystem | Roast My Design System |
|---|---|---|
| Marketplaces that list it (differs) | 2 (worse) | 3 (better) |
| Stars (GitHub) (differs) | 73 (better) | 27 (worse) |
| Forks (GitHub) (differs) | 3 (better) | 1 (worse) |
| Last release (differs) | 2026-10-25 (better) | 2026-10-16 (worse) |
| Where it runs (differs) | On your machine (onsystem) | On your machine (roast-my-design-system) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 1 | 3 |
| Parts of the bundle (differs) | 3 | 6 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/dgesteves/onsystem | github.com/gregkozakiewicz/roast-my-design-system |
| Changes in the last 7 days (differs) | 7 | 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
onsystem
Catches palette colors, native elements and APIs your design system lacks in agent-written React.
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
onsystem As a local MCP server: npm package
claude mcp add --transport stdio onsystem -- npx -y onsystemRoast 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
Neither one's marketplaces publish the settings it asks for.
What it can do: onsystem · 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. Data comes from public marketplace files in GitHub repositories of their authors. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.