figwright

Where Playwright drives the browser, Figwright drives Figma.

What is Figwright?

Figwright connects an MCP server to a Figma plugin over a local WebSocket relay, so an AI agent — Claude Code, Cursor, Codex, or any other MCP client — can work with Figma instead of just looking at it.

It works in both directions:

Read — turn a Figma selection into framework-aware code, grounded on faithful, de-duplicated design context (layout, typography, variables, components).

Write — author and edit the canvas directly: frames, text, auto-layout, styles, variables, components, whole screens.

Everything runs on your machine and talks to Figma through a plugin, so it needs no Figma Dev Mode seat and no paid tier.

Why Figwright

• Free — no Figma Dev Mode or paid seat. The official Dev Mode MCP is gated; Figwright isn't.
• Bidirectional — not read-only. 112 tools span reading and writing the canvas, so an agent can both implement designs and build them.
• Provider-first codegen — Figwright detects your real stack (framework + styling system) and reuses your existing components, tokens, and icons, instead of emitting generic markup you have to rewrite.
• Any MCP client — Claude Code, Cursor, and other MCP-capable agents all work the same way.
• Open & extensible — the read/write workflows ship as installable skills you can adopt or fork.

How it works

Your MCP client talks to the @figwright/mcp server over stdio; the server relays to the Figma plugin over a local WebSocket. Several clients can share one plugin — they elect a leader that owns the connection — and the transport is built to ride out dropped sockets:

---

GitHub에서 전체 내용 보기