skillpack.co
← All categories

UX / UI

Four lanes: (1) trust leader (Official, zero CVE, triple AI partnership), (2) enterprise write-access (Console MCP, Uber uSpec), (3) community read-only default (Framelink — ⚠️ CVE patched, use ≥v0.6.3), (4) design-in-code (Onlook — 24,918 stars, bypasses Figma entirely for Next.js+Tailwind teams). Cursor marketplace listing elevates Grab to #5.

11

Ranked

11

Signals

Verdict

Figma Official MCP is #1 — zero CVE history, triple AI platform partnership (GitHub Copilot, Claude Code, OpenAI Codex), bidirectional since Mar 6 2026. Dev Mode paywall is the main barrier but trust signal is unmatched.

Figma Console MCP is #2 — Uber Engineering Blog validates production uSpec at scale (7 stacks, accessibility in <2 min). 57+ tools, 17,356 npm/week, last push 2026-03-18. Enterprise write-access leader.

Framelink is #3 — 13.7K stars, 38.6K npm/week, Figma docs endorsed. ⚠️ CVE-2025-53967 (CVSS 7.5, RCE) patched in v0.6.3 — require ≥v0.6.3. Security press recommends migrating to Official MCP.

Onlook is #4 (new entry) — 24,918 stars, highest in category. 'Cursor for Designers' for Next.js+Tailwind teams. Bypasses Figma entirely — different lane, not a Figma MCP competitor.

Cursor Talk to Figma (Grab) is #5 — Cursor marketplace listing (alongside AWS, Stripe, Linear) is independent enterprise curation. 6,505 stars, 699 forks, free-plan compatible.

figma-use is #6 — strongest HN signal in write-access lane (115pt, 37 comments). CDP-based, 100+ commands, last push 2026-03-01.

The deeper read

The evidence demands splitting into three lanes: Lane A read-only (Framelink, Official), Lane B write-access bidirectional (Console MCP, Grab, figma-use, Claude Talk to Figma), Lane C alternative platforms (Excalidraw, Penpot). Lumping them together is misleading.

The CTO Guide comparison (Alex Bobes, Extremoo CTO) is the key independent finding: Framelink's descriptive output vs Official's prescriptive output is the real architecture split. LogRocket independently validates the same trade-off.

Uber's uSpec blog (2026-03-11) is the strongest enterprise validation in the category — automated component specs across 7 stacks, accessibility specs in under 2 minutes, all local.

Console MCP's hockey-stick npm trajectory (127/wk Nov → 17.4K/wk Mar) is the fastest growth in the category — if it sustains past Framelink's 38.6K/wk, rankings shift.

Bidirectional capability (Official Mar 6 2026) is the emerging battleground — Framelink's read-only moat erodes as bidirectional becomes table stakes.

Paper MCP, Penpot MCP, and Excalidraw MCP represent alternative platform lanes outside Figma — niche but genuinely differentiated.

Current ranking

01
Figma MCP Server GuideOfficial★ 431 62

Best for: Enterprise teams on Figma Professional/Organization with Code Connect configured

Zero CVE history. Triple AI platform partnership (GitHub Copilot, Claude Code, OpenAI Codex). Bidirectional since Mar 6 2026. 13 tools + Code Connect maps your codebase components to Figma. 14+ supported clients.

⚡ Dev Mode paywall: Free 6 calls/month (non-functional), Pro $15/seat, Code Connect requires Org $45/seat. Closed-source. Without Code Connect, Framelink produces cleaner, 25% smaller context.

02
Figma Console MCP★ 1.1K+ 59

Best for: Enterprise design automation, spec generation at scale, free-tier teams needing write access

Uber Engineering Blog: automated component specs across 7 stacks, accessibility in <2 min — strongest enterprise case study in category. 57+ tools (11 variable/token). Hockey-stick npm: 127/wk → 17,356/wk. Last push 2026-03-18.

⚡ Only one enterprise case study (Uber). Requires Figma Desktop app + local server setup. 1,097 stars — lower raw community adoption than Framelink.

03
Framelink / Figma-Context-MCP★ 14K+ 70

Best for: Individual developers and free-tier users wanting the simplest read-only Figma MCP on ≥v0.6.3

13.7K stars, 38.6K npm/week, Figma docs endorsed. CTO Guide: 25% smaller output than Official. Framework-agnostic descriptive JSON. Works on free Figma plans with broadest editor support (11+).

⚡ ⚠️ CVE-2025-53967 (CVSS 7.5, RCE) — use ≥v0.6.3 only. Security press recommends migrating to Official MCP. Read-only by design. Bus factor = 1 (solo maintainer).

04
Onlook★ 25K+ 72

Best for: Frontend teams building in Next.js + Tailwind who want designers to work directly in the codebase

24,918 stars — highest in UX/UI category. HN: 408 pts (May 2025), 227 pts (Aug 2024). 1,877 forks. 'Open-source, local-first Webflow for your own app.' Eliminates Figma-to-code translation step entirely.

⚡ No Figma integration — different workflow assumption. Tightly coupled to Next.js + Tailwind. Desktop app only (no npm). Last commit 2026-02-27 — development pace unclear.

05
Cursor Talk to Figma★ 6.5K+ 57

Best for: Cursor IDE users wanting Figma write-access without a Professional plan

Built by Grab ($12B+ market cap). Listed in Cursor's official marketplace alongside AWS, Stripe, Linear — independent enterprise curation. 6,505 stars, 699 forks. Plugin architecture bypasses API rate limits.

⚡ Local WebSocket server required — higher setup friction. Fewer tools than Console MCP (no variable/token management). Grab is primary maintainer now; community fork velocity unclear.

06
Figma-use★ 503 48

Best for: CLI-first power users wanting scriptable Figma traversal without a plugin or MCP server

Strongest HN validation in write-access lane (115pt, 37 comments). CDP-based, 100+ commands, JSX input format. Works without Figma Pro.

⚡ Solo maintainer. Development pace slowing (last push Mar 1). 185 npm/week. CDP fragility is existential if Figma blocks remote debugging.

Below the cut line
07
Claude Talk to Figma★ 516 42

Best for: Claude Code / Claude Desktop users wanting write-access on free Figma plans

Claude-specific with DXT one-click installer. 521 stars. Free Figma plan support. WebSocket-based architecture (port 3055) with Figma Plugin bridge.

⚡ Claude-only — no Cursor, VS Code, or other editor support. No HN presence, no independent reviews. Superseded by Official Figma MCP's direct Claude Code integration for most use cases.

08
Excalidraw MCPOfficial★ 3.4K+ 47

Best for: Diagramming and whiteboarding lane — AI-driven visual design outside Figma

3.4K stars, official Excalidraw org backing, community extension (1.4K stars). Clear diagramming lane leader.

⚡ Growth stalled (last push Feb 20). Diagramming lane, not design-to-code. Category scope decision needed.

09
Paper MCP

Best for: Solo devs wanting free, code-native design-to-code without Figma

HTML/CSS-native canvas — 'the design is already code' (SFAI Labs). 24 MCP tools, full bidirectional. Abduzeedo covered GPU shader capabilities.

⚡ Open alpha, no HN/Reddit signal, no enterprise evidence. Marketing-driven growth pattern.

10
Vibma★ 426 48

Best for: Design-system-forward experiments with agent guardrails

400 stars in 19 days — fastest growth rate in category. Only tool publishing model-specific design quality benchmarks. Harness engineering is novel.

⚡ Zero independent validation. Watchlist only — revisit by 2026-04-01. If HN/review coverage appears, reassess for #5-6.

11
Penpot MCPOfficial★ 225 43

Best for: Teams requiring fully open-source, self-hostable design tooling

Only open-source design platform with official MCP. Smashing Magazine coverage. Self-hostable for compliance.

⚡ Archived (merged into main repo). No npm data, no HN signal, no independent testimonials beyond Smashing.

See the full comparison.

Stars, downloads, evidence — all skills side by side.

COMPARE →

Skills comparison

GitHub stars and evidence count for top ranked skills.

GitHub Stars

Evidence items

Strong
Moderate

Head to head

FramelinkvsFigma MCP Server Guide

Framelink wins without Code Connect — 25% smaller, framework-agnostic output. Official wins with Code Connect — maps components to your codebase. CTO Guide and LogRocket independently confirm this split.

Figma Console MCPvsCursor Talk to Figma

Console MCP has Uber production evidence, 25x npm downloads, and 3x the tool surface. Grab has more stars but Console has stronger enterprise validation. Grab wins on accessibility for individual devs and free-plan users.

Figma MCP Server GuidevsFigma-use

The official path wins on trust and team adoption. Figma-use wins on direct write access and builder energy. Official is safer; Figma-use is more capable for power users.

Figma MCP Server GuidevsPaper MCP

Both offer official-lane trust. Figma MCP is the broader ecosystem play. Paper MCP is a narrower direct-write wedge outside Figma entirely. Different tools for different design surfaces.

Missing a contender?

If there's a skill we haven't ranked, submit it.

SUBMIT A SKILL →

Public signals

Enterprise production2026-03
Uber Engineering Blog: uSpec with Figma Console MCP

Strongest enterprise validation in the entire category. Publicly traded company documenting production usage — automated specs across 7 stacks, accessibility in under 2 minutes. All local — no data leaves network.

Bidirectional milestone2026-03
GitHub Blog: Figma bidirectional MCP (Mar 6 2026)

Figma Official MCP gains bidirectional capability — generate_figma_design sends rendered UI back to Figma as editable frames. Transforms Official from read-only to full design loop. Currently the ONLY option with first-party bidirectional support.

LogRocket comparison2026-03
LogRocket: Figma MCP Comparison

Independent comparison validates the simplicity-vs-depth trade-off. Confirms Framelink’s descriptive JSON vs Official’s prescriptive output. Third-party evidence supporting the lane split.

Official repo2026-03
Figma MCP Server Guide repository

The repo itself is a useful trust signal because it shows Figma treating this as a maintained, evolving workflow instead of a one-off demo.

Southleft comparison2026-03
Southleft: Figma MCP vs Figma Console MCP

Creator comparison — Official MCP is read-only window, Console MCP is full access. 57+ tools vs 14, WebSocket real-time awareness, variable management where Official has zero. Self-reported but objectively verifiable.

What changes this

Framelink loses #1 if: it remains read-only while bidirectional becomes table stakes, OR a second security incident hits without prompt patching, OR Graham Lipsman stops maintaining (bus factor = 1). Oct 2025–Jan 2026 npm decline (224K → 63K) shows it's not immune to competition.

Official overtakes Framelink if: Figma drops the Pro paywall for meaningful usage (>6 calls/month on free), OR Code Connect adoption reaches critical mass. Triple partnership gives distribution to eventually overtake — but pricing friction must drop first.

Console MCP rises to #2 if: a second major enterprise case study emerges (Uber alone is strong but single-source), OR npm growth continues hockey-stick trajectory past Framelink's 38.6K/wk.

If Grab launches enterprise features (variable management, cloud mode), it closes the gap with Console MCP and could reclaim #3.

Vibma enters ranked list if: independent HN/review validation appears within 2 weeks. At current growth rate (400 stars in 19 days), it will overtake figma-use on stars alone — but stars without independent evidence aren't sufficient.

If figma-use CDP architecture breaks permanently on Figma 126+, it drops below the cut line. Platform-dependent fragility is existential.

The entire Figma MCP category becomes less relevant if: AI-native design generation tools (Google Stitch, v0, Banani, Kombai) mature to the point where starting from a Figma file is no longer the default workflow.

If Excalidraw MCP hits 10K+ stars, it forces a category scope decision. At that scale, excluding it would be editorial malpractice.

If Paper.design exits alpha, it moves above the cut line immediately. HTML-native architecture is genuinely better for AI-first workflows.

Lane restructuring needed if: Alternative Design Platform contenders (OpenPencil, Subframe, Paper.design) collectively gain enough traction to warrant their own ranked category.