Figma MCP Bridge vs Figwright
A side-by-side look at the Figma MCP Bridge and Figwright MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Figma MCP Bridge 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?
Choose Figma MCP Bridge when
- You need dedicated capabilities in the Architecture & Design domain.
- You prefer a local stdio subprocess transport.
- You want tools like
figma_execute_code, figma_inspect, figma_read_canvas.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Architecture & Design | Architecture & Design |
| Quality signal | 57/100 · Good | 69/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 1,155 |
| Directory activity | 7 views 0 installs 0 upvotes | 6 views 0 installs 0 upvotes |
| Tools | 18 | 3 |
| Full listing | View Figma MCP Bridge | View Figwright |
Tools & capabilities
Figma MCP Bridge tools 18
figma_execute_codeRun JS in the Figma sandbox. Injects `figma`, `ensureFont`, `getFreePosition`, `progress`, `bridge`. Supports `capture`, `capture_node_ids`, `diff`, `max_px`, `max_output_bytes`, `async`, `target`.figma_inspectRead many live nodes in one call: compact outline (or `view: "map"` canvas map), exact `props` (incl. `reactions`, `connector`), name `find` / text `find_text`, `context` (ancestor sections, breakpoints, component variants), `offset` paging, or `check` expectations (mismatches only). Changes nothin…figma_read_canvasToken-optimized read of the **live** document (`jsx` / `tree` / `json`) with `budget_tokens` (default: the server's byte budget).figma_screenshotPNG of specific `node_ids` or the current selection, sized by `max_px`.figma_find_componentsCached, tokenized, fuzzy component search — variants, properties, keys.figma_insert_component_instanceInstantiate a component/variant, apply text overrides, place into AutoLayout.figma_insert_svgInsert raw SVG with proportional scaling, recoloring, optional component wrapping.figma_get_variablesVariable collections, modes, and token values.figma_rollbackUndo a previous write call's checkpoint.figma_get_selectionGeometry, compact hex fills, parent/page, AutoLayout context of the selection.figma_get_canvas_layoutArtboard bounds + a safe `suggestedNextPosition`. `layout:"grid"` shelf-packs.figma_set_variables_modeSwitch theme mode (Dark/Light/Brand) on a frame or page.- +6 more on the listing page
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 MCP Bridge
{
"mcpServers": {
"figma-mcp-bridge": {
"command": "npx",
"args": [
"-y",
"@kolganovr/figma-mcp-bridge"
]
}
}
}
Figwright
{
"mcpServers": {
"awdr74100-figwright": {
"command": "npx",
"args": [
"-y",
"@figwright/mcp@latest"
]
}
}
}
Frequently asked questions
Figma MCP Bridge is categorized under Architecture & Design and uses a local stdio subprocess. Figwright belongs to Architecture & Design and uses a local stdio subprocess. Pick Figma MCP Bridge 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 MCP Bridge is listed as free. 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-mcp-bridge and awdr74100-figwright as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Figma MCP Bridge has a quality signal of 57/100 (Good) with 7 views, 0 installs and 2 GitHub stars. Figwright has 69/100 (Great) with 6 views, 0 installs and 1,155 GitHub stars.