FigmaMCP

Figwright vs FigmaMCP

Figwright is a free two-way Figma MCP server, and FigmaMCP is a free Mac app that does a similar job. Both let an agent read and edit the file open in Figma desktop through a plugin on your machine. They differ in how you install them, what runs on your computer and how edits are limited. Facts about Figwright come from its GitHub README, checked 2026-11-20.

Figwright and FigmaMCP
FigwrightFigmaMCP
PriceFreeFree Mac app
Source codePublic on GitHub; license: see its repositoryNot public; the built app and releases are. See is the source public
Install the serverAdd a server entry for @figwright/mcp, launched with npx, to your MCP client configDownload the Mac app; it connects Claude Code and Codex for you
Install the pluginDownload the plugin zip from the latest GitHub release, unzip it, and import its manifest in the Figma desktop appThe Mac app registers the plugin in Figma for you
Needs Node.jsYes, 20.19+ or 22.12+No
Figma token or Dev Mode seatREADME says it pairs with a plugin, not a Dev Mode seat; it mentions no Figma API tokenNo API token, no Dev Mode seat
Reads and writesBoth; README counts 136 tools, plus optional skillsBoth; see tools
Dev Mode and FigJamREADME says it runs in both, with less available; in Dev Mode it can read and export but every write failsDev Mode features are not included; see without Dev Mode
Several files at onceYes; each agent can claim its own open fileThe agent picks one file when several have the plugin open
Limits on editsREADME describes an activity log in the plugin, per-file routing, and a retried write that is replayed instead of applied twice. We did not find a read-only switch or a name check on each edit in itEach edit must name its target exactly, a bulk edit with one invalid item changes nothing, and one switch in the plugin makes the file read-only
Where data goesREADME says everything stays on your machineLocal; see privacy for the counts we collect
PlatformREADME states no operating system limit. It needs Node, and the Figma desktop app to import the plugin; its diagram shows Figma in the desktop app or the browser. We have not tested it on Windows or LinuxmacOS only; needs the Figma desktop app, not the browser

Source: Figwright README, checked 2026-11-20. These may change; its repository is the authority.

Where Figwright is better

Where FigmaMCP is different

Which one to choose

Choose Figwright if you want public code, you are not on a Mac, or you want its broader tool set and are comfortable with Node and importing a plugin by hand. Choose FigmaMCP if you use a Mac with Claude Code or Codex and want the shortest install and strict limits on what an edit can touch. Both are free, so you can try both on a copy of a file; avoid having two tools edit the same file at once.

Download for Mac Version 0.1.20 macOS 14+ · Intel & Apple Silicon · ~155 MB

See also all comparisons, other Figma MCP alternatives, Figma MCP rate limit and setup.

Questions

Is Figwright free?
Yes. Its README describes it as a free two-way Figma MCP server that runs on the free Figma tier. Source: the Figwright README, checked 2026-11-20. FigmaMCP is free too.
How do I install Figwright?
Its README has two steps: add a server entry for @figwright/mcp, launched with npx, to your MCP client, then download the plugin zip from the latest GitHub release and import its manifest in the Figma desktop app. It needs Node.js 20.19+ or 22.12+. Source: the Figwright README, checked 2026-11-20.
Does Figwright work on Windows or Linux?
Its README states no operating system limit, says the Figma desktop app is needed to import the plugin, and shows Figma in the desktop app or the browser. We have not tested it on Windows or Linux. FigmaMCP is macOS only. Checked 2026-11-20.
Is FigmaMCP open to read like Figwright?
No. Figwright’s source is public. FigmaMCP’s source code is private; the built app and its releases are public.
Is FigmaMCP affiliated with Figwright or Figma?
No. FigmaMCP is independent and is not endorsed by Figma, Inc.

Last updated: