figma-console-mcp
Your design system as an API. Connect AI to Figma for extraction, creation, and debugging.
What is figma-console-mcp?
Your design system as an API. Connect AI to Figma for extraction, creation, and debugging.
Overview of figma-console-mcp
What it is
Figma Console MCP is a design-system-focused Model Context Protocol server for Figma. It connects AI assistants (such as Claude) to Figma, enabling bidirectional communication: reading design data and writing to Figma. The server runs deterministic checks for design-code parity, accessibility, and design-system health. It provides structured data (tokens, variants, bindings, states) rather than prescribing a specific framework, allowing generated code to follow the team's own stack and conventions.
Key features
- Design system extraction – pull variables, components, and styles from Figma - Codebase → design system extraction – scan a production codebase, mine styling into DTCG tokens with provenance, scaffold a design-system package with Storybook, and round-trip tokens into Figma variables - Bidirectional token sync – export Figma variables to DTCG JSON and other formats; push code-side edits back to Figma with create, rename, alias re-targeting, and replace-gated deletes - Visual debugging – take screenshots for context - Design creation – create UI components, frames, and layouts directly in Figma, including one-call component-set creation from a variant axes matrix - Variable management – create, update, rename, and delete design tokens - Version history & time-series awareness – list versions, diff snapshots, generate markdown changelogs, trace property/variant introduction via binary-search blame - Real-time monitoring – watch console logs from the Desktop Bridge plugin - FigJam boards – create stickies, flowcharts, tables, and code blocks - Slides presentations – build and manage Figma Slides decks programmatically - Accessibility scanning – 14 WCAG design checks with conformance level tagging, component scorecards, axe-core code scanning - Design-code parity & component docs – deterministic comparison of Figma components with code, and generated component documentation - Design-system health audits – Lighthouse-style scored audit across naming, tokens, component metadata, accessibility, consistency, and coverage - Cross-MCP identity – every tool response carries
_mcp: 'figma-console-mcp'and errors are prefixed[figma-console-mcp] - Cloud Write Relay – web AI clients (Claude.ai, v0, Replit) can design in Figma via cloud pairing - Four ways to connect – Remote SSE, Cloud Mode, NPX, or Local Git
Use cases
- Connecting AI assistants to Figma for design system extraction and token management - Syncing design tokens bidirectionally between codebase and Figma variables - Creating UI components, frames, and layouts programmatically with AI - Auditing design system health and accessibility - Generating component documentation with design and git history - Debugging designs visually and monitoring real-time console logs
Getting started
Prerequisites: Node.js 18+, Figma Desktop, and an MCP client (Claude Code, Cursor, Windsurf, Claude Desktop, etc.). Obtain a Figma personal access token with scopes: File content, File versions, Library content, Library assets, Comments (Read and write), Current user, and Variables (optional). Configure your MCP client. Example for Cursor / Windsurf / Claude Desktop (add to MCP config file): json { 'mcpServers': { 'figma-console': { 'command': 'npx', 'args': ['-y', 'figma-console-mcp@latest'], 'env': { 'FIGMA_ACCESS_TOKEN': 'figd_YOUR_TOKEN_HERE', 'ENABLE_MCP_APPS': 'true' } } } } For Claude Code CLI: bash claude mcp add figma-console -s user -e FIGMA_ACCESS_TOKEN=figd_YOUR_TOKEN_HERE -e ENABLE_MCP_APPS=true -- npx -y figma-console-mcp@latest See the repository README for full setup instructions for other clients.
License and pricing
Licensed under MIT. Open source – no pricing information stated.
Based on the project's public README and repository metadata.