figwright

Figwright connects an MCP server to a Figma plugin over a local WebSocket relay, so an agent such as Claude Code, Cursor or Codex can work with Figma rather than just look at it. The README says it works in two directions: reading a Figma selection and turning it into framework-aware code, and writing to the canvas (frames, text, auto-layout, styles, variables, components and whole screens). It claims 104 tools across both directions.

Everything runs on your machine and talks to Figma through a plugin, so the README says it needs no Figma Dev Mode seat and no paid tier. For code generation it says it detects your actual framework and styling system and reuses your existing components, tokens and icons. Several MCP clients can share one plugin, with a leader process owning the connection, and the transport is built to survive dropped sockets. Read and write workflows are also published as installable agent skills.

Setup has four steps. Add `npx -y @figwright/mcp@latest` to your MCP client config; download the plugin zip from the latest GitHub release and import its `manifest.json` in the Figma desktop app (the plugin is not on the Figma Community marketplace yet); open the plugin, which connects automatically; and ask the agent to run `ping`. It is MIT licensed and was last pushed on 2026-10-12. This review is based on the README and repository data; we have not run it ourselves.