In-depth architectural comparison of the Figma Context MCP 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
Figma Context MCP
Architecture & Design · Local stdio
Quality: 60/100 (Good) | Auth: API Key required
Figma Context MCP AIR
Architecture & Design · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
Verdict Summary: Choose Figma Context MCP 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 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.
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
Figma Context MCP AIR Tools (7)
download_figma_images
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.
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, Figma Context MCP AIR belongs to Architecture & Design using local stdio subprocess. Select Figma Context MCP when you need capabilities focused on architecture & design and Figma Context MCP AIR when you require tools for architecture & design.
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.