Figwright vs Figma MCP Server — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Figwright vs Figma MCP Server
In-depth architectural comparison of the Figwright and Figma MCP Server 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: 69/100 (Great) | Auth: No auth required
Figma MCP Server
Architecture & Design · Remote HTTP/SSE
Quality: 47/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Figwright if you need specialized Architecture & Design tools running via a local process. Choose Figma MCP Server if your workspace requires Architecture & Design integration with remote web transport. 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.
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.
The Figma MCP server brings Figma design context directly into your AI workflow.
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 MCP Server Tools (0)
No explicit tool names declared in metadata yet. Check project README on main listing page.
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 MCP Server belongs to Architecture & Design using remote streaming HTTP/SSE transport. Select Figwright when you need capabilities focused on architecture & design and Figma MCP Server when you require tools for architecture & design.