In-depth architectural comparison of the Figwright and Figma Context MCP AIR 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 Context MCP AIR
Architecture & Design · Local stdio
Quality: 51/100 (Good) | Auth: No auth required
Verdict Summary: Choose Figwright if you need specialized Architecture & Design tools running via a local process. Choose Figma Context MCP AIR 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.
Figma MCP server for AI agents. 9 tools: design context, variables, screenshots, and FigJam.
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 Context MCP AIR Tools (7)
download_figma_images
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 AIR belongs to Architecture & Design using local stdio subprocess. Select Figwright when you need capabilities focused on architecture & design and Figma Context MCP AIR when you require tools for architecture & design.
Downloads PNG or SVG renders of Figma nodes to your local filesystem.
get_screenshot
Captures a Figma node as a 2x PNG and saves it to disk. Useful for visual validation.
get_metadata
Returns a sparse XML representation of the node hierarchy (depth=2). Use this for quick layer discovery before fetching full design context.
get_variable_defs
Fetches all design tokens from a Figma file — variable collections (colors, spacing, typography) and published styles (effects, text styles, fill styles). Returns data with CSS custom property syntax.
whoami
Returns the authenticated user's Figma account information (name, email, plan tier). Useful for verifying your API key is working.
create_design_system_rules
Generates a comprehensive markdown template for project-specific design system rules. Tailored to your language and framework combination. Save the output to `CLAUDE.md` or your project's AI instructions file.
get_figjam
Extracts content from a FigJam board — sticky notes, connectors, shapes, sections — as XML with screenshot URLs.