Figwright vs Figma Context MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Figwright vs Figma Context MCP
In-depth architectural comparison of the Figwright and Figma Context 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: 67/100 (Great) | Auth: No auth required
Figma Context MCP
Architecture & Design · Local stdio
Quality: 51/100 (Good) | Auth: API Key required
Verdict Summary: Choose Figwright if you need specialized Architecture & Design tools running via a local process. Choose Figma Context 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).
You have access to required keys: FIGMA_PLUGIN_PORT, FIGMA_PLUGIN_HOST.
You need dedicated capabilities in the Architecture & Design domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: FIGMA_API_KEY, PORT.
Primary tools included: Access Figma file, frame, or group metadata, Simplify and translate Figma API responses, Provide relevant layout and styling info only.
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.
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 (5)
Access Figma file, frame, or group metadata
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 Context MCP belongs to Architecture & Design using local stdio subprocess. Select Figwright when you need capabilities focused on architecture & design and Figma Context MCP when you require tools for architecture & design.
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.
Provide coding agents direct access to Figma data to help them one-shot design implementation.