HTML to Figma — Design System MCP server
io.github.miapre/html-to-figma-design-system·v1.1.0·13 starsTranslate HTML prototypes into Figma using your design system's real components and tokens.
13 stars24 downloads/wk
Reviews
Write oneNobody has reviewed HTML to Figma — Design System yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
HTML to Figma — Design System tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it
- Code scan8 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 9 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How HTML to Figma — Design System compares
Against every graded Media MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 92/100
- higher than 88% of 1,336 Media servers
- GitHub stars
- 13
- more than 89% of 716 Media servers
- Downloads a week
- 24
- more than 10% of 372 Media servers with a package
Install HTML to Figma — Design System in Claude Code, Cursor or VS Code
Runs npx -y html-to-figma-design-system on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add html-to-figma-design-system -- npx -y html-to-figma-design-system
What the publisher says
From the HTML to Figma — Design System repository's README, as published. We do not edit it. Read it on GitHub
Mimic AI
Transforms HTML into Figma using only your design system, enforcing correct component usage and falling back safely when needed, while improving accuracy with every build.
Open-source MCP server. Runs locally. Your design data never leaves your machine.
Gated, not steered
AI writing into Figma isn't the hard part anymore; several tools do it now. The differences show up in what happens when the AI reaches for something your design system doesn't have. A tool that steers an agent toward your components can still land on a raw hex value, a raw pixel size, or a font your system doesn't use, and general guidance for that category of tool is that the result may need manual review and cleanup before it's usable. Mimic enforces at write time, inside the Figma plugin itself, not just in the prompt.
What the gate blocks
- Raw hex/rgb fills where a DS color variable exists
- Raw pixel font sizes where a DS text style exists
- Fonts outside the design system
- Variable category mismatches (e.g. a background token used as a stroke)
- Primitive frames for elements the DS already has as components (buttons, badges, inputs, table cells, and more)
If the DS genuinely has no equivalent, Mimic says so in the build report instead of quietly leaving a raw value in place.
What the learning accumulates
- Component recipes, replayed automatically once confirmed across builds
- Majority-wins variant defaults, learned from your own usage patterns
- Design rules you set once by correcting a build, enforced on every one after
- No-good compilation: patterns tried and confirmed not to work, so they aren't retried
- Staleness detection: flags a stored recipe the moment it stops matching your current DS
- All scoped per design system library: nothing bleeds across unrelated files
Nothing else accumulates this across builds. A hand-authored Figma Agent Skill is static text; it doesn't learn from what you correct.
What the report proves Every build ends in a compliance-audited report: components used and their keys, primitives built and why, which stored rules were checked and whether they held, and where the DS still has coverage gaps. It's built to be shown to a stakeholder, not just read by the person who ran the build.
Why Mimic exists
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
HTML to Figma — Design System: common questions
- Is HTML to Figma — Design System MCP server safe?
- Yes, by our scan: it is graded A (92/100). Read the HTML to Figma — Design System safety report
- How do I install HTML to Figma — Design System?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does HTML to Figma — Design System need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is HTML to Figma — Design System maintained?
- The last commit was 48 days ago (2026-09-18). The latest release is v1.1.0.
- What can I use instead of HTML to Figma — Design System?
- Servers from other publishers that do the same job: Dembrandt MCP server, melta UI MCP server and Buoy MCP server. Compare all HTML to Figma — Design System alternatives.
- How does HTML to Figma — Design System compare with other Media MCP servers?
- safety score 92/100 (higher than 88% of 1,336 Media servers); github stars 13 (more than 89% of 716 Media servers); downloads a week 24 (more than 10% of 372 Media servers with a package). Full comparison.
Alternatives to HTML to Figma — Design System
Same job from other publishers: the closest match first, then the best rated.
- DembrandtDesign tokens from any live site: colours, type, spacing, components, drift against a baseline.not reviewedWidely usedB
- melta UIAI-Ready design system MCP: melta UI tokens, component contracts, 107 rules, check_html self-verifynot reviewedEstablishedA
- BuoyThe design system your coding agents check before they ship: tokens plus exact UI fixes.not reviewedGrowingA
Mlola UIMlola UI components, tokens and design rules for coding agents, with a markup checkernot reviewedGrowingA- WunderUIThe WunderUI design system for coding agents: components, props, tokens, rules and skills.not reviewedGrowingB