Ext Ops Panel
Open dashboard
Comparison

HTML to Figma — Design System vs io.github.themesberg/flowbite-mcp

HTML to Figma — Design System is an MCP server published by miapre. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.themesberg/flowbite-mcp is an MCP server published by themesberg. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-07. 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
MarketplaceHTML to Figma — Design Systemio.github.themesberg/flowbite-mcp
Official MCP Registry Listed
Version: 1.1.0
Downloads/month (npm): 95
Downloads/week (npm): 44
Forks (GitHub): 6
Stars (GitHub): 15
Not marked · First seen
Listed
Version: 1.1.3
Downloads/month (npm): 1 822
Downloads/week (npm): 443
Forks (GitHub): 7
Stars (GitHub): 42
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

HTML to Figma — Design System vs io.github.themesberg/flowbite-mcp
FactHTML to Figma — Design Systemio.github.themesberg/flowbite-mcp
Marketplaces that list it11
Stars (GitHub) (differs)15 (worse)42 (better)
Forks (GitHub) (differs)6 (worse)7 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (html-to-figma-design-system)On your machine (flowbite-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/miapre/html-to-figma-design-systemgithub.com/themesberg/flowbite-mcp
Changes in the last 7 days00
First seen2026-10-112026-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

HTML to Figma — Design System

In its own words, on Official MCP Registry:

Translate HTML prototypes into Figma using your design system's real components and tokens.

io.github.themesberg/flowbite-mcp

In its own words, on Official MCP Registry:

MCP server to convert Figma designs to Flowbite UI components in Tailwind CSS

How to run each

HTML to Figma — Design System As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio html-to-figma-design-system -- npx -y html-to-figma-design-system

io.github.themesberg/flowbite-mcp As a local MCP server: npm package

Claude Code
claude mcp add --env "FIGMA_ACCESS_TOKEN=<YOUR_FIGMA_ACCESS_TOKEN>" --transport stdio flowbite-mcp -- npx -y flowbite-mcp

Requires: FIGMA_ACCESS_TOKEN (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 HTML to Figma — Design System publish no settings it asks for, so we do not compare settings.

What it can do: HTML to Figma — Design System · What it can do: io.github.themesberg/flowbite-mcp · Compare two other plugins

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