Figma Context MCP vs Figwright — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Figma Context MCP vs Figwright
In-depth architectural comparison of the Figma Context MCP and Figwright 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
Figma Context MCP
Architecture & Design · Local stdio
Quality: 71/100 (Great) | Auth: API Key required
Figwright
Architecture & Design · Local stdio
Quality: 69/100 (Great) | Auth: No auth required
Verdict Summary: Choose Figma Context MCP if you need specialized Architecture & Design tools running via a local process. Choose Figwright 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 Figma Context MCP when:
You need dedicated capabilities in the Architecture & Design domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: FIGMA_API_KEY, PORT.
Provide coding agents direct access to Figma data to help them one-shot design implementation.
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.
Category & Scope
Tools & Capabilities Breakdown
Figma Context MCP Tools (2)
get_figma_data
Get comprehensive Figma file data including layout, content, visuals, and component information
download_figma_images
Download SVG and PNG images used in a Figma file based on the IDs of image or icon nodes. Images will be saved relative to the server's image directory: /home/user
Figwright Tools (3)
Read
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).
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.
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).
Figma Context MCP is categorized under Architecture & Design and uses a local stdio subprocess. In contrast, Figwright belongs to Architecture & Design using local stdio subprocess. Select Figma Context MCP when you need capabilities focused on architecture & design and Figwright when you require tools for architecture & design.
`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…