Figma Context MCP AIR
Pull Figma design context, variables, screenshots, and FigJam into your agent session while implementing UI.
Overview
Figma Context MCP AIR is a MCP server for the Build phase that gives agents nine tools to read Figma design context, variables, screenshots, and FigJam over stdio.
What is this MCP server?
- Nine MCP tools for design context, variables, screenshots, and FigJam workflows
- figma-context-mcp-air npm package v2.0.2 with --stdio positional argument
- Requires FIGMA_API_KEY personal access token (secret, required)
- AIR variant of Figma Context MCP focused on agent-readable design structure
- Nine documented MCP tools for Figma and FigJam
- Published server version 2.0.2
- npm identifier figma-context-mcp-air with required FIGMA_API_KEY
Community signal: 1 GitHub stars.
What problem does it solve?
Implementing UI from Figma without structured context in the agent leads to wrong tokens, layouts, and endless screenshot paste churn.
Who is it for?
Solo builders shipping UI from Figma files who use Claude Code or Cursor and want MCP-native design variables and screenshots during frontend Build.
Skip if: Teams with no Figma source of truth, or backends-only work with zero design file access.
What do I get? / Deliverables
After setup with a Figma PAT, your agent can fetch authoritative design context and assets so frontend implementation aligns with the file.
- Agent-callable Figma design context, variables, and screenshots
- FigJam-aware context for collaborative spec threads
- Reduced manual copy-paste during frontend Build
Recommended MCP Servers
Journey fit
Figma-to-code context is Build work: you consume design specs while constructing frontend surfaces. Frontend is the canonical shelf because the nine tools target design tokens, frames, screenshots, and FigJam for implementation handoff.
How it compares
Figma API MCP for design handoff, not a standalone UI component library or generic browser automation skill.
Common Questions / FAQ
Who is Figma Context MCP AIR for?
Indie developers and designer-coders who build from Figma and want their MCP agent to pull structured design context instead of manual exports.
When should I use Figma Context MCP AIR?
Use it during Build frontend work when translating frames, variables, or FigJam boards into code inside your agent session.
How do I add Figma Context MCP AIR to my agent?
Register figma-context-mcp-air with stdio and pass --stdio; set FIGMA_API_KEY to a Figma personal access token with access to the files you reference.