Figma vs Figwright

A side-by-side look at the Figma and Figwright MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Figma logoFigmaArchitecture & Design · Local subprocess (stdio)A local MCP server with full Figma REST API coverage.60GoodAuth: api key requiredFigwright logoFigwrightArchitecture & Design · Local subprocess (stdio)Bidirectional Figma server over a local WebSocket relay: turn a selection into framework-aware code (reusing your components and tokens), or author frames, text, styles, variables, and whole screens back onto the canvas. 92 tools, any MCP client, no Dev Mode seat or paid tier.69GreatAuth: no auth required

Verdict: choose Figma for architecture & design work as a local process; choose Figwright for architecture & design as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Figma logoChoose Figma when

  • You need dedicated capabilities in the Architecture & Design domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: FIGMA_API_KEY.
  • You want tools like list_file_variables, get_published_variables, modify_variables.
Explore Figma

Figwright logoChoose Figwright when

  • You need dedicated capabilities in the Architecture & Design domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
  • You want tools like Read, Write, Grounding.
Explore Figwright

Feature & specification comparison

Rows where the two servers differ are marked.

SpecFigma logoFigmaFigwright logoFigwright
CategoryArchitecture & DesignArchitecture & Design
Quality signal60/100 · Good69/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthAPI key requiredNo auth required
PricingNot declaredFree
Required env varsFIGMA_API_KEYNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars101,155
Directory activity 8 views 0 installs 0 upvotes 6 views 0 installs 0 upvotes
Tools33

Tools & capabilities

Figma tools 3

  • list_file_variables
  • get_published_variables
  • modify_variables

Figwright tools 3

  • Readselection, document and node inspection, styles, variables, components, fonts, prototype reactions and flows, motion (animation) state, screenshots, original image-fill assets, PDF export, and video export of animated frames (MP4 / GIF / WebM); plus `list_files` / `use_file` for working across more…
  • Writecreate and edit frames, text, shapes (lines, polygons, stars, boolean operations, flattening), auto-layout, alignment and distribution, effects, images (as a new layer or into an existing layer's fill), styles, variables (including importing a team library's variables and styles, and switching a fr…
  • Grounding`get_design_context` for faithful, de-duplicated design context, and `component_map` / `token_map` / `icon_map`, which join Figma data to your codebase so codegen reuses what you already have; plus `design_diff`, which reports what changed in a design against a saved baseline so you update only the…

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Figma

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "figma-2": {
      "command": "bunx",
      "args": [
        "figma-mcp-server"
      ],
      "env": {
        "FIGMA_API_KEY": "YOUR_FIGMA_API_KEY_HERE"
      }
    }
  }
}

Figwright

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "awdr74100-figwright": {
      "command": "npx",
      "args": [
        "-y",
        "@figwright/mcp@latest"
      ]
    }
  }
}

Frequently asked questions

Figma is categorized under Architecture & Design and uses a local stdio subprocess. Figwright belongs to Architecture & Design and uses a local stdio subprocess. Pick Figma for architecture & design work and Figwright for architecture & design.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Figma has no declared pricing — check the project's own site. Auth: api key required. Figwright is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add figma-2 and awdr74100-figwright as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Figma has a quality signal of 60/100 (Good) with 8 views, 0 installs and 10 GitHub stars. Figwright has 69/100 (Great) with 6 views, 0 installs and 1,155 GitHub stars.