Figma MCP Bridge vs Layerwright
A side-by-side look at the Figma MCP Bridge and Layerwright MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
L
LayerwrightArchitecture & DesignTurn Claude Design and Claude Code designs into native, editable Figma files (HTML to Figma with Auto Layout and your Design System components), and Figma frames into code that uses your own React components. An MCP server and Figma plugin for Claude Code53GoodAuth: no auth requiredVerdict: choose Figma MCP Bridge for architecture & design work as a local process; choose Layerwright for architecture & design. 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.
LChoose Layerwright when
- You need dedicated capabilities in the Architecture & Design domain.
- Its auth model fits you: No auth required.
- You want tools like
import_html_to_plan, figma_execute_plan, figma_preview_plan.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | L Layerwright | |
|---|---|---|
| Category | Architecture & Design | Architecture & Design |
| Quality signal | 56/100 · Good | 53/100 · Good |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 9 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 18 | 16 |
| Full listing | View Figma MCP Bridge | View Layerwright |
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
Layerwright tools 16
import_html_to_planHTML file or folder → editable Design Plan (Auto Layout, DS components, your own mappings). Returns a `planIdfigma_execute_planBuilds a plan in Figma: one undo step, rollback on failure, automatic verificationfigma_preview_planValidates and resolves a hand-written plan and returns a summaryfigma_editRename, move, duplicate, set, delete, resize to fit, group / ungroup, boolean shapes, componentize (variants, text properties), swap instances, bind variables, apply styles, annotations, prototype links and flowsfigma_export_imageA node as an image; compared with the source HTML or another node, with a diff heatmap. `save: true` writes it to `.layerwright/exports/` to show the userfigma_inboxRequests the user sent from the Figma window to this session, and the answer shown back in the windowfigma_statusConnection, page and the open Figma files (`file` to switch), Design System scan (components, variants, variables, styles, duplicate names), task-scoped contextfigma_inspectSnapshots (tree, summary, text, instances, or the subtree as a plan, saved to a file with `save`), plan-vs-canvas checks, select and zoom (switches page)figma_linkLinks to the selection, layers or the page, and the file's own link. Any layer argument also takes a Figma linkfigma_analyze_designAudit a frame against the DS, or `mode: "sync"` after an import; apply the groups you approvefigma_import_htmlPixel-faithful import, page setup, variables and text stylesfigma_import_assetsIcons and pictures from files or folders: SVGs as vectors (or components), PNG/JPEG/GIF/WebP/AVIF as images, in a grid- +4 more on the listing page
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"
]
}
}
}
Layerwright
No confirmed install command for Layerwright yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Figma MCP Bridge is categorized under Architecture & Design and uses a local stdio subprocess. Layerwright belongs to Architecture & Design and uses an install path we have not confirmed yet. Pick Figma MCP Bridge for architecture & design work and Layerwright 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. Layerwright has no confirmed install command yet — follow its own setup instructions.
Figma MCP Bridge has no declared pricing — check the project's own site. Layerwright 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 layerwright 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 56/100 (Good) with 2 views, 0 installs and 2 GitHub stars. Layerwright has 53/100 (Good) with 0 views, 0 installs and 9 GitHub stars.