What is Figwright?
Figwright is an open source MCP server that connects a coding agent to Figma through a plugin and a local WebSocket relay. It exposes 135 tools to read designs into code and to write frames, styles, variables and components, and the README says it runs on the free Figma tier.
Figwright is an MCP server plus a Figma plugin. The server talks to your agent over stdio and relays each call over a local WebSocket to the plugin, which runs it through Figma's Plugin API.
It works in both directions. Reading turns a Figma selection into code that matches your stack. Writing lets the agent create and edit frames, text, auto-layout, styles, variables, components and whole screens.
What it changes for design to code work
- The README says the official Dev Mode MCP needs a paid seat, while Figwright works through a plugin on the free Figma tier.
- Its codegen is provider-first: it looks for your framework and styling system and reuses existing components, tokens and icons.
- Grounding tools join Figma data to your codebase, and a diff tool reports what changed against a saved baseline.
- Several agents can work at once, each claiming its own open Figma file.
Who it is for
Best for
- Developers who want a selected frame turned into components that reuse their own design system.
- Designers and developers who want an agent to build screens directly on the Figma canvas.
- Teams without a Dev Mode seat who still want an MCP route into Figma.
Not for
- Anyone who cannot import a development plugin into the Figma desktop app, which the setup requires.
- Dev Mode sessions that need writes. The README says Figma makes plugins read-only there.
- Workflows where nobody reviews the agent's changes, since write tools alter your Figma file.
Use it with UiChemy
Figwright works on the Figma side. When the finished design needs to become a live site, UiChemy's Figma to WordPress converts designs into editable pages. Compare other bridges in the figma-mcp-rust write-up. Click Get Started on uichemy.com.
Connect Figwright MCP: A Free Two-Way Figma Server for Coding Agents to your AI client
npx -y @figwright/mcp@latestCheck the requirements
You need an MCP client, Node.js 20.19+ or 22.12+, and Figma. The free tier is enough, but the desktop app is needed to import the plugin.
Add the server
Put the config above in your client's MCP settings. For Claude Code that is the project .mcp.json, and the README says other clients use the same shape.
Import the plugin
Download the plugin zip from the latest GitHub release, unzip it, then in Figma choose Plugins, Development, Import plugin from manifest and pick manifest.json.
Connect and test
Open the Figwright plugin from Plugins, Development. It connects to the local server and shows Connected. Ask the agent to run ping to confirm the link.
Client configuration
{
"mcpServers": {
"figwright": {
"command": "npx",
"args": ["-y", "@figwright/mcp@latest"]
}
}
}Endpoints and ports
127.0.0.1:3055Local WebSocket between the server and the Figma pluginstdioYour MCP client launches the server processWhat you can do with it
- Read a selection into codeSelect a frame and ask for a component. The server supplies layout, type, variables and component data so the agent writes code for your stack.
- Write to the canvasAgents can create frames, text, shapes, auto-layout, effects, styles, variables, components, pages and prototype reactions.
- Reuse your own systemComponent, token and icon maps tie the design to your codebase, so output uses existing parts instead of generic markup.
- Update only what changedThe diff tool compares a design to a saved baseline, so you change only the code that the edit affects.
- Work across several filesEach agent can claim its own open Figma file, which keeps two agents from editing the same design by accident.
- Inspect every callThe plugin panel shows an activity log, the exact payload sent to the model and a debug tab with server and plugin versions.
- Runs on your machineThe README says the server, the relay and the plugin all run locally and designs are not sent anywhere else.
Tools it exposes
ping
Confirms the agent can reach the Figma plugin.
get_design_context
Returns faithful, de-duplicated context for a selection: layout, typography, variables and components.
component_map
Joins Figma components to the components in your codebase so codegen reuses them.
token_map
Joins Figma variables and styles to your project's design tokens.
icon_map
Matches icons in the design to icons your project already has.
design_diff
Reports what changed in a design against a saved baseline.
list_files
Lists every Figma file that currently has the plugin open.
use_file
Claims one open file for this agent so edits do not land in another design.
Frequently asked questions
What is Figwright?
Figwright is an MIT licensed MCP server and Figma plugin pair. The server talks to your agent over stdio and relays tool calls to the plugin over a local WebSocket. It reads designs into code and writes to the canvas, using 135 tools according to the README.
Do I need a paid Figma plan or Dev Mode seat for Figwright?
No. The README states that Figwright talks to Figma through a plugin, so the free tier is enough. You do need the Figma desktop app once, to import the plugin from its manifest file, plus Node.js 20.19+ or 22.12+ for the server.
How do I install the Figwright MCP server?
Add an entry to your MCP client config that runs npx with the arguments -y and @figwright/mcp@latest. Then download the plugin zip from the latest GitHub release and import its manifest.json in Figma. Opening the plugin shows Connected once the relay link works.
Does Figwright work with Claude Code, Cursor and Codex?
The README names Claude Code, Cursor and Codex as example clients and says any other MCP client works. Its setup example uses a project .mcp.json, and it states other clients use the same configuration shape.
Can Figwright edit Figma files, or is it read only?
It can do both. The README lists read tools for selections, nodes, styles, variables and exports, and write tools for frames, text, auto-layout, components and more. In Dev Mode the plugin is read only because Figma restricts plugins there.
Why does the Figwright server fail to start or disconnect?
The README says clients spawn the command directly, not through your shell, so version managers like fnm or nvm may hide npx. Use the absolute path to npx, or install the package and drop the @latest tag to avoid a registry fetch at launch.
Can two agents use Figwright on different Figma files?
Yes, once each agent claims its file. The list_files tool shows files with the plugin open and use_file claims one. The README notes that the claim belongs to one MCP client process, so two agents need two separate clients.
What are alternatives to Figwright?
Other Figma bridges include the figma-mcp-rust server and the Figma MCP Bridge. For read-only layout context, see Framelink MCP for Figma. Figwright's pitch is two-way work with codebase mapping on the free tier.


