Figwright vs Figma Context MCP
A side-by-side look at the Figwright and Figma Context MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Figwright for architecture & design work as a local process; choose Figma Context MCP 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?
Choose 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.
Choose Figma Context MCP when
- You need dedicated capabilities in the Architecture & Design domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
FIGMA_API_KEY. - You want tools like
get_figma_design, get_image_fills, render_node_images.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Architecture & Design | Architecture & Design |
| Quality signal | 69/100 · Great | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | FIGMA_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1,122 | 7 |
| Directory activity | 6 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 3 | 4 |
| Full listing | View Figwright | View Figma Context MCP |
Tools & capabilities
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…
Figma Context MCP tools 4
get_figma_designFetches CSS-aligned, LLM-optimized design data. Supports SVG export to custom dir.get_image_fillsRetrieves image fill URLs from a Figma filerender_node_imagesRenders Figma nodes as PNG imagesread_vector_svgReads vector node data as SVG
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.
Figwright
{
"mcpServers": {
"awdr74100-figwright": {
"command": "npx",
"args": [
"-y",
"@figwright/mcp@latest"
]
}
}
}
Figma Context MCP
{
"mcpServers": {
"figma-context-mcp": {
"command": "npx",
"args": [
"-y",
"@tmegit/figma-to-code-mcp"
],
"env": {
"FIGMA_API_KEY": "YOUR_FIGMA_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Figwright is categorized under Architecture & Design and uses a local stdio subprocess. Figma Context MCP belongs to Architecture & Design and uses a local stdio subprocess. Pick Figwright for architecture & design work and Figma Context MCP 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.
Figwright is listed as free. Auth: no auth required. Figma Context MCP has no declared pricing — check the project's own site. 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 awdr74100-figwright and figma-context-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Figwright has a quality signal of 69/100 (Great) with 6 views, 0 installs and 1,122 GitHub stars. Figma Context MCP has 55/100 (Good) with 2 views, 0 installs and 7 GitHub stars.