Figwright vs Figma Edit MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Figwright vs Figma Edit MCP
In-depth architectural comparison of the Figwright and Figma Edit MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Figwright
Architecture & Design · Local stdio
Quality: 65/100 (Great) | Auth: No auth required
Figma Edit MCP
Architecture & Design · Local stdio
Quality: 57/100 (Good) | Auth: No auth required
Verdict Summary: Choose Figwright if you need specialized Architecture & Design tools running via a local process. Choose Figma Edit MCP if your workspace requires Architecture & Design integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Figwright when:
You need dedicated capabilities in the Architecture & Design domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
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.
Programmatically read, create, and modify Figma designs via MCP.
selection, document and node inspection, styles, variables, components, fonts, reactions, 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 than one open Figma…
Write
create and edit frames, text, shapes, auto-layout, effects, styles, variables, components (including authoring their boolean/text/instance-swap properties), pages, reactions, and Motion animations (keyframes, animation-style presets, timelines); plus a `batch` tool to apply many edits at once.
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 Edit MCP Tools (45)
page_info
List the document's pages; with `pageIds`, return those pages and their top-level children
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Figwright is categorized under Architecture & Design and uses a local stdio subprocess. In contrast, Figma Edit MCP belongs to Architecture & Design using local stdio subprocess. Select Figwright when you need capabilities focused on architecture & design and Figma Edit MCP when you require tools for architecture & design.
Read one or more nodes — recursive traversal with `properties`, `filter`, and `maxDepth` (the workhorse read; also returns bound variables / explicit modes)
node_transform
Move and/or resize a node by setting absolute `x` / `y` / `width` / `height
node_rename
Rename a node
node_delete
Delete one or more nodes in a single validated batch
node_clone
Duplicate a node, optionally at a new position
view_navigate
Navigate the editor view to a page or node(s)
node_group
Wrap nodes in a new group
node_ungroup
Dissolve a group, promoting its children
node_flatten
Flatten a node and its children into a single vector
node_insert_child
Reparent a node under a new parent at an optional index
node_set_auto_layout
Configure a frame's auto-layout (mode, padding, spacing, alignment, sizing)