Figma Context MCP AIR vs Figma MCP Bridge | AllMCPs
Side-by-Side Model Context Protocol Comparison
Figma Context MCP AIR vs Figma MCP Bridge
In-depth architectural comparison of the Figma Context MCP AIR and Figma MCP Bridge 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 AIR
Architecture & Design · Local stdio
Quality: 51/100 (Good) | Auth: No auth required
Figma MCP Bridge
Architecture & Design · Local stdio
Quality: 56/100 (Good) | Auth: No auth required
Verdict Summary: Choose Figma Context MCP AIR if you need specialized Architecture & Design tools running via a local process. Choose Figma MCP Bridge 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 AIR 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_API_KEY, FIGMA_OAUTH_TOKEN, PORT, OUTPUT_FORMAT, SKIP_IMAGE_DOWNLOADS, NODE_ENV.
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.
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 AIR is categorized under Architecture & Design and uses a local stdio subprocess. In contrast, Figma MCP Bridge belongs to Architecture & Design using local stdio subprocess. Select Figma Context MCP AIR when you need capabilities focused on architecture & design and Figma MCP Bridge when you require tools for architecture & design.
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.
Figma MCP Bridge Tools (18)
figma_execute_code
Run JS in the Figma sandbox. Injects `figma`, `ensureFont`, `getFreePosition`, `progress`, `bridge`. Supports `capture`, `capture_node_ids`, `diff`, `max_px`, `max_output_bytes`, `async`, `target`.
figma_inspect
Read many live nodes in one call: compact outline (or `view: "map"` canvas map), exact `props` (incl. `reactions`, `connector`), name `find` / text `find_text`, `context` (ancestor sections, breakpoints, component variants), `offset` paging, or `check` expectations (mismatches only). Changes nothin…
figma_read_canvas
Token-optimized read of the **live** document (`jsx` / `tree` / `json`) with `budget_tokens` (default: the server's byte budget).
figma_screenshot
PNG of specific `node_ids` or the current selection, sized by `max_px`.