figma-console-mcp
Provides tools for extracting, creating, and managing design elements in Figma, including variables, components, styles, frames, and layouts; enables bidirectional token sync, visual debugging, version history, real-time monitoring, FigJam boards, slides presentations, accessibility scanning, and design-system health audits.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@figma-console-mcp Export all variables to DTCG format"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Figma Console MCP Server
Your design system as an API. A design-system-focused Model Context Protocol server for Figma. It works in both directions (Figma ⇄ code), writes to Figma, and runs deterministic checks for design-code parity, accessibility, and design-system health. It hands the AI exact tokens, variants, bindings, and states as structured data rather than prescribing a framework or house style, so generated code follows your team's own stack and conventions.
🆕 Shaders, grid and auto layout, OKLCH and P3 color, text wrap and variable fonts (latest v1.46.0): apply shaders and set their properties by name (
figma_apply_shader,figma_list_shaders), set auto layout or grid layout in one call with CSS-style grid tracks (figma_set_layout), use OKLCH, Display P3 and other CSS colors on fills and strokes, and set text wrap (balance, pretty) and variable-font axes withfigma_set_text(v1.46.0). v1.45 added Motion: animate layers with presets, custom animation styles or keyframes bound to Timing and Easing tokens, export video, and find code layers. See what's new →
What is this?
Figma Console MCP connects AI assistants (like Claude) to Figma, enabling:
🎨 Design system extraction - Pull variables, components, and styles
🧬 Codebase → design system extraction - Scan a production codebase, mine its de-facto styling into DTCG tokens with per-token provenance, scaffold a design-system package with a wired Storybook workshop, and gate it with deterministic fidelity evals — then round-trip the tokens into Figma variables (Local Mode)
🔁 Bidirectional token sync - Export Figma variables to DTCG JSON (legacy or 2025.10 dialect) + 9 more formats; push code-side edits back to Figma with full apply — creates, renames, alias re-targeting, and replace-gated deletes. Replaces Style Dictionary and Tokens Studio's export pipeline.
📸 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, and fold per-component design + git history into generated component docs
⚡ Real-time monitoring - Watch console logs from the Desktop Bridge plugin
📌 FigJam boards - Create stickies, flowcharts, tables, and code blocks on collaborative boards
🎞️ 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-to-code parity
🔍 Design-code parity & component docs - Deterministic comparison of a Figma component with its code (visual, spacing, typography, tokens, component API, accessibility), and generated component documentation with per-variant tokens and an optional design + git changelog
📋 Design-system health audits - Lighthouse-style scored audit across naming, tokens, component metadata, accessibility, consistency, and coverage — available as a plain tool for any MCP client (with per-finding auto-fix guidance) and as a visual dashboard app
🛡 Cross-MCP identity - Every tool response carries
_mcp: "figma-console-mcp"and errors are prefixed[figma-console-mcp]so attribution stays unambiguous in agents running multiple Figma MCPs☁️ 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
Related MCP server: Figma MCP Server
⚡ Quick Start
Choose Your Setup
First, decide what you want to do:
I want to... | Setup Method | Time |
Create and modify designs with AI | NPX Setup (Recommended) | ~10 min |
Design from the web (Claude.ai, v0, Replit, Lovable) | ~5 min | |
Contribute to the project | ~15 min | |
Just explore my design data (read-only) | ~2 min |
⚠️ Important: Capability Differences
Capability | NPX / Local Git | Cloud Mode | Remote SSE |
Read design data | ✅ | ✅ | ✅ |
Create components & frames | ✅ | ✅ | ❌ |
Edit existing designs | ✅ | ✅ | ❌ |
Manage design tokens/variables | ✅ | ✅ | ❌ |
FigJam boards (stickies, flowcharts) | ✅ | ✅ | ❌ |
Real-time monitoring (console, selection) | ✅ | ❌ | ❌ |
Codebase → design system extraction ( | ✅ | ❌ | ❌ |
Desktop Bridge plugin | ✅ | ✅ | ❌ |
Requires Node.js | Yes | No | No |
Total tools available | 130 | 105 after pairing | Read-only subset |
Bottom line: Remote SSE is read-only until you pair the plugin. Cloud Mode unlocks write access (105 tools) from web AI clients without Node.js. NPX/Local Git gives the full 130 tools with real-time monitoring.
🚀 NPX Setup (Recommended)
Best for: Designers who want full AI-assisted design capabilities.
What you get: All 130 tools including design creation, variable management, and component instantiation.
Prerequisites
Node.js 18+ — Check with
node --version(Download)Figma Desktop installed (not just the web app)
An MCP client (Claude Code, Cursor, Windsurf, Claude Desktop, etc.)
Step 1: Get Your Figma Token
Go to Manage personal access tokens in Figma Help
Follow the steps to create a new personal access token
Enter description:
Figma Console MCPSet scopes (all Read unless noted): File content, File versions, Library content, Library assets, Comments (Read and write), Current user, and Variables (Enterprise only, optional). See why each is needed
Copy the token — you won't see it again! (starts with
figd_)
Step 2: Configure Your MCP Client
Claude Code (CLI):
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@latestOpenAI Codex (CLI):
codex mcp add figma-console --env FIGMA_ACCESS_TOKEN=figd_YOUR_TOKEN_HERE --env ENABLE_MCP_APPS=true -- npx -y figma-console-mcp@latestThen set startup_timeout_sec = 60 and tool_timeout_sec = 300 for it in ~/.codex/config.toml (Codex's 10 s / 60 s defaults are too short). The Codex app and IDE extension share this config. Full Codex setup →
Gemini CLI:
gemini mcp add -s user -e FIGMA_ACCESS_TOKEN=figd_YOUR_TOKEN_HERE -e ENABLE_MCP_APPS=true figma-console npx -y figma-console-mcp@latestGoogle Antigravity (IDE, CLI, app): add the JSON below to ~/.gemini/config/mcp_config.json, plus "timeoutSeconds": 300 in the server entry. Full Antigravity setup →
Cursor / Windsurf / Claude Desktop:
Add to your MCP config file (see Where to find your config file below):
{
"mcpServers": {
"figma-console": {
"command": "npx",
"args": ["-y", "figma-console-mcp@latest"],
"env": {
"FIGMA_ACCESS_TOKEN": "figd_YOUR_TOKEN_HERE",
"ENABLE_MCP_APPS": "true"
}
}
}
}📂 Where to Find Your Config File
If you're not sure where to put the JSON configuration above, here's where each app stores its MCP config:
App | macOS | Windows |
Claude Desktop |
|
|
Claude Code (CLI) |
|
|
Cursor |
|
|
Windsurf |
|
|
OpenAI Codex (app, CLI, IDE) |
|
|
Gemini CLI |
|
|
Google Antigravity (IDE, CLI, app) |
|
|
Tip for designers: The
~symbol means your home folder. On macOS, that's/Users/YourName/. On Windows, it'sC:\Users\YourName\. You can open these files in any text editor — even TextEdit or Notepad.Can't find the file? If it doesn't exist yet, create it. The app will pick it up on its next restart. Make sure the entire file is valid JSON (watch for missing commas or brackets).
Claude Code users: You can skip manual editing entirely. Just run the
claude mcp addcommand above and it handles everything for you.
Step 3: Connect to Figma Desktop
Desktop Bridge Plugin:
Open Figma Desktop normally (no special flags needed) and open a file
Go to Plugins → Development → Import plugin from manifest...
Select
~/.figma-console-mcp/plugin/manifest.json(stable path, auto-created by the MCP server). Runnpx figma-console-mcp --print-pathto print the exact path for your machine.Run the plugin in your Figma file — it scans ports 9223–9232 and connects automatically to your running MCP server
Can't see the folder in the import dialog?
.figma-console-mcpstarts with a dot, so macOS hides it. In the dialog, press ⌘⇧G and paste the path (or press ⌘⇧. to show hidden files). On Windows the folder is visible as normal.
Heads-up on plugin updates. Figma caches plugin files (
code.jsandui.html) at the application level. The MCP server refreshes the files at~/.figma-console-mcp/plugin/on every startup, but Figma keeps using its cached copy until you re-import the manifest.Re-importing is required only when a release notes entry says so — typically when the plugin adds a new method the server needs (e.g. v1.22.4, v1.10.0). The plugin files last changed in v1.41.5; if your imported plugin predates that, re-import once. The plugin shows an update banner when the server bundles a newer plugin than the one running. For most upgrades the new server stays wire-compatible with the previous plugin, and re-importing is optional: you'll still get every functional change, just not the cosmetic plugin-side touches (status-pill copy,
pluginVersionreporting).When you do re-import: Plugins → Manage plugins → re-import
~/.figma-console-mcp/plugin/manifest.json. The stable path never changes, so it's a one-click step.
Step 4: Restart Your MCP Client
Restart your MCP client to load the new configuration.
Step 5: Test It!
Check Figma status→ Should show connection status with active WebSocket transport
Create a simple frame with a blue background→ Should create a frame in Figma (confirms write access!)
For Contributors: Local Git Mode
Best for: Developers who want to modify source code or contribute to the project.
What you get: Same 130 tools as NPX, plus full source code access.
Quick Setup
# Clone and build
git clone https://github.com/southleft/figma-console-mcp.git
cd figma-console-mcp
npm install
npm run build:localConfigure Your MCP Client
Add to your config file (see Where to find your config file):
{
"mcpServers": {
"figma-console": {
"command": "node",
"args": ["/absolute/path/to/figma-console-mcp/dist/local.js"],
"env": {
"FIGMA_ACCESS_TOKEN": "figd_YOUR_TOKEN_HERE",
"ENABLE_MCP_APPS": "true"
}
}
}
}Then follow NPX Steps 3-5 above.
📡 Remote SSE (Read-Only Exploration)
Best for: Quickly evaluating the tool or read-only design data extraction.
What you get: the read-only tools — view file data, components, styles, comments and version history, take screenshots, read logs, check design-code parity. Cannot create or modify designs.
Claude Desktop (UI Method)
Open Claude Desktop → Settings → Connectors
Click "Add Custom Connector"
Enter:
Name:
Figma Console (Read-Only)URL:
https://figma-console-mcp.southleft.com/sse
Click "Add" — Done! ✅
OAuth authentication happens automatically when you first use design system tools.
Claude Code
⚠️ Known Issue: Claude Code's native
--transport ssehas a bug. Usemcp-remoteinstead:
claude mcp add figma-console -s user -- npx -y mcp-remote@latest https://figma-console-mcp.southleft.com/sse💡 Tip: For full capabilities, use NPX Setup instead of Remote SSE.
Other Clients (Cursor, Windsurf, etc.)
{
"mcpServers": {
"figma-console": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://figma-console-mcp.southleft.com/sse"]
}
}
}Upgrading to Full Capabilities
Ready for design creation? Follow the NPX Setup guide above, or try Cloud Mode if you don't want to install Node.js.
☁️ Cloud Mode (Web AI Clients)
Best for: Using Claude.ai, v0, Replit, or Lovable to create and modify Figma designs — no Node.js required.
What you get: 105 tools including full write access — design creation, variable management, component instantiation, and all REST API tools. Only real-time monitoring (console logs, selection tracking, document changes) requires Local Mode.
Prerequisites
Figma Personal Access Token — Create one here (starts with
figd_)Figma Desktop with the Desktop Bridge plugin installed (see Desktop Bridge setup)
A web AI client that supports MCP (Claude.ai, Lovable, v0, Replit, etc.)
Step 1: Add the MCP Connector
Add this endpoint to your AI platform's MCP settings:
URL: https://figma-console-mcp.southleft.com/mcp
Auth: Your Figma PAT as Bearer token
In Claude.ai: Settings → Connectors → Add Custom Connector → paste the URL above. In Lovable/v0/Replit: Look for "Add MCP Server" or "Integrations" in settings → paste the URL and add your token.
Step 2: Pair the Plugin
Open the Desktop Bridge plugin in Figma Desktop (Plugins → Development → Figma Desktop Bridge)
Tell your AI assistant:
Connect to my Figma pluginThe AI gives you a 6-character pairing code (expires in 5 minutes)
In the plugin: Toggle "Cloud Mode" → enter the code → click Connect
You're paired! Full write access is now available
What You Can Do
Once paired, use natural language to design:
Create a card component with a header image, title, description, and action button
Set up a color token collection with Light and Dark modes
Add a "High Contrast" mode to my existing token collectionHow It Works
Your AI client sends write commands through the cloud MCP server, which relays them via WebSocket to the Desktop Bridge plugin running in your Figma Desktop. The plugin executes the commands using the Figma Plugin API and returns results back through the same path.
AI Client → Cloud MCP Server → Durable Object Relay → Desktop Bridge Plugin → FigmaVariables on any plan: Cloud Mode uses the Plugin API (not the Enterprise REST API), so variable management works on Free, Pro, and Organization plans.
📊 Installation Method Comparison
Feature | NPX (Recommended) | Cloud Mode | Local Git | Remote SSE |
Setup time | ~10 minutes | ~5 minutes | ~15 minutes | ~2 minutes |
Total tools | 130 | 105 after pairing | 130 (Local Git) | Read-only subset |
Design creation | ✅ | ✅ | ✅ | ❌ |
Variable management | ✅ | ✅ | ✅ | ❌ |
Component instantiation | ✅ | ✅ | ✅ | ❌ |
FigJam boards | ✅ | ✅ | ✅ | ❌ |
Real-time monitoring | ✅ | ❌ | ✅ | ❌ |
Desktop Bridge plugin | ✅ | ✅ | ✅ | ❌ |
Variables (no Enterprise) | ✅ | ✅ | ✅ | ❌ |
Console logs | ✅ (zero latency) | ❌ | ✅ (zero latency) | ✅ |
Read design data | ✅ | ✅ | ✅ | ✅ |
Requires Node.js | Yes | No | Yes | No |
Authentication | PAT (manual) | OAuth (automatic) | PAT (manual) | OAuth (automatic) |
Automatic updates | ✅ ( | ✅ | Manual ( | ✅ |
Source code access | ❌ | ❌ | ✅ | ❌ |
Key insight: Remote SSE is read-only. Cloud Mode adds write access for web AI clients without Node.js. NPX/Local Git give the full 130 tools.
🎯 Test Your Connection
After setup, try these prompts:
Basic test (all modes):
Navigate to https://www.figma.com and check statusDesign system test (requires auth):
Get design variables from [your Figma file URL]Cloud Mode test:
Connect to my Figma plugin→ Follow the pairing flow, then try: "Create a simple blue rectangle"
Plugin test (Local Mode only):
Show me the primary font for [your theme name]🔐 Authentication
Remote Mode - OAuth (Automatic)
When you first use design system tools:
Browser opens automatically to Figma authorization page
Click "Allow" to authorize (one-time)
Token stored securely and refreshed automatically
Works with Free, Pro, and Enterprise Figma plans
Local Mode - Personal Access Token (Manual)
Visit https://help.figma.com/hc/en-us/articles/8085703771159-Manage-personal-access-tokens
Generate token with scopes (all Read unless noted): File content, File versions, Library content, Library assets, Comments (Read and write), Current user, and Variables (Enterprise only, optional)
Add to MCP config as
FIGMA_ACCESS_TOKENenvironment variable
🛠️ Available Tools
Status & Diagnostics
figma_get_status- Check WebSocket bridge connection and file contextfigma_diagnose- Designer-readable health check + setup guidancefigma_reconnect- Force reconnect to the Desktop Bridge pluginfigma_navigate- Switch the active file target among connected plugins (Local), or navigate the cloud headless browser (Remote/Cloud)figma_list_open_files- List files connected through the Desktop Bridge and which one is active (Local Mode)
Console Debugging
figma_get_console_logs- Retrieve console logsfigma_watch_console- Real-time log streamingfigma_clear_console- Clear log bufferfigma_reload_plugin- Reload current page
Visual Debugging
figma_take_screenshot- Export an image of a page or node (Desktop Bridge first, REST fallback)figma_capture_screenshot- Render a node from the plugin runtime, reflecting changes that haven't reached the REST API yet
👁️ Real-Time Awareness (Local Mode only)
figma_get_selection- The nodes currently selected in Figmafigma_get_design_changes- Buffered document-change events, for polling what changed
Design System Extraction
figma_get_design_system_kit- Full design system in one call — tokens, components, styles, visual specsfigma_get_variables- Extract design tokens/variablesfigma_get_component- Get component data (metadata or reconstruction spec)figma_get_component_for_development- Component + imagefigma_get_component_image- Just the imagefigma_get_styles- Color, text, effect stylesfigma_get_file_data- Full file structurefigma_get_file_for_plugin- Optimized file datafigma_get_design_system_summary/figma_get_token_values- Compact design-system overview and variable values by mode (Local Mode only)figma_audit_design_system_report- Scored health audit for any MCP client — six-category report (naming, tokens, metadata, accessibility, consistency, coverage) with per-finding remediation ("can this MCP fix it?"), chunked per-category drill-down, live-first data with disclosed source, 5-minute cache
📚 Shared Library Inspection
figma_get_library_component_by_key- Resolve any component key to full properties + variants + visual specs — without needing the source library file's URL. Works for both COMPONENT_SET and standalone COMPONENT keys. Adaptive compression at >500KB.figma_get_library_components- Discover all components in a library file (requires library file URL/key)figma_get_library_variables- List every variable from team libraries the current file has subscribed. Works on every Figma plan — uses the Plugin API path, not the Enterprise-only REST endpoint. Filter bylibraryName,collectionName, orresolvedType.figma_import_library_variable- Import a library variable into the current file. Returns a localidready to pass tofigma_set_fills/figma_update_variable/ any variable-binding tool.
☁️ Cloud Relay
figma_pair_plugin- Generate a pairing code to connect a Desktop Bridge plugin via the cloud relay
✏️ Design Creation (Local Mode + Cloud Mode)
figma_execute- Power tool: Run any Figma Plugin API code to create designsCreate frames, shapes, text, components
Apply auto-layout, styles, effects
Build complete UI mockups programmatically
Optional
fileKeytargets one specific connected file directly (Local Mode only), without touching the active file or target lock
figma_execute_across_files- Local Mode only. Run the same script in several Desktop Bridge-connected files at once, concurrently, returning a per-file result map — for cross-file consistency checks and fixes across a multi-file design system, replacing "open file, run plugin, repeat per file"Name the files with
fileKeys(fromfigma_list_open_files), or passallFiles: trueto hit every connected file — one of the two is required, so a script never fans out to files you didn't mean to touchPer-file timeouts and error isolation: one slow or failing file doesn't delay or fail the others
figma_create_component_set- Create a component set with variants in one declarative callGenerate every variant combination from an axes matrix (e.g.
{ State: ["default", "hover", "disabled"], Size: ["sm", "lg"] }→ 6 variants) off a base component, or combine existing componentsProp=Valuevariant naming,combineAsVariantsunder the hood, optional auto-arranged labeled gridReturns each variant's key, ready for
figma_instantiate_component
figma_arrange_component_set- Organize variants into professional component setsConvert multiple component variants into a proper Figma component set
Applies native purple dashed border visualization automatically
Creates white container frame with title, row labels, and column headers
Row labels vertically centered with each grid row
Column headers horizontally centered with each column
Use natural language like "arrange these variants" or "organize as component set"
figma_set_description- Document components with rich descriptionsAdd descriptions to components, component sets, and styles
Supports markdown formatting for rich documentation
Descriptions appear in Dev Mode for developers
🧩 Figma Slots (Local Mode + Cloud Mode)
figma_create_slot- Add a slot to a component via the GAcreateSlot()API — the linked SLOT property is created automatically; works on standalone components and variants inside a component setfigma_get_slots- List slots on a component, component set (aggregated across variants), or instance — ids, names, property keys, dimensions, and current childrenfigma_append_to_slot- Populate an instance's slot by cloning an existing node or creating new content (setPropertiesrejects slot values by design — this is the population path)figma_reset_slot- Clear a slot's content on an instancefigma_add_slot_property- Retrofit an existing frame as a slot via a manual SLOT property binding, withdescriptionandpreferredValues
🎬 Motion (Local Mode + Cloud Mode)
Figma Motion (Plugin API beta). Animations play in Figma's preview and in video export, not in static screenshots.
figma_get_animations- Read a layer's animation styles, keyframe tracks and timeline, with CSS easings and token bindingsfigma_apply_animation- Animate a layer with a Figma preset (Opacity, Scale, Position, Rotation, Size, Path, TextStagger), a custom animation style, or manual keyframes for any animatable property, paint color or effect. Easing and duration can bind to EASING/TIMING variablesfigma_remove_animation- Remove one animation style, one keyframe track, or everythingfigma_manage_animation_styles- Build reusable motion styles: list Figma's presets and their options, and create, update or delete custom animation stylesfigma_export_animation- Export an animated frame as MP4, GIF or WebM
🧱 Code Layers (Local Mode + Cloud Mode)
figma_get_code_layers- Find Figma code layers on a page or across the file, with position, size and linked dev resources. Figma's APIs don't expose code-layer source, so creating and editing them stays in Figma or Figma's own MCP (send_code_to_figma)
✨ Shaders (Local Mode + Cloud Mode)
figma_list_shaders- List shaders applied in the file (with each property's name, type and default, and the layers using them) and shaders from your librariesfigma_apply_shader- Apply a shader or change its properties by name ({turbulence: 40, cloudColor: '#E8F4FF'}) on fills, strokes or effects, including variable bindings. Shaders themselves are created in Figma or with Figma's own MCP
📐 Layout (Local Mode + Cloud Mode)
figma_set_layout- Auto layout and grid layout in one call: direction, gaps, padding, alignment includingSPACE_EVENLY/SPACE_AROUND, wrap, sizing, and grid tracks written CSS-style ('240px 1fr 1fr',repeat(3, 1fr)) with child placement and spans
🔍 Design-Code Parity (All Modes)
figma_check_design_parity- Compare Figma component specs against code implementation, producing a scored diff report with actionable fix itemsfigma_generate_component_doc- Generate platform-agnostic markdown documentation by merging Figma design data with code-side info; the optionalhistoryparameter adds a changelog from Figma version history andgit log
🔬 Components, Nodes & Deep Analysis (Local Mode + Cloud Mode unless noted)
figma_search_components/figma_get_component_details- Find components (local + library) and get their variants, properties, and keys (Local Mode only)figma_instantiate_component/figma_set_instance_properties- Place instances and set their TEXT, BOOLEAN, INSTANCE_SWAP, and VARIANT propertiesfigma_add_component_property/figma_edit_component_property/figma_delete_component_property- Manage component propertiesfigma_create_child,figma_move_node,figma_resize_node,figma_clone_node,figma_rename_node,figma_delete_node,figma_set_text,figma_set_fills,figma_set_strokes,figma_set_image_fill- Structured node edits, including variable binding on fills and strokes, OKLCH/Display P3 and other CSS colors on fills and strokes, and text wrap style and variable-font axes on textfigma_get_component_for_development_deep- Full component tree with resolved token names and instance referencesfigma_analyze_component_set- A variant set as a state machine, with CSS pseudo-class mappings and per-variant diffs
♿ Accessibility (Local Mode + Cloud Mode)
figma_lint_design- WCAG and design-system lint on the canvas, with AA and best-practice level taggingfigma_audit_component_accessibility- Component scorecard: state coverage, focus indicators, color-blind simulationfigma_scan_code_accessibility- axe-core scan of HTML
📝 Annotations & Comments
figma_get_annotations/figma_set_annotations/figma_get_annotation_categories- Read and write designer annotations (Local Mode + Cloud Mode)figma_get_comments/figma_post_comment/figma_delete_comment- File comments, optionally pinned to a node
🕰 Version History
figma_get_file_versions/figma_get_file_at_version- List versions and snapshot a file or node at a past versionfigma_diff_versions/figma_get_changes_since_version- Structured diffs, including component property and binding changesfigma_generate_changelog- Markdown changelog for release notesfigma_blame_node- Find when, and by whom, a property or variant was introduced
🔁 Token Sync (Local Mode + Cloud Mode)
figma_export_tokens- Export Figma variables to design token files in your codebase. Canonical DTCG JSON (legacy hex dialect by default, or DTCG 2025.10 object colors/dimensions viadtcgDialect: "2025") plus CSS, Tailwind v4/v3, SCSS, TS, JSON, Style Dictionary, and Tokens Studio formats. Diff-aware merge against existing source files (only writes what changed).tokens.config.jsonautodiscovery means zero-arg calls after first setup. Scopes and codeSyntax metadata round-trip via$extensions. Replaces Style Dictionary and Tokens Studio's export pipeline for popular styling methods.figma_import_tokens- Push code-side token edits back to Figma with a full apply phase. Diffs against current Figma state, then applies value updates, creates missing collections/variables, applies renames, writes real alias (VARIABLE_ALIAS) references, and — only understrategy: "replace"— deletes Figma-only variables. Round-trip safe — Figma variable IDs preserved in DTCG$extensions["figma-console-mcp"]so renames on either side don't create duplicates. Accepts both DTCG dialects. Dry-run strategy for safe previews. In Cloud Mode, pass tokens inline viapayloadorfiles(no local filesystem access).
🧬 Design System Extraction (Local Mode only)
Turn a production codebase into a design system: analyze → extract tokens → scaffold → port components → verify. Local Mode only — these tools read and write your local filesystem, so they are never registered in Cloud Mode.
figma_ds_analyze- Scan one or more production app codebases — framework/styling/vendor-layer detection; a usage-ranked component inventory classified vendored / wrapped / pure-vendor / bespoke, with prop contracts, variant inference from real call sites, and duplicate detection; iconography + typography capture; and architecture classification (atomic levels, specializations likeFollowButton→Button, missing generic primitives — the "UI kit vs design system" analysis)figma_ds_extract_tokens- Mine the app's styling into DTCG tokens. Declared intent first — multi-mode CSS custom properties (.dark/[data-theme]and other conventions), SCSS variables, Tailwind config values, shadcn HSL triples — plus Tailwind utility-class frequency mining valued from the app's own theme, and frequency-promoted recurring raw values. Every token carries provenance (source file:line, confidence, frequency) in$extensions; the output imports straight into Figma variables viafigma_import_tokensfigma_ds_scaffold- Generate the design-system package — package skeleton, token files via the shared formatter engine, token/typography/iconography showcase docs pages, framework peer deps, and a workflow READMEfigma_ds_setup_storybook- Wire a freshly-initialized Storybook workshop to the extraction — a preview stylesheet carrying the source app's@thememapping, custom@utilitydefinitions,@layer base, and@font-facerules; self-hosted font copying; config patches (Tailwind vite plugin, automatic JSX runtime); and a theme toolbar built from the extracted modesfigma_ds_extract_component- Deep-extract one component for porting — source, prop contract, observed call-site variants, style touchpoints, and a ready-to-adapt CSF3 story scaffoldfigma_ds_verify- Deterministic fidelity evals — DTCG parse + alias integrity, quoted-CSS-expression scan, workshopvar()resolution, structure + porting coverage, and Figma round-trip readinessfigma_ds_status- Read or record porting progress, persisted across sessions
🔧 Variable Management (Local Mode + Cloud Mode)
figma_create_variable_collection- Create new variable collections with modesfigma_create_variable- Create COLOR, FLOAT, STRING, or BOOLEAN variablesfigma_update_variable- Update variable values in specific modesfigma_rename_variable- Rename variables while preserving valuesfigma_delete_variable- Delete variablesfigma_delete_variable_collection- Delete collections and all their variablesfigma_add_mode- Add modes to collections (e.g., "Dark", "Mobile")figma_rename_mode- Rename existing modesfigma_batch_create_variables- Create up to 100 variables in one call (10-50x faster)figma_batch_update_variables- Update up to 100 variable values in one callfigma_setup_design_tokens- Create complete token system (collection + modes + variables) atomically — values accept DTCG brace references ("{color.blue.600}") that resolve to real variable aliases
📌 FigJam Board Tools (Local Mode + Cloud Mode)
figjam_create_sticky- Create a sticky note with color optionsfigjam_create_stickies- Batch create up to 200 stickiesfigjam_create_connector- Connect nodes with labeled connector linesfigjam_create_shape_with_text- Create flowchart shapes (diamond, ellipse, etc.)figjam_create_table- Create tables with cell datafigjam_create_code_block- Add code snippets with syntax highlightingfigjam_create_section- Group board content in a sectionfigjam_auto_arrange- Arrange nodes in grid, horizontal, or vertical layoutsfigjam_get_board_contents- Read all content from a FigJam boardfigjam_get_connections- Read the connection graph (flowcharts, relationships)
🎞️ Slides Presentation Tools (Local Mode + Cloud Mode)
figma_list_slides- List all slides with IDs, positions, and skip statusfigma_get_slide_content- Get the full content tree of a slidefigma_get_slide_grid- Get the 2D grid layout of the presentationfigma_get_slide_transition- Read transition settings for a slidefigma_get_focused_slide- Get the currently focused slidefigma_create_slide- Create a new blank slidefigma_delete_slide- Delete a slide from the presentationfigma_duplicate_slide- Clone an existing slidefigma_reorder_slides- Reorder slides via new 2D grid layoutfigma_set_slide_transition- Set transition effects (22 styles, 8 curves)figma_skip_slide- Toggle whether a slide is skipped in presentation modefigma_add_text_to_slide- Add text to a slide with custom fonts, colors, alignment, and wrappingfigma_add_shape_to_slide- Add rectangle or ellipse shapes with colorfigma_set_slide_background- Set a slide's background color (creates or updates)figma_get_text_styles- Get all local text styles with IDs, fonts, and sizesfigma_set_slides_view_mode- Toggle grid vs. single-slide viewfigma_focus_slide- Navigate to a specific slide
📖 Example Prompts
Cloud Mode (Web AI Clients)
Connect to my Figma plugin so we can start designing
Pair with my Figma file and create a login form with email, password, and submit button
Set up a brand color token collection with Light and Dark modesPlugin Debugging
Navigate to my Figma plugin and show me any console errors
Watch the console for 30 seconds while I test my plugin
Get the last 20 console logsDesign System Extraction
Get all design variables from https://figma.com/design/abc123
Extract color styles and show me the CSS exports
Get the Button component with a visual reference image
Get the Badge component in reconstruction format for programmatic creationDesign Creation (Local Mode + Cloud Mode)
Create a success notification card with a checkmark icon and message
Design a button component with hover and disabled states
Build a navigation bar with logo, menu items, and user avatar
Create a modal dialog with header, content area, and action buttons
Arrange these button variants into a component set
Organize my icon variants as a proper component set with the purple borderVariable Management (Local Mode + Cloud Mode)
Create a new color collection called "Brand Colors" with Light and Dark modes
Add a primary color variable with value #3B82F6 for Light and #60A5FA for Dark
Rename the "Default" mode to "Light Theme"
Add a "High Contrast" mode to the existing collectionDesign-Code Parity
Compare the Button component in Figma against our React implementation
Check design parity for the Card component before sign-off
Generate component documentation for the Dialog from our design systemFigJam Boards
Create a retrospective board with "Went Well", "To Improve", and "Action Items" columns
Build a user flow diagram for the checkout process with decision points
Read this brainstorming board and summarize the key themes
Generate an affinity map from these meeting notes
Create a comparison table of our three platform optionsSlides Presentations
List all slides and tell me which ones are skipped
Add a new slide with the title "Thank You" in 72px text
Set a DISSOLVE transition on the first slide with 0.5 second duration
Duplicate slide 5 for an A/B comparison
Skip slides 8 and 9 — they're not ready for the client presentation
Reorder my slides so the conclusion comes before Q&AVisual Debugging
Take a screenshot of the current Figma canvas
Navigate to this file and capture what's on screen🎨 AI-Assisted Design Creation
Requires Desktop Bridge: This feature works with Local Mode (NPX or Local Git) and Cloud Mode. Remote SSE without Cloud Mode pairing is read-only and cannot create or modify designs.
One of the most powerful capabilities of this MCP server is the ability to design complete UI components and pages directly in Figma through natural language conversation with any MCP-compatible AI assistant like Claude Desktop or Claude Code.
What's Possible
Create original designs from scratch:
Design a login card with email and password fields, a "Forgot password?" link,
and a primary Sign In button. Use 32px padding, 16px border radius, and subtle shadow.Leverage existing component libraries:
Build a dashboard header using the Avatar component for the user profile,
Button components for actions, and Badge components for notifications.Generate complete page layouts:
Create a settings page with a sidebar navigation, a main content area with form fields,
and a sticky footer with Save and Cancel buttons.How It Works
You describe what you want in plain English
The AI searches your component library using
figma_search_componentsto find relevant building blocksComponents are instantiated with proper variants and properties via
figma_instantiate_componentCustom elements are created using the full Figma Plugin API via
figma_executeVisual validation automatically captures screenshots and iterates until the design looks right
Who Benefits
Role | Use Case |
Designers | Rapidly prototype ideas without manual frame-by-frame construction. Explore variations quickly by describing changes. |
Developers | Generate UI mockups during planning discussions. Create visual specs without switching to design tools. |
Product Managers | Sketch out feature concepts during ideation. Communicate visual requirements directly to stakeholders. |
Design System Teams | Test component flexibility by generating compositions. Identify gaps in component coverage. |
Agencies | Speed up initial concept delivery. Iterate on client feedback in real-time during calls. |
Example Workflows
Brand New Design:
"Create a notification toast with an icon on the left, title and description text, and a dismiss button. Use our brand colors."
The AI creates custom frames, applies your design tokens, and builds the component from scratch.
Component Composition:
"Build a user profile card using the Avatar component (large size), two Button components (Edit Profile and Settings), and a Badge for the user's status."
The AI searches your library, finds the exact components, and assembles them with proper spacing and alignment.
Design Iteration:
"The spacing feels too tight. Increase the gap between sections to 24px and make the heading larger."
The AI modifies the existing design, takes a screenshot to verify, and continues iterating until you're satisfied.
Visual Validation
The AI automatically follows a validation workflow after creating designs:
Create → Execute the design code
Screenshot → Capture the result
Analyze → Check alignment, spacing, and visual balance
Iterate → Fix any issues detected
Verify → Final screenshot to confirm
This ensures designs aren't just technically correct—they look right.
🎨 Desktop Bridge Plugin (Recommended Connection)
The Figma Desktop Bridge plugin is the recommended way to connect Figma to the MCP server. It communicates via WebSocket — no special Figma launch flags needed, and it persists across Figma restarts.
Setup
Open Figma Desktop (normal launch — no debug flags needed)
Go to Plugins → Development → Import plugin from manifest...
Select
~/.figma-console-mcp/plugin/manifest.json— the stable path the MCP server keeps up to date (npx figma-console-mcp --print-pathprints it; on macOS press ⌘⇧G in the dialog and paste it, since the folder is hidden). If you cloned this repo for development, you can selectfigma-desktop-bridge/manifest.jsonfrom the clone instead.Run the plugin in your Figma file — it auto-connects via WebSocket (scans ports 9223–9232)
Ask your AI: "Check Figma status" to verify the connection
One-time import. Once imported, the plugin stays in your Development plugins list. Just run it whenever you want to use the MCP.
📖 Desktop Bridge Documentation
Capabilities
Read Operations:
Variables without Enterprise API
Reliable component descriptions (bypasses API bugs)
Multi-mode support (Light/Dark/Brand variants)
Real-time selection tracking and document change monitoring
Write Operations:
Design Creation - Create frames, shapes, text, components via
figma_executeVariable Management - Full CRUD operations on variables and collections
Mode Management - Add and rename modes for multi-theme support
How the Transport Works
The MCP server communicates via WebSocket through the Desktop Bridge plugin
The server tries port 9223 first, then automatically falls back through ports 9224–9232 if needed
The plugin scans all ports in the range and connects to every active server it finds
All 130 tools work through the WebSocket transport
Multiple files: The WebSocket server supports multiple simultaneous plugin connections — one per open Figma file. Each connection is tracked by file key with independent state (selection, document changes, console logs).
Environment variables:
FIGMA_WS_PORT— Override the preferred WebSocket port (default: 9223). The server will fall back through a 10-port range starting from this value if the preferred port is occupied.FIGMA_WS_HOST— Override the WebSocket server bind address (default:localhost). Set to0.0.0.0when running inside Docker so the host machine can reach the MCP server.FIGMA_MCP_HTTP_PORT— Also serve MCP over Streamable HTTP athttp://127.0.0.1:<port>/mcp, so other local clients can share this server's Figma connection. Off by default. See Sharing one server over HTTP.FIGMA_MCP_HTTP_TOKEN— WithFIGMA_MCP_HTTP_PORT, requireAuthorization: Bearer <token>on every HTTP request.
Cloud Mode: The plugin also supports a Cloud Mode toggle for pairing with web AI clients (Claude.ai, v0, Replit, Lovable). Toggle "Cloud Mode" in the plugin UI, enter the 6-character pairing code from your AI assistant, and click Connect. See Cloud Mode for details.
Plugin Limitation: In Local Mode, works with NPX or Local Git. In Cloud Mode, pairs with the remote MCP endpoint. Remote SSE without Cloud Mode pairing is read-only.
🔀 Multi-Instance Support (v1.10.0)
Figma Console MCP now supports multiple simultaneous instances — perfect for designers and developers who work across multiple projects or use Claude Desktop's Chat and Code tabs at the same time.
The Problem (Before v1.10.0)
When two processes tried to start the MCP server (e.g., Claude Desktop's Chat tab and Code tab), the second one would crash with EADDRINUSE because both competed for port 9223.
How It Works Now
The server tries port 9223 first (the default)
If that port is already taken, it automatically tries 9224, then 9225, and so on up to 9232
The Desktop Bridge plugin in Figma connects to all active servers simultaneously
Every server instance receives real-time events (selection changes, document changes, console logs)
figma_get_statusshows which port you're on and lists other active instances
What This Means for You
Scenario | Before v1.10.0 | Now |
Two Claude Desktop tabs (Chat + Code) | Second tab crashes | Both work independently |
Multiple CLI terminals on different projects | Only one can run | All run simultaneously |
Claude Desktop + Claude Code CLI | Port conflict | Both coexist |
Do I Need to Do Anything?
Nothing. Multi-instance support is fully automatic:
Each MCP server claims the next available port in the range
The Desktop Bridge plugin scans all ports and connects to every active server
Orphaned processes from closed tabs are automatically cleaned up on startup
No manual port management — the plugin already scans the whole range
(Re-importing the manifest is only required when the plugin code itself changes — e.g. after a package update. Port-range scanning is already in the shipped plugin.)
Sharing one server over HTTP (optional)
Normally each MCP client starts its own server over stdio. To let several local clients share one server and its Figma connection, set FIGMA_MCP_HTTP_PORT. The server then also serves MCP at http://127.0.0.1:<port>/mcp, and lists that URL in its port file (mcpHttpUrl) and in figma_get_status (transport.mcpHttp).
# Start a shared server in a terminal (keep it open)
FIGMA_ACCESS_TOKEN=figd_... FIGMA_MCP_HTTP_PORT=9300 npx -y figma-console-mcp@latest
# Point clients at it, e.g. Claude Code:
claude mcp add --transport http figma-console-shared http://127.0.0.1:9300/mcpLoopback only. It binds
127.0.0.1and refuses requests whoseHostisn't localhost (DNS rebinding) or that come from a non-localhost browser page. SetFIGMA_MCP_HTTP_TOKENto also require a bearer token.Each client gets its own session, as with stdio, and all of them share the plugin connection. Idle sessions close after 30 minutes and clients reconnect automatically.
The endpoint lives as long as the server process. When an MCP client spawned the server, closing that client ends it.
Avoid port 3845, which Figma's own Dev Mode MCP server uses, and the bridge range 9223–9232.
🧩 MCP Apps (Experimental)
Figma Console MCP includes support for MCP Apps — rich interactive UI experiences that render directly inside any MCP client that supports the MCP Apps protocol extension. Built with the official @modelcontextprotocol/ext-apps SDK.
What are MCP Apps? Traditional MCP tools return text or images to the AI. MCP Apps go further — they render interactive HTML interfaces inline in the chat, allowing users to browse, filter, and interact with data directly without consuming AI context.
Token Browser
An interactive design token explorer.
Usage: Ask Claude to "browse the design tokens" or "show me the design tokens" while connected to a Figma file.
Features:
Browse all tokens organized by collection with expandable sections
Filter by type (Colors, Numbers, Strings) and search by name/description
Per-collection mode columns (Light, Dark, Custom) matching Figma's Variables panel
Color swatches, alias resolution, and click-to-copy on any value
Works without Enterprise plan via Desktop Bridge (local mode)
Design System Dashboard
A Lighthouse-style health scorecard that audits your design system across six categories.
Usage: Ask Claude to "audit the design system" or "show me design system health" while connected to a Figma file.
Features:
Overall weighted score (0–100) with six category gauges: Naming, Tokens, Components, Accessibility, Consistency, Coverage
Expandable category sections with individual findings, severity indicators, and actionable details
Diagnostic locations linking findings to specific variables, components, or collections
Tooltips explaining each check's purpose and scoring criteria
Refresh button to re-run the audit without consuming AI context
Pure scoring engine with no external dependencies — all analysis runs locally
No MCP Apps support? Same audit, plain tool: figma_audit_design_system_report runs the identical scoring engine and returns the report as data — summary by default, per-category drill-down via category, full JSON via format: "full" — with a remediation section stating which findings this MCP can fix (design), which need a design decision first (design-assisted), and which need human design work (manual). Works in every MCP client with no ENABLE_MCP_APPS flag; results cache for 5 minutes (forceRefresh to re-crawl).
Enabling MCP Apps:
MCP Apps are enabled by default in the setup configurations above (via "ENABLE_MCP_APPS": "true"). If you set up before v1.10.0 and don't have this in your config, add it to your env section:
"env": {
"FIGMA_ACCESS_TOKEN": "figd_YOUR_TOKEN_HERE",
"ENABLE_MCP_APPS": "true"
}Note: MCP Apps require an MCP client with ext-apps protocol support (e.g. Claude Desktop). This feature is experimental and the protocol may evolve.
Future MCP Apps Roadmap
Planned MCP Apps:
Component Gallery — Visual browser for searching and previewing components with variant exploration
Style Inspector — Interactive panel for exploring color, text, and effect styles with live previews
Variable Diff Viewer — Side-by-side comparison of token values across modes and branches
The architecture supports adding new apps with minimal boilerplate — each app is a self-contained module with its own server-side tool registration and client-side UI.
🚀 Advanced Topics
Setup Guide - Complete setup guide for all MCP clients
Self-Hosting - Deploy your own instance on Cloudflare
Architecture - How it works under the hood
OAuth Setup - Configure OAuth for self-hosted deployments
Troubleshooting - Common issues and solutions
🤝 vs. Figma's Official MCP Server
The two servers are complementary, and both can run in the same MCP client.
Figma's official MCP server is hosted by Figma. It focuses on design-to-code context (get_design_context), Code Connect, library search, and creating content in Figma: it writes through use_figma, creates files, generates FigJam diagrams, generates code layers, and works with shaders.
Figma Console MCP focuses on design-system operations:
Deterministic checks: design-code parity, accessibility (canvas and code), and design-system health
Token export in 10 formats and DTCG import with round-trip variable IDs
Variable reads and writes on any Figma plan through the Desktop Bridge plugin
Component documentation with design and code history, and version-history diffs
Codebase → design system extraction
Plugin console capture, selection tracking, and multi-file execution (Local Mode)
🛤️ Roadmap
Current Status: v1.46.0 (Stable) - Production-ready. Latest: shaders applied with properties set by name, figma_set_layout for auto layout and grid layout, OKLCH/Display P3 and other CSS colors on fills and strokes, and text wrap style and variable-font axes in figma_set_text (server-only). On top of v1.45.1's figma_get_code_layers no longer hangs on a file in a background window, and the tool docs were audited against every tool's real parameters (server-only). On top of v1.45.0's Motion tools — apply, read, remove and export Figma Motion animations, manage custom animation styles, write Timing and Easing variables from token files, and find code layers (server-only). On top of v1.44.2's Cloud sign-in requests library_assets:read, so component lookups by key work over OAuth (server-only). On top of v1.44.1's Cloud Mode accepting personal access tokens without the Current user scope, 403 errors name the missing scope, and setup guides for Codex, Gemini CLI and Antigravity (server-only). On top of v1.44.0's opt-in Streamable HTTP endpoint for Local Mode (FIGMA_MCP_HTTP_PORT, loopback only, optional bearer token) so several local clients share one server and its Figma connection (server-only). On top of v1.43.0's @modelcontextprotocol/sdk 1.32.1 and zod 4 clear all seven production security advisories, with tool behavior unchanged and Gemini-safe schemas (server-only). On top of v1.42.1's commands to a plugin stuck on a timed-out script fail fast with a busy message instead of queuing behind it, port-exhaustion eviction ends the least recently used server instead of the oldest, and figma_execute accepts up to a 300 s timeout (server-only). On top of v1.42.0's figma_get_comments returning compact threads (root + replies, newest activity first) with node_id, thread_id and since filters and limit/offset paging, 30 threads by default; summary counts are per thread (server-only, PR #139). On top of v1.41.5's component-set analysis reporting gradient/image/paint-opacity, corner radius, typography and label text, swapped spacing tokens, nested layer geometry and vector shape changes (re-import the plugin). On top of v1.41.4's variant background/stroke and auto-layout changes. On top of v1.41.3's component-set analysis reporting changes inside nested layers (instance swaps, nested token changes, opacity on the variant itself) and no longer reports a layer hidden in every variant as a change (re-import the plugin). On top of v1.41.2's design-system summary and figma_get_token_values report the file's tokens (they always reported 0) (server-only). On top of v1.41.1's component-set analysis reports real variant differences (Figma's default variant, size and layer changes), component loading no longer times out on large files (throttled plugin timers), relevance-ranked component search, and figma_get_variables paging that works with format: "full" (re-import the plugin for the component fixes). On top of v1.41.0's Cloud Mode sign-in hardening (per-session tokens on /sse, single-use authorization codes bound to client, redirect URI and PKCE, a consent page for unrecognized destinations), a script-execution fix in the accessibility scanner, figma_import_tokens refusing empty imports and scoping replace deletes to imported collections, figma_arrange_component_set no longer deleting other arranged sets, live variable reads for token export/import, Windows orphan-server exit (PR #140), and fileKey for the Slots tools (PR #112) (server-only, no plugin re-import). On top of v1.40.9's composed colors (a color variable set to another color at an opacity, "grey/900 at 50%") export and import with the link to the primitive intact — color-mix() in CSS/Tailwind v4, rgba() in SCSS, an alpha modifier in Tokens Studio, the resolved color plus the composition in DTCG — where the export previously failed or wrote [object Object] (server-only, no plugin re-import). On top of v1.40.8's min/max width and height survive every way of extracting a component as JSON — the design system kit, the reconstruction format and figma_get_file_data now carry them, design-code parity compares them, and the reconstruction format returns real geometry again instead of 50×50 placeholders when the plugin is connected (server-only, no plugin re-import). On top of v1.40.7's clearer Color Tokens table in generated docs — layers revealed by a boolean property are printed once under that property, and stroke/fill rows name the nested instance they belong to (server-only, no plugin re-import). On top of v1.40.6's overrides in extended variable collections are visible (previously reported as nonexistent), and a third round of generated-doc fidelity fixes — radius tokens read per corner, boolean props compared in Design-Code Parity, source links pinned to a commit, hidden layers linked to the property that shows them (server-only, no plugin re-import). On top of v1.40.5's clean dependency audit for the npm package — Worker-only dependencies (@cloudflare/puppeteer, which pulled in a high-severity extract-zip advisory with no upstream fix, and agents) no longer install for npm users, so npm install figma-console-mcp audits at 0 vulnerabilities and is 64 MB instead of 173 MB; the server also reports its real version to MCP clients instead of 0.1.0 (server-only, no plugin re-import). On top of v1.40.4's fixes found by live-testing v1.40.3 on hard production components — tools given a fileUrl now read variables, descriptions and annotations from THAT file rather than whichever file is active (previously every token name could vanish, or on an id collision come from the wrong file; figma_get_component could return a different component), a tool result over 16 MB no longer disconnects the server, anatomy labels sizing by the layout's real axes, and the icon/typography/anatomy output stays readable on large components (server-only, no plugin re-import). On top of v1.40.3's fidelity fixes for generated component docs on harder components — hidden layers are labeled instead of documented as rendered, one-sided borders report the weight that actually renders, typography and layer structure are compared across every variant instead of read from the first, gradients/shadows/opacity are no longer silently dropped, truncated trees say so, and SLOT properties are listed (server-only, no plugin re-import). On top of v1.40.2's data-loss fix for figma_export_tokens — with a different file active in Figma than intended, an export could replace a real token file with an empty one (or with another file's tokens) and report success; exports now refuse to write when a requested collection is missing, when the export is empty, when the target was generated from a different Figma file, or when overwriting would destroy tokens the export doesn't manage, and strategy: "merge" — documented as preserving code-only tokens but never implemented — is now a genuinely safe default (server-only, no plugin re-import). On top of v1.40.1's accuracy fixes for generated component docs across variants — a descendant's fill (typically an icon's) could be documented as a variant's Background, Color Token headings kept only a property literally named Variant, spacing was read from the first variant alone, and icons were only detected by layer name — plus figma_export_tokens accepting a file path as outputPath instead of failing with a raw EEXIST or silently creating a directory (server-only, no plugin re-import). On top of v1.40.0's design system extraction from production codebases — seven Local-Mode figma_ds_* tools that scan one or more apps (framework/styling/vendor detection, usage-ranked component inventory classified vendored/wrapped/pure-vendor/bespoke, variant inference from real call sites, duplicate detection, and an architecture pass separating UI-kit specializations from the missing generic primitives), mine the de-facto styling into DTCG tokens with per-token provenance (multi-mode CSS custom properties, SCSS, Tailwind config, shadcn HSL triples, utility-class frequency mining valued from the app's own theme), scaffold the design-system package with showcase docs pages, wire a fresh Storybook workshop to the app's real theme layers and fonts, deep-extract components for porting with CSF3 story scaffolds, verify with deterministic fidelity evals, and persist porting progress across sessions — the extracted tokens import straight into Figma variables via figma_import_tokens. On top of v1.39.1's fix for a plugin-update banner that could never be cleared — an older server instance nagging a newer plugin to re-import, which only ever installs the same or a newer plugin. On top of v1.39.0's multi-file execution — figma_execute_across_files runs one script against several Desktop Bridge-connected files concurrently (four files x 2s of work in ~3s, not ~8s), and figma_execute takes an optional fileKey to target a single file without moving the active file or releasing target lock; targeting must be explicit (fileKeys or allFiles: true), so nothing fans out to files you did not name. From community PR #107 by @Wolfr. Ships with a relay fix: handleResult() in the plugin's ui.html rebuilt each response field by field and silently dropped resultAnalysis and fileContext, so the resultAnalysis.warning check that figma_execute's own description tells callers to perform has never been possible (re-import manifest.json for those two fields; everything else works without it). On top of v1.38.2's connection-stability fix — the server's own orphan reaper was terminating healthy MCP servers because its liveness probe used an IPv4 literal while the server binds the IPv6 loopback, which turned every kill-safety gate into a rubber stamp; this was the cause of recurring "Server disconnected" errors across all MCP clients. Alongside v1.38.1's fix for the shared-library variable tools, which had silently reported zero collections since v1.29.0 and reported failed imports as successes. On top of v1.38.0's ongoing component changelogs in generated docs — figma_generate_component_doc takes an opt-in history parameter that pulls per-component design history from Figma version history (each version diffed and scoped to that component, so renames, added properties, and token bindings show up as rows) alongside code history from git log on the component's source files, rendered as a ## History section with design, code, and release-note tables. Prefers labeled versions, falls back to auto-saves when a file has none, and is off by default so existing calls are unchanged (server-only, no plugin re-import). On top of v1.37.x's design-system health audit for every client — figma_audit_design_system_report runs the dashboard's deterministic six-category scoring engine and returns the report as data with per-finding remediation, live-first fileKey-verified data (source disclosed), chunked per-category drill-down, and a 5-minute cache (server-only, no plugin re-import). On top of v1.36.0's target lock for multi-file parallel work — — figma_navigate takes a lock: true flag that pins the active file so an AI agent can work in one file while you work in another without commands routing to the wrong file. On top of v1.35.0's Figma Slots write support — create, inspect, populate, and reset Slots (GA at Config 2026) via 5 new tools (figma_create_slot, figma_get_slots, figma_append_to_slot, figma_reset_slot, figma_add_slot_property), live-validated against the GA Plugin API and based on community PR #77. On top of v1.34.0's Bidirectional Token Sync v2 + DTCG 2025.10 — figma_import_tokens applies the complete diff plan (creates missing collections/variables, applies renames, writes real VARIABLE_ALIAS references, and deletes only under explicit replace), figma_export_tokens speaks the DTCG 2025.10 dialect on request (legacy default byte-identical), variable scopes/codeSyntax round-trip via $extensions, figma_setup_design_tokens accepts alias values via DTCG brace references, and figma_create_component_set builds a full variant set from an axes matrix in one call. On top of the v1.33.x line: version-handshake fix (re-import banner only fires when plugin files actually changed), security dependency sweep, and the v1.33.0 connection UX overhaul (honest status pill derived from live connection state, /health auto-discovery with self-healing reconnect) + a 33-fix full-codebase audit (lossless DTCG multi-mode round-trips, cross-collection alias resolution, branch-URL correctness across REST tools, cache-poisoning and CSWSH fixes, bridge-first screenshots). Built on WCAG-accurate accessibility auditing (line height below 1.5× is no longer mis-flagged as a failure; readability hints decoupled from conformance checks and scoped to multi-line text; code-side WCAG 1.4.12 check), a self-healing Desktop Bridge connection (zombie-process reaper + auto-reconnect watchdog — fixes the recurring "not connected until restart" bug), native variable binding on fills/strokes + typography control in the write tools, shared-library inspection (key-based component resolution + library variable read/import without Enterprise plan), 10-format token export pipeline (DTCG, CSS, Tailwind v4, Tailwind v3, SCSS, TS module, JSON flat/nested, Style Dictionary v3, Tokens Studio), bidirectional Figma↔code token sync, version history & time-series awareness, FigJam + Slides support, Cloud Write Relay, Design System Kit, WebSocket-only connectivity, smart multi-file tracking, 130 tools (Local) / 105 tools (Cloud) / read-only subset (Remote), Comments API, cross-MCP identity disambiguation, and MCP Apps.
Recent Releases:
v1.46.0 -
figma_list_shaders,figma_apply_shader(properties by name),figma_set_layout(auto layout and grid), CSS colors on fills/strokes, text wrap and variable-font axes (#150). Server-only.v1.45.1 -
figma_get_code_layersno longer hangs on background-window files (#149); tool docs audited against real parameters (#151). Server-only.v1.45.0 - Motion tools (apply, read, remove, export MP4/GIF/WebM, custom animation styles), Timing/Easing token import and writes, easing export fix, and
figma_get_code_layers(#147). Server-only.v1.44.2 - Cloud sign-in requests
library_assets:read; component lookups by key work over OAuth. Server-only.v1.44.1 - Cloud Mode accepts PATs without
current_user:read; 403s name the missing scope; complete token scopes and Codex/Gemini CLI/Antigravity setup. Server-only.v1.44.0 - Opt-in Streamable HTTP endpoint for Local Mode (
FIGMA_MCP_HTTP_PORT) so local clients can share one server (#48). Server-only.v1.43.0 -
@modelcontextprotocol/sdk1.32.1 andzod4: 0 production advisories (#141). Server-only.v1.42.1 - Fail fast while the plugin is stuck on a timed-out script (#94); evict the least recently used server, never one in use (#69);
figma_executetimeout up to 300 s. Server-only.v1.42.0 -
figma_get_commentscompact threads with node/thread/date filters and paging, 30 threads by default (PR #139 by @OAPrilepa). Server-only.v1.41.5 - Component-set analysis diffs paints (gradients, images, opacity), corner radius, typography and label text, swapped tokens (
tokens), nested size/position/rotation and vector shapes. Plugin re-import.v1.41.4 - Component-set analysis diffs the variant's own fill/stroke (button backgrounds) and auto-layout (
layout). Plugin re-import.v1.41.3 - Component-set analysis diffs nested layers by path (instance swaps, nested fill/stroke tokens), variant-level opacity, and visibility in both directions; a layer hidden in every variant is no longer reported as a change. Plugin re-import.
v1.41.2 - Design-system summary and token values read the bridge's variables response correctly (always 0 tokens before). Server-only.
v1.41.1 - Component-set analysis finds Figma's default variant and diffs size/layers (#121); component loading drops throttled setTimeout yields and uses native search — 300s timeouts → ~1.5s (#120); summary fails loudly; search ranked by relevance;
figma_get_variablesfull-format paging and one pagination shape (#98, #99); deep extraction mixed-text fix and unlimited depth (PRs #85, #86 by @DarWiM). Plugin re-import for component fixes.v1.41.0 - Security & data-safety. Cloud Mode:
/ssesessions use their own token (a shared slot let REST calls run with another user's token), authorization codes are random/single-use/10-minute and bound to client_id + redirect_uri + PKCE S256, unregistered redirects refused, consent page for other registered destinations, callback error page escaped. Local: accessibility scan no longer executes scanned scripts;figma_import_tokensrefuses 0-token imports and scopesreplacedeletes to imported collections;figma_arrange_component_setreplaces only its own set's arrangement; token export/import read variables live; stdin-EOF exit (PR #140 by @RomanOdokienko); SlotsfileKey(PR #112 by @Wolfr); batch-create aliases. Server-only. Reported in #104, #122, #53, #91, #116.v1.40.9 - Composed colors (color variable = another color at an opacity): export keeps the link in CSS/Tailwind v4/SCSS/Tokens Studio/DTCG and the resolved color elsewhere; import writes the composition back; resolver, audit, contrast and token-browser fixes; aliased colors no longer read as black in the design-system summary. Server-only. Reported by Isabella Minzly.
v1.40.8 - Min/max sizing in every JSON extraction path (design system kit, reconstruction format,
figma_get_file_data, component docs) and in design-code parity; reconstruction reads the full REST tree with real geometry, alignment, hidden layers and absolute positioning;nodeIdshonored by the file-data tools; Cloud Modefigma_diagnoseon/mcp. Server-only. Reported by Brett Cooper.v1.40.7 - Color Tokens readability: a layer shown by a boolean property is printed once under that property when identical across variants (kept per variant when it differs); paints on nested instances carry the instance's variant, and same-named fills/strokes are qualified by instance. Server-only. Reported by Robin Di Capua.
v1.40.6 - Extended collections + doc fidelity.
figma_get_variablesreads extended variable collections (overrides live on the collection; they were invisible and reported as nonexistent) — summary, per-collection resolved values marked overridden/inherited, per-variable overrides; the mode filter no longer drops0/falsevalues;figma_export_tokensexplains instead of emitting empty sets.figma_generate_component_doc: radius and per-side stroke bindings read per corner/side, Design-Code Parity compares booleans and never prints an empty section, source links pinned to a commit (no raw relative paths, no local paths, credentials stripped), hidden layers linked to the boolean that shows them, same-named layers qualified by instance. Server-only. Reported by Brett Cooper and Robin Di Capua.v1.40.5 - Clean dependency audit.
@cloudflare/puppeteer(→@puppeteer/browsers→extract-zip, high, no upstream fix) andagentswere regular dependencies but are only used by the Cloudflare Worker; they are now devDependencies and the Worker build is excluded from the npm package, so a fresh install audits at 0 vulnerabilities (was 4 high) and drops from 173 MB to 64 MB. The local server now reports its real version to MCP clients instead of0.1.0. A new test guards both directions of the dependency split. Server-only. Reported by Daniel Westerlund.v1.40.4 - Live-test fixes. Tools given a
fileUrl(figma_generate_component_doc,figma_get_component,figma_get_component_for_development) read bridge data from the ACTIVE file instead of the named one — token names vanished, and on an id collision another file's names, description, annotations or even component were returned; they now target the named file and fall back to REST. A tool result over 16 MB disconnected the server for the session (the client closes the transport); results are now size-capped centrally with an actionable error. Anatomy sizing labels follow the real layout axes (vertical layouts were mislabeled); icons are grouped, counted and named by the glyph in the slot; typography rows are identified by (element, style); identical sibling layers collapse to×N. Found by testing on hard production components. Server-only.v1.40.3 - Component-doc fidelity on harder components.
figma_generate_component_doc: hidden layers labeled rather than documented as rendered; border width honorsindividualStrokeWeights(a tab underline is4px bottom, not the vestigial scalar) and is reported only where a stroke is painted; typography and anatomy compared across every variant (an Applies to column; one tree per distinct layer structure) instead of read from the first; gradients, images, shadows, blurs and opacity reported instead of dropped; fetch depth raised from 4 to 8 with an explicit note when a tree may be cut off; boolean-valued variant properties keep their name; Configurable Properties renders for variant-only sets and listsSLOTproperties; every icon shown, not just the first; Design-Code Parity compares property values (it could report a property name as a missing variant); placeholderstatus/version/description no longer asserted. Server-only. Reported by Robin Di Capua.v1.40.2 - Token export data-loss fix.
figma_export_tokensreads from whichever file is active in Figma Desktop; with the wrong one focused it could overwrite a real token file with an empty document — or, for CSS/SCSS/Tailwind/TS outputs, with another file's tokens — and reportsuccess: true. Exports now refuse (writing nothing) when a requested collection isn't in the file that was read, when the export is empty, when the target was generated from a different Figma file (generated files now record their source), when a DTCG target can't be parsed or would be replaced by a different kind of output, or when overwriting would destroy hand-added tokens or another collection's tokens.strategy: "merge"had been documented as preserving code-only tokens but was never implemented; it is now the safe default andreplaceis the explicit override. Every response reports thesourceFigma file. Server-only. Reported by Isabella Minzly; two further loss paths found in code review.v1.40.1 - Component-doc variant accuracy + token export file paths.
figma_generate_component_doc: Background now comes only from the variant's own fills (a transparent outline/ghost variant no longer borrows its icon's color), Color Token headings name every variant property under any property names, Spacing Tokens are compared across all variants (varies by **Size**: …, with a Spacing Inconsistencies list for properties tokenized on some variants and hardcoded on others), and icons resolve from the main component andINSTANCE_SWAPslots rather than a layer name containing "icon".figma_export_tokens: anoutputPaththat is an existing file or ends in a token-file extension is written as that exact file; multi-file exports into a file path are rejected before anything is written.figma_search_componentsno longer reports a failed component load as a successful empty search. Server-only. Reported by Robin Di Capua and Isabella Minzly.v1.40.0 - Design System Extraction. Seven new Local-Mode-only tools that turn a production codebase into a design system, plus the supporting extraction engine.
figma_ds_analyzescans one or more app codebases: framework/styling/vendor-layer detection (React/Next/Angular/Web Components; Tailwind v3/v4, CSS Modules, SCSS, Emotion, styled-components; shadcn/ui, Radix, MUI, Chakra…), a usage-ranked component inventory classified vendored/wrapped/pure-vendor/bespoke with prop contracts, variant inference from real call sites, duplicate detection, iconography + typography capture, and an architecture classification separating a UI kit from a design system (atomic levels, specializations like FollowButton → Button, missing generic primitives).figma_ds_extract_tokensmines de-facto styling into DTCG tokens — multi-mode CSS custom properties across.dark/[data-theme]conventions, SCSS variables, Tailwind config values, shadcn HSL triples, Tailwind utility-class frequency mining valued from the app's own theme, frequency-promoted raw values — with per-token provenance in$extensions, importable straight into Figma variables viafigma_import_tokens.figma_ds_scaffoldgenerates the package (token files via the shared formatters, token/typography/iconography showcase pages);figma_ds_setup_storybookwires a fresh Storybook workshop to the app's real theme layers and fonts;figma_ds_extract_componentproduces per-component porting manifests with CSF3 story scaffolds;figma_ds_verifygates the result with deterministic fidelity evals plus Figma round-trip readiness;figma_ds_statuspersists porting progress across sessions. Also fixes the CSS/SCSS/Tailwind v4 formatters quoting CSS functional expressions (a quotedcubic-bezier(...)silently kills transitions — affectsfigma_export_tokenstoo). Server-only, no plugin re-import.v1.39.1 - Plugin update banner could never be cleared.
computePluginUpdateAvailable()was a bare inequality with no direction check, so a server whose bundled plugin copy was OLDER than the connected plugin still told the user to re-import — which only ever installs the same or a newer plugin. Not an edge case: the 9223–9232 port range keeps several server instances alive,BUNDLED_PLUGIN_VERSIONis parsed once at module load, and every server left running from before an upgrade nags a correctly-updated plugin. Reproduced live with four leftover v1.38.2 servers against a freshly re-imported 1.39.0 plugin. Now flags only when the bundled copy is genuinely newer. Server-only, no plugin re-import. 1452 tests.v1.39.0 - Multi-file execution. New
figma_execute_across_filesruns one script against several Desktop Bridge-connected files concurrently, with per-file error isolation and independent timeouts (verified live: four files × 2s of work in ~3.0s, all dispatches within 5ms — versus ~8s serialized).figma_executegained an optionalfileKeyto target a single non-active file without moving the active file or releasing target lock. Targeting is deliberately explicit —fileKeysorallFiles: true, no fan-out-to-everything default — because this runs arbitrary code in files you may be actively editing, including one pinned by target lock. The transport was already concurrent (sendCommandhas always taken a target file key, and every hop is request-id keyed); only the tool layer was missing. Community PR #107 by @Wolfr. Also fixes a Desktop Bridge relay bug that silently droppedresultAnalysisandfileContextfrom everyfigma_executeresponse since they were introduced — making theresultAnalysis.warningcheck the tool's own description tells callers to perform impossible — guarded now by a test that reads the real plugin files. Re-importmanifest.jsonfor those two fields; the rest works without it, and mixed plugin versions degrade cleanly. 52 suites / 1443 tests.v1.38.2 - Connection stability: the orphan reaper was terminating healthy MCP servers, the cause of recurring "Server disconnected" errors across every MCP client (reproduced in both Claude Code and Claude Desktop; unrelated to the Desktop Bridge plugin). The reaper probes a sibling's
/healthbefore deciding it is dead, but requested127.0.0.1while the WebSocket server bindslocalhost— resolved to the IPv6 loopback on dual-stack macOS, with nothing on IPv4 — so the probe reported "nothing responding" for healthy servers and every kill-safety gate built on it became a rubber stamp, including the one written to spare siblings after the machine sleeps. Three supporting defects: port files written non-atomically (a reader landing mid-rewrite got a parse error that both cleanup paths treated as "corrupt, delete it", stranding a healthy server), an orphan path that terminated fileless port-holders without probing at all, and a heartbeat that gave up permanently once its own file went missing. Fixes: probelocalhost, atomic temp+rename writes, never delete on a parse failure, health-probe before the orphan kill in both paths, and self-healing re-advertisement guarded by in-process port ownership. Fully restart MCP clients after upgrading — older running builds keep the broken probe and still terminate healthy siblings. Server-only, no plugin re-import. 1422 tests (7 new regressions, each verified to fail pre-fix).v1.38.1 - Shared-library variable tools fixed.
figma_get_library_variablesreturnedtotalCollections: 0for every file, on every plan, since it shipped in v1.29.0, andfigma_import_library_variablereported failed imports as successes withid: undefined. Both read the Desktop Bridge's{ success, result }envelope as if it were the injected script's bare return value, soArray.isArray()was always false, the__errorguard was dead code, and.idwas always undefined. The failure presented as a success with a plausible hint attached ("subscribe a library via the Assets panel"), which is why it survived two months unreported. Both tools now unwrap through a shared helper that also maps a bridge-levelsuccess: falseonto the error path, so a plugin timeout surfaces as a real error instead of being swallowed as "0 collections"; an import yielding noidis now an explicit error. All 26executeCodeViaUIcall sites audited — only these two were affected. Test mocks had encoded a wire contract that does not exist, which is why CI stayed green; they now reproduce the real envelope, plus six regression tests verified to fail against the pre-fix source. Reported by Isabella Minzly. Server-only — no plugin re-import needed.v1.38.0 - Ongoing component changelogs in generated docs.
figma_generate_component_docgained an opt-inhistoryparameter that produces a real changelog instead of only echoing hand-writtencodeInfo.changelogrows:history.figmawalks Figma version history and diffs each consecutive pair scoped to the component (reusing the same engine asfigma_diff_versions, so a rename, a newly added component property, or a token binding each become a row), whilehistory.gitrunsgit logover the component's source files auto-derived fromcodeInfo.filePath/sourceFiles[]. Labeled versions are preferred but auto-saves are used automatically when a file has none — verified against a mature system with 72 auto-saves and 0 labeled versions, where a labeled-only walk yields nothing. Detailed-mode bindings group by property (binding one token across a 24-variant set otherwise produced 44 near-identical bullets in a single table cell). Both sources default off, so existing callers get byte-identical output. No new tools; server-only, no plugin re-import.v1.37.0 - Design-system health audit for every MCP client. New
figma_audit_design_system_reportruns the Design System Dashboard's deterministic scoring engine (naming, token architecture, component metadata, accessibility, consistency, coverage) and returns the scored report as data — no MCP Apps support orENABLE_MCP_APPSneeded (the previous registration gated everything, making the audit unreachable outside Claude Desktop). Component data is now live-first: a fileKey-verified per-page bridge crawl (30s/page, failures isolated per page) with REST published-library fallback, and the chosen source is disclosed in the report (bridge-live/rest-published/none) so stale-publish scores can't masquerade as live ones. Output is token-safe by design: bounded summary, per-category chunked drill-down, clamped full JSON, 5-minute raw-data cache. Every finding carries a remediation verdict — auto-fixable by this MCP's write tools, fixable after a design decision, or manual — with the exact tools named. Scoring accuracy pass: variant components no longer poison PascalCase/casing checks, Title Case accepted, component-set names count toward core-component coverage,color/content/*recognized in contrast pairing, state synonyms (active≈pressedetc.), and./_-prefixed internals excluded. Server-only — no plugin re-import needed.v1.36.0 - Target lock for multi-file parallel work.
figma_navigategains alock: trueflag that pins the active file — new connections, reconnects, and the user's own selection/page changes in other files no longer move the command target, so an agent can safely write to one file while the user works in another. Auto-releases when the pinned file disconnects or navigates away;figma_list_open_filesreports atargetLockedflag for pre-write guards. Server-only — no plugin re-import needed.v1.35.0 - Figma Slots write support, closing #29 (the tracker's most-requested feature) via community PR #77 by @simonesalvucci, updated to the GA API. Five new tools:
figma_create_slot(slot + auto-linked SLOT property; variants inside component sets supported — the beta restriction was lifted at GA),figma_get_slots,figma_append_to_slot(clone or create content into instance slots; snaps clones to the slot origin),figma_reset_slot, andfigma_add_slot_property(retrofit an existing frame as a slot). Hardened by live validation: VARIANTdefaultValuepassthrough restored (Figma requires non-empty), destructive-path reorder in the append handler (content validated beforeclearExistingempties anything), relay whitelist fix forslotpayloads. Plugin re-import required (code.js+ui.htmlchanged).v1.34.0 - Bidirectional Token Sync v2 + DTCG 2025.10.
figma_import_tokensnow applies the complete diff plan: missing collections and variables are created (with modes, inferred/recorded types, and values set in dependency order — aliases in a second pass), token-path renames route to the update phase by round-trip variable ID (no more create+delete pairs that would permanently destroy the original underreplace), reference values write real{ type: "VARIABLE_ALIAS", id }payloads via a four-tier resolver, and deletes are strictly gated behindstrategy: "replace".figma_export_tokensgainsdtcgDialect: "2025"(object-form colors from full-precision floats, object dimensions) while the legacy default stays byte-identical; import accepts both dialects unconditionally with dialect-insensitive diff normalization. Variablescopes+codeSyntaxround-trip through$extensions["figma-console-mcp"].figma_setup_design_tokensaccepts DTCG brace references ("{color.blue.600}") that resolve to real aliases, including forward references. New toolfigma_create_component_setbuilds a variant set from an axes matrix (or combines existing components) withProp=Valuenaming, optional auto-arranged grid, and variant keys in the response — with count-scaled timeouts and rollback on failure. Plugin re-import required (code.js+ui.htmlchanged — the component-set handler and relay). 183 tests across the token/write-tools suites.v1.33.2 - Version-handshake false-positive fix. The v1.33.0 handshake compared the plugin's reported version against the server's package version, so server-only releases (like the v1.33.1 dependency sweep) flagged every up-to-date plugin as stale and pushed the re-import banner for files that hadn't changed. The server now compares against the
PLUGIN_VERSIONembedded in thefigma-desktop-bridge/code.jsit ships — exactly what a re-import would install — andPLUGIN_VERSIONitself now means "last release in which plugin files changed" (release tooling bumps it only whenfigma-desktop-bridge/actually changed since the last tag).figma_get_statusgainstransport.websocket.bundledPluginVersion;figma_diagnoseblames the right version. No new tools, no plugin re-import required (one-time exception: if you re-imported at v1.33.1, the banner appears once more — clear it with one final re-import). 1245 tests passing (9 new).v1.33.1 - Security dependency sweep. All runtime and critical npm audit alerts resolved via in-range bumps (
ws8.21.0,hono4.12.27,undici7.28.0,handlebars4.7.9 — the lone critical, dev-only — pluslodash,path-to-regexp,basic-ftp,fast-uri,vite).wranglerdeliberately held at 4.72.0 because newer versions require Node ≥22; the only residual audit findings are inside wrangler/miniflare's dev-time toolchain, which never ships in the npm package or Worker bundle. Supersedes dependabot PRs #81/#82/#84. No code changes, no API changes, no plugin re-import. 1236 tests passing unchanged.v1.33.0 - Connection UX overhaul + full-codebase audit. The plugin's status pill now derives from live connection state instead of Figma's variables loading (it used to glow green with zero MCP servers connected); HTTP
/healthauto-discovery reconnects restarted servers automatically (including one-dead-among-live, previously a permanent dead end); a version handshake banners the plugin UI when a re-import is needed and surfaces the mismatch infigma_get_status/figma_diagnose; cloud pairing config survives plugin reopen and its status line is derived + labeled (no more orphaned "Disconnected" under a green pill); all plugin copy is designer-language. The audit fixed 33 verified issues: lossless DTCG multi-mode round-trips, set-qualified cross-collection aliases, TIMING/EASING mapped to DTCGduration/cubicBezier, two cache-poisoning bugs (the "search returns 0 components" reports), a CSWSH origin bypass (startsWith→ exact match), post-sleep reaper kill-safety (plus a shell-free/healthprobe withos.devNullso Windows curl can't false-negative a healthy sibling), branch-URL correctness across REST tools, and bridge-firstfigma_take_screenshot.figma_arrange_component_setnow rearranges variants in place so placed instances survive. No new tools; plugin re-import required (code.js+ui.htmlchanged — and the new handshake makes this the last one you have to discover on your own). 1236 tests passing (33 new).v1.32.1 - Documentation-generator fix reported by Robin Di Capua:
figma_generate_component_docdocumented colors as raw hex (with—in the Figma Variable column) even when fills/strokes were bound to variables, while spacing tokens documented correctly. Two root causes — an id→name lookup that read the wrong keys (.id/.nameinstead ofvariableId/variableName), and variable names only ever being sourced from the Enterprise-only REST/variables/localendpoint (403 elsewhere). The generator now resolves names via the Desktop Bridge Plugin API (works on every plan) and threads them through the States, Color Tokens, and Spacing tables, so real token names likecolor/content/defaultandspacing/1appear. No new tools, no arg-shape changes, no plugin re-import required. 1203 tests passing.v1.32.0 - Accessibility-audit correctness fix reported by Isabella (a11y collaborator):
figma_lint_designwas flagging line height below 1.5× as an accessibility failure on hundreds of components. That misreads WCAG 1.4.12 Text Spacing, which requires content to support user spacing overrides without loss — not that designs ship at 1.5× — so a sub-1.5 line height is not a conformance failure. Line/paragraph-spacing checks are now scoped to multi-line text (single-line labels and buttons exempt); readability hints (text-size,line-height,letter-spacing,paragraph-spacing) are decoupled from thewcaggroup into an opt-inbest-practicegroup, so the default audit (['wcag','design-system','layout']) andrules: ['wcag']return genuine conformance only; and a new code-sidetext-spacing-supportadvisory infigma_scan_code_accessibilityflags fixed-px typography — where 1.4.12/1.4.4 are actually verifiable. No new tools, no arg-shape changes; plugin re-import required to pick up the new audit behavior (bridge protocol unchanged, so an un-updated plugin stays compatible). 1196 tests passing.v1.31.0 - Fixes the most-reported reliability bug: the Desktop Bridge connection dropping and staying down until you closed the plugin, restarted your MCP client, or killed ports by hand. Root cause was zombie MCP server processes squatting the WebSocket port range (9223–9232) after a bad shutdown. The reaper now escalates
SIGTERM→SIGKILL(a hung server that ignores graceful shutdown can no longer survive), sweeps the range every 5 minutes via anunref'd periodic reaper, and a shutdown backstop prevents a server from zombifying in the first place. The redesigned Desktop Bridge plugin adds an auto-reconnect watchdog (re-probes every ~12s while disconnected), a context-aware Pause / Resume / Reconnect button, and a live server-count badge. No new tools; plugin re-import required (bridgeui.html+code.jschanged). 1190 tests passing, including an integration test that spawns a realSIGTERM-ignoring process and asserts the reaper kills it.v1.30.0 - Native variable binding + typography in the structured write tools, closing the Plugin API gaps that used to force raw
figma_execute.figma_set_fills/figma_set_strokesaccept avariableIdto bind a fill/stroke to a color variable viasetBoundVariableForPaint(any plan, via the bridge).figma_set_textgainsfontFamily/fontStylewith space-insensitive normalization (SemiBold→Semi Bold) and gracefulRegularfallback.figma_instantiate_componentpre-loads instance text fonts before applying overrides (fixes silently-skipped text overrides on non-Regular weights) and returns awarningsarray for failed overrides. Also fixes a mixed-font crash infigma_set_textand aui.htmlrelay that was dropping new message fields. No new tools; plugin re-import required (bridgeui.html+code.jschanged). Validated live; 1185 tests passing.v1.29.2 - Bug fix:
figma_generate_component_docnow renders Figma component descriptions faithfully and reliably tags atomic-design level. Single-#headings in descriptions render as real sections (Usage Guidelines, Implementation Considerations, Accessibility Requirements, Content Configuration) instead of leaking as- # Headinglist items; frontmatterdescriptiontakes the first sentence instead of truncating on the word "Accessibility"; the generated Figma URL no longer doubles?node-id=; and the component's atomic level (atom/molecule/organism/template) is auto-detected via a singleids=<node>file request + divider walk-back, with no dependency on library publishing. No new tools; plugin re-import not required.v1.29.1 - Bug fix:
figma_get_design_system_kitnow resolves variables bridge-first (Desktop Bridge / cloud relay → REST fallback) instead of calling the Enterprise-only Variables REST API directly. Non-Enterprise users no longer hit a 403 on the kit's token section when a bridge is connected, and a REST 403 now points the caller back to the bridge instead of dead-ending. 7 new tests, 1185 total passing. No new tools; plugin re-import not required.v1.29.0 - Shared library inspection: three new tools close the gap between "I have a component key" and "I can actually use it."
figma_get_library_component_by_keyresolves any 40-char component key to fullcomponentPropertyDefinitions+ variants (with their published keys) + per-variant visual specs — without needing the source library file's URL.figma_get_library_variableslists library tokens via Plugin API (works on every Figma plan; the REST equivalent is Enterprise-only).figma_import_library_variableimports a library token to the current file so it can be bound to nodes. 27 new tests, 1178 total passing. Plugin re-import optional.v1.28.1 - Bug fix patch surfacing from live-fire testing of the v1.28.0 formatters against multi-tier semantic-token design systems. Fixes: Tailwind v3 emitted empty
module.exportsfor alias-only sets (now resolves alias chains to literal values); TypeScript module + JSON flat + JSON nested formatters emitted"{alias.path}"strings as literal values (now resolves); Tailwind v4 namespace-prefix doubling (--color-theme-color-Xis now--color-theme-X). AddsresolveAliasChainpublic helper. 1151 tests still passing.v1.28.0 - Full formatter coverage for
figma_export_tokens. Seven new output formats: Tailwind v4@theme inline, Tailwind v3 config, SCSS variables, TypeScript module, JSON flat/nested, Style Dictionary v3, Tokens Studio multi-file. Combined with DTCG + CSS variables, ships 10 fully-implemented output formats with zero third-party build-tool dependencies. Tool description updated, docs/tools.md table all-green. 22 new Jest tests, 1151 total passing.v1.27.1 - Documentation patch. No code behavior changes. Sweeps stale "Phase 1 ships with DTCG only" claims across tool descriptions, error messages, and internal comments after CSS variables formatter and the apply phase shipped during the v1.27.0 dev cycle. Refreshes README banner + capability bullets + roadmap. Adds
Phase 3.5: Stale-Content Auditto the release runbook so future releases get a strict pre-publish grep sweep across banners, tool descriptions, error messages, source comments, and tool-count consistency.v1.27.0 - Bidirectional token sync:
figma_export_tokens+figma_import_tokensreplace Style Dictionary and Tokens Studio's export pipeline. Canonical DTCG JSON + CSS custom properties. Diff-aware merge with round-trip ID preservation via$extensions["figma-console-mcp"]. Apply phase pushes hex-value edits back to Figma via the plugin bridge. Verified end-to-end against 713-token + 280-token design systems.v1.26.0 - Internal cleanup + cross-MCP identity: Local-mode CDP/Puppeteer transport removed entirely (WebSocket-only).
figma_diagnosetool for designer-readable health checks. Every response tagged_mcp: "figma-console-mcp"; errors prefixed[figma-console-mcp]so attribution is unambiguous when running multiple Figma MCPs. Plugin status pill now readsLocal · ready/Cloud · ready/Local + Cloud · ready. Net diff: −7,299 lines, plugin re-import optional.v1.25.0 - Description + Dev Mode annotation tracking in
figma_diff_versionsvia plugin session buffer. Description and annotation edits made during a session now appear in diff output (REST API doesn't return these — bridged through the plugin'sdocumentchangelistener).v1.24.0 - Honest scope coverage on version diffs.
scope_coverageobject surfaces whatfigma_diff_versionsdoes and doesn't track; always-on coverage warnings prevent silent invisibility on token-value changes and component-instance placements.v1.23.0 - Version History & Time-Series Awareness: 6 new tools (list versions, snapshot any past version, diff two versions for component/binding deltas, generate markdown changelogs, trace property/variant introduction via binary-search blame walker). Author attribution flows from autosaves, not just labeled releases.
v1.17.0 - Figma Slides support: 15 tools for managing presentations.
v1.16.0 - FigJam support: 9 tools for creating and reading FigJam boards.
v1.12.0 - Cloud Write Relay: web AI clients can create and modify Figma designs without Node.js.
v1.11.0 - Complete CDP removal, improved multi-file active tracking with focus detection.
v1.10.0 - Multi-instance support (dynamic port fallback 9223–9232, multi-connection plugin, instance discovery).
v1.9.0 - Figma Comments tools, improved port conflict detection.
v1.8.0 - WebSocket Bridge transport (CDP-free connectivity), real-time selection/document tracking.
v1.7.0 - MCP Apps (Token Browser, Design System Dashboard), batch variable operations, design-code parity tools.
Coming Next:
Token sync — non-DTCG input parsers - Parsers for non-DTCG input (Tokens Studio, CSS vars, Tailwind v4, Tailwind v3 config, SCSS, Style Dictionary v3, JSON flat/nested) so
figma_import_tokenscan ingest the same formats it exports. (The import-side apply expansion — creates, replace-gated deletes, alias-target updates — shipped in v1.34.0.)Cross-library variable resolution - Resolve cross-library aliases via
getVariableByIdAsyncso they render as realvar(--target)references in exports instead of comments.Component template library - Common UI pattern generation
Visual regression testing - Screenshot diff capabilities
💻 Development
git clone https://github.com/southleft/figma-console-mcp.git
cd figma-console-mcp
npm install
# Local mode development
npm run dev:local
# Cloud mode development
npm run dev
# Build
npm run build📄 License
MIT - See LICENSE file for details.
🔗 Links
📚 Documentation Site — Complete guides, tutorials, and API reference
📖 Local Docs — Documentation source files
Available Tools
130 toolsfigjam_auto_arrangeA
Arrange nodes on a FigJam board in a grid, horizontal row, or vertical column layout. Use after batch-creating elements to organize them neatly.
Inputs: nodeIds (required), layout, columns, spacing.
figjam_create_code_blockA
Create a code block on a FigJam board. Use for sharing code snippets, config examples, or technical documentation in collaborative boards.
Inputs: code (required), x, y, language.
figjam_create_connectorA
Connect two nodes with a connector line in FigJam. Use to create flowcharts, diagrams, and relationship maps.
Nodes must exist on the board (stickies, shapes, etc.). Use their node IDs from creation results.
Magnet positions: AUTO (default), TOP, BOTTOM, LEFT, RIGHT — controls where the connector attaches to each node.
Inputs: endNodeId (required), startNodeId (required), label, endMagnet, +1 more.
figjam_create_sectionA
Create a section on a FigJam board. Sections are containers that can hold other elements. Use for grouping related content.
Note: After creating a section, place elements inside it by setting their x/y coordinates within the section's bounds, then use figma_execute to call section.appendChild(node) to parent them.
Inputs: x, y, name, width, +2 more.
figjam_create_shape_with_textA
Create a labeled shape on a FigJam board with optional size, colors, and font control. Use for flowchart nodes, process diagrams, and visual organization.
Shape types: ROUNDED_RECTANGLE (default), DIAMOND, ELLIPSE, TRIANGLE_UP, TRIANGLE_DOWN, PARALLELOGRAM_RIGHT, PARALLELOGRAM_LEFT, ENG_DATABASE, ENG_QUEUE, ENG_FILE, ENG_FOLDER
Inputs: x, y, text, width, +6 more.
figjam_create_stickiesA
Batch create multiple sticky notes on a FigJam board (max 200). Use this to populate boards from structured data (meeting notes, brainstorm ideas, etc.).
Colors: YELLOW, BLUE, GREEN, PINK, ORANGE, PURPLE, RED, LIGHT_GRAY, GRAY
Inputs: stickies (required).
figjam_create_stickyB
Create a sticky note on a FigJam board. Only works in FigJam files.
Colors: YELLOW, BLUE, GREEN, PINK, ORANGE, PURPLE, RED, LIGHT_GRAY, GRAY (default: YELLOW)
Inputs: text (required), x, y, color.
figjam_create_tableB
Create a table on a FigJam board with optional cell data. Use for structured data display, comparison matrices, and organized information.
Data format: 2D array of strings, e.g. [["Header1", "Header2"], ["Row1Col1", "Row1Col2"]]
Inputs: rows (required), columns (required), x, y, +1 more.
figjam_get_board_contentsA
Read all content from a FigJam board. Returns stickies, shapes, connectors, tables, code blocks, and sections with their text content and positions.
Use this to understand what's on a board before modifying it, or to extract structured data from collaborative sessions.
Filters: Pass nodeTypes to limit results (e.g., ["STICKY"] for only stickies). Omit for everything.
Inputs: maxNodes, nodeTypes.
figjam_get_connectionsA
Read the connection graph from a FigJam board. Returns all connectors with their start/end node references and labels.
Use this to understand relationships, flowcharts, and diagrams. Returns edges as {startNodeId, endNodeId, label} plus a summary of connected nodes.
Inputs: no named parameters.
figma_add_component_propertyA
Add a new component property to a component or component set. Properties enable dynamic content and behavior in component instances. Supported types: BOOLEAN (toggle), TEXT (string), INSTANCE_SWAP (component swap), VARIANT (variant selection), SLOT (freeform slot — prefer figma_create_slot for new slots).
Inputs: type (required), nodeId (required), propertyName (required), description, +2 more.
figma_add_modeA
Add a new mode to an existing Figma variable collection. Modes allow variables to have different values for different contexts (e.g., Light/Dark themes, device sizes). Requires the Desktop Bridge plugin to be running.
Inputs: modeName (required), collectionId (required).
figma_add_shape_to_slideC
Add a rectangle or ellipse shape to a specific slide with optional fill color.
Inputs: x (required), y (required), width (required), height (required), +3 more.
figma_add_slot_propertyA
Manually add a SLOT component property and bind it to an existing frame (alternative to figma_create_slot). The frame must be a direct child of the component, must not use GRID layout, and must not be nested inside another slot. Supports description and preferredValues.
MULTI-FILE (Local Mode only): Pass fileKey to run this against a specific connected file without switching the active file/target lock (see figma_list_open_files). Does not change the active file or target lock. Cloud Mode pairs with a single plugin instance and rejects fileKey.
Inputs: nodeId (required), frameNodeId (required), propertyName (required), fileKey, +2 more.
figma_add_text_to_slideC
Add a new text element to a specific slide. Supports custom fonts, colors, alignment, and text formatting.
Inputs: text (required), slideId (required), x, y, +9 more.
figma_analyze_component_setA
Analyze a Figma COMPONENT_SET to extract variant state machine and cross-variant diffs for code generation. Returns: (1) variant axes (size, state) with all values, (2) CSS pseudo-class mappings for interaction states (hover→:hover, focus→:focus-visible, disabled→:disabled, error→[aria-invalid]), (3) visual diff from default state per variant (only changed properties — fill/stroke as token or hex, gradient, image and paint opacity, stroke weight, text color, opacity, effects, corner radius, size, child layers, visibility, the variant's own fill/stroke/opacity/radius (variantFill, variantStroke, variantOpacity, variantRadius), auto-layout (layout) and swapped spacing/size tokens (tokens), plus layers: changes to nested layers keyed by layer path such as 'Icons/Radio › Icon' — instance swaps, size, free position, rotation, vector shape, label text and typography), (4) component property definitions mapped to code props (BOOLEAN→boolean, TEXT→string, INSTANCE_SWAP→slot/ReactNode), and (5) slots — Figma SLOT properties (name, preferredValues = the components a slot accepts, and limitViolations) to implement as named slots / children props (React {children} or named ReactNode; Web Components ). Use this on the parent COMPONENT_SET node, not individual variants. Requires Desktop Bridge plugin.
Inputs: nodeId (required).
figma_append_to_slotA
Add content to a slot on a component instance. Clones sourceNodeId into the slot, or creates a new node (nodeType). SLOT content cannot be set via figma_set_instance_properties — use this tool instead. Widgets, stickies, and raw ComponentNodes cannot be appended to slots.
MULTI-FILE (Local Mode only): Pass fileKey to run this against a specific connected file without switching the active file/target lock (see figma_list_open_files). Does not change the active file or target lock. Cloud Mode pairs with a single plugin instance and rejects fileKey.
Inputs: clone, slotId, fileKey, nodeType, +5 more.
figma_apply_animationA
Animate a node with Figma Motion. Pass exactly one of:
preset: a Figma animation style (Position, Scale, Rotation, Size, Opacity, Path, TextStagger), with optional duration, timelineOffset, easing and preset props. List presets and their props with figma_manage_animation_styles action 'list_presets'.
customStyleId: a local custom animation style (see figma_manage_animation_styles).
keyframeTracks: manual keyframes per property, paint color or effect field. Each track replaces any existing track for that target. Easing can be a literal curve or an EASING variable (easing.variableId); a preset's duration can be bound to a TIMING variable (durationVariableId). Main components can't be animated through the Plugin API: use an instance or frame. Motion plays in Figma's preview and video export, not in static screenshots.
Inputs: nodeId (required), props, easing, preset, +6 more.
figma_apply_shaderA
Apply a shader to a node's fills, strokes or effects, or change the properties of one already applied. Set properties by name (e.g. {turbulence: 40, cloudColor: '#E8F4FF'}); names, types and defaults come from figma_list_shaders. Colors take hex strings or {r,g,b,a}, and any property can bind a variable with {variableId}. Pass index to change a shader already in that list; without index the shader is added on top (or replaces the list with replace: true). Fill shaders go on fills or strokes; effect shaders go on effects. Unknown property names change nothing and list the valid ones. Requires Desktop Bridge.
Inputs: nodeId (required), index, target, fileKey, +6 more.
figma_arrange_component_setA
Organize a component set with Figma's native purple dashed visualization. Use after creating variants, adding states (hover/disabled/pressed), or when component sets need cleanup.
Non-destructive: rearranges the existing variants in place (grid positions on the existing set's children), so the component set keeps its node ID and all placed instances remain intact. Arranges variants in a labeled grid (columns = last property like State, rows = other properties like Type+Size) and wraps the set in a white container with title, row/column labels. Safe to run on component sets with placed instances, and safe to re-run.
Inputs: options, componentSetId, componentSetName.
figma_audit_component_accessibilityA
Deep accessibility audit for a specific component or component set. Produces a scorecard covering: state coverage (default/hover/focus/disabled/error/active/loading), focus indicator quality and contrast, non-color differentiation (WCAG 1.4.1), target size consistency (WCAG 2.5.8), annotation completeness, and color-blind simulation (protanopia/deuteranopia/tritanopia). Returns per-category scores (0-100) and prioritized recommendations. Use after designing a component to validate accessibility before handoff. Requires Desktop Bridge plugin.
Inputs: nodeId, targetSize.
figma_audit_design_system_reportA
Run the design-system health audit and return the scored report as data (no UI required). Same deterministic engine as the Design System Dashboard app: naming & semantics, token architecture, component metadata, accessibility, consistency, coverage — each 0-100 plus a weighted overall. Start with the default summary, then drill into one category at a time via category (chunked; avoids one giant payload). Results are cached ~5 minutes; pass forceRefresh after editing the file. Every finding includes whether this MCP can fix it (design-side write tools vs. design decision vs. manual).
Inputs: format, fileUrl, category, forceRefresh.
figma_batch_create_variablesA
Create multiple variables in one operation. Use instead of calling figma_create_variable repeatedly — up to 50x faster for bulk operations. Get collection IDs from figma_get_variables first. Requires Desktop Bridge plugin.
Inputs: variables (required), collectionId (required).
figma_batch_update_variablesA
Update multiple variable values in one operation. Use instead of calling figma_update_variable repeatedly — up to 50x faster for bulk updates. Get variable/mode IDs from figma_get_variables first. Requires Desktop Bridge plugin.
Inputs: updates (required).
figma_blame_nodeA
Find the version that introduced a specific change to a node — answers 'who/when added this'. Walks version history backward via binary search (~log2(N) API calls instead of N) to localize the introduction point. Returns the version's metadata (label/author/timestamp). Default includes autosaves for finer attribution; system 'Figma' user appears occasionally for scheduled snapshots and is flagged via attribution_certainty='system_attributed'. Specify EXACTLY ONE of target_component_property or target_child_node_id. node_id is optional — if omitted, falls back to the first node in the current Figma selection.
Inputs: fileUrl, node_id, start_version, include_autosaves, +3 more.
figma_capture_screenshotA
Capture a screenshot of a node using the plugin's exportAsync API. IMPORTANT: This tool captures the CURRENT state from the plugin runtime (not cloud state like REST API), making it reliable for validating changes immediately after making them. Use this instead of figma_get_component_image when you need to verify that changes were applied correctly. Defaults are AI-optimized: PNG at 1x with automatic downscaling so the longest side stays within the 1568px AI vision processing ceiling. PNG is the default because design tool content (flat colors, text, UI components) compresses significantly better as PNG. Use JPG for photographic or gradient-heavy content. Requires Desktop Bridge connection (Figma Desktop with plugin running).
Inputs: scale, format, nodeId.
figma_check_design_parityB
Compare a Figma component's design specs against code-side data to find discrepancies. Returns a parity score, categorized discrepancies, and actionable fix items for both design-side (Figma tool calls) and code-side (file edits). Read the component source code first, then pass the data in codeSpec.
Inputs: nodeId (required), codeSpec (required), enrich, fileUrl, +1 more.
figma_clear_consoleA
Clear the console log buffer. Safely clears the buffer without disrupting the connection. Returns number of logs cleared.
Inputs: no named parameters.
figma_clone_nodeB
Duplicate a node. The clone is placed at a slight offset from the original.
Inputs: nodeId (required).
figma_create_childA
Create a new child node inside a parent container. Always place inside an existing Section or Frame — never on a bare page. If no suitable parent exists, create a Section first. Clean up any empty or orphaned nodes if the operation fails.
Inputs: nodeType (required), parentId (required), properties.
figma_create_component_setA
Create a component set with variants in one call — replaces hand-written figma.combineAsVariants scripts.
Two modes:
Generate from a base component: pass baseComponentId + properties (variant axes). The base is cloned for every combination of the axes ({ State: ['default','hover','disabled'], Size: ['sm','lg'] } → 6 variants), each named 'Prop=Value' comma-joined (e.g. 'State=hover, Size=sm'), then combined into a set. The base component itself becomes the FIRST variant (same node ID), so existing instances of the base survive as instances of that variant.
Combine existing components: pass componentIds, optionally with variantProperties (aligned 1:1) to rename each component to Prop=Value form before combining.
Figma derives the variant property definitions from the names; they live on the SET (componentPropertyDefinitions), not on individual variants. The result includes each variant's key — instantiate with a VARIANT's key/nodeId via figma_instantiate_component, not the set's key.
Set autoArrange:true to lay the new set out as a labeled grid inside a white container (same layout as figma_arrange_component_set). Requires Desktop Bridge plugin.
SIZE GUIDANCE: hard cap 100 variants. The timeout auto-scales with variant count (~1.2s/variant, 30s floor / 2min cap), but above ~40 variants the single-pass clone+combine gets slow and heavy base components may still push the limit — prefer splitting large matrices into multiple sets (e.g. one set per Size).
Inputs: name, parentId, position, properties, +5 more.
figma_create_slideB
Create a new blank slide in the Figma Slides presentation. Optionally specify grid position.
Inputs: col, row.
figma_create_slotA
Create a SlotNode inside a component using createSlot(). Automatically creates a linked SLOT component property named after the slot (renaming the slot renames the property). Slots are freeform drop zones for instance content — more flexible than INSTANCE_SWAP. Works on standalone COMPONENTs and variant COMPONENTs inside a COMPONENT_SET (call once per variant). GRID layout is not allowed on slots. Requires Desktop Bridge.
MULTI-FILE (Local Mode only): Pass fileKey to run this against a specific connected file without switching the active file/target lock (see figma_list_open_files). Does not change the active file or target lock. Cloud Mode pairs with a single plugin instance and rejects fileKey.
Inputs: nodeId (required), name, width, height, +2 more.
figma_create_variableA
Create a single Figma variable. For multiple variables, use figma_batch_create_variables instead (10-50x faster). Use figma_get_variables first to get collection IDs. Supports COLOR, FLOAT, STRING, BOOLEAN, and motion TIMING/EASING. Requires Desktop Bridge plugin.
Inputs: name (required), collectionId (required), resolvedType (required), description, +1 more.
figma_create_variable_collectionA
Create an empty variable collection. To create a collection WITH variables and modes in one step, use figma_setup_design_tokens instead. Requires Desktop Bridge plugin.
Inputs: name (required), additionalModes, initialModeName.
figma_delete_commentA
Delete a comment from a Figma file by its comment ID. Use figma_get_comments to find comment IDs first.
Inputs: comment_id (required), fileUrl.
figma_delete_component_propertyA
Delete a component property. Works with BOOLEAN, TEXT, INSTANCE_SWAP, and SLOT properties (not VARIANT). This is a destructive operation.
Inputs: nodeId (required), propertyName (required).
figma_delete_nodeA
Delete a node from the canvas. WARNING: This is a destructive operation (can be undone with Figma's undo).
Inputs: nodeId (required).
figma_delete_slideB
Delete a slide from the presentation. WARNING: This is a destructive operation (can be undone with Figma's undo).
Inputs: slideId (required).
figma_delete_variableA
Delete a Figma variable. WARNING: This is a destructive operation that cannot be undone (except with Figma's undo). Use figma_get_variables first to get variable IDs. Requires the Desktop Bridge plugin to be running.
Inputs: variableId (required).
figma_delete_variable_collectionA
Delete a Figma variable collection and ALL its variables. WARNING: This is a destructive operation that deletes all variables in the collection and cannot be undone (except with Figma's undo). Requires the Desktop Bridge plugin to be running.
Inputs: collectionId (required).
figma_diagnoseA
Designer-readable health check for figma-console-mcp. Use this when something seems wrong — it self-identifies the server, reports plugin connection / file / token status in plain language, and disambiguates errors that may be coming from a different Figma-related MCP server. Recommended as the first step when a user reports a "token expired" or "plugin disconnected" issue.
Inputs: verbose.
figma_diff_versionsA
Diff two versions of a Figma file. Always returns a cheap page-structure diff (added/removed/renamed pages, 2 API calls). Pass component_ids to additionally get per-node deep diffs at depth=2 (added/removed children, name/description changes, componentPropertyDefinitions changes for COMPONENT_SETs, boundVariables deltas) — costs 2 API calls per scoped node. Use 'current' for to_version to diff against HEAD. v1.25.0: when the Desktop Bridge plugin is connected, description and Dev Mode annotation changes are ALSO tracked via a session buffer and surfaced under scoped_nodes[].metadata_changes[] and unscoped_metadata_changes[] — Figma REST omits these from version snapshots so they're otherwise invisible. STILL NOT tracked: instances of components on the canvas, raw layout properties (layoutSizingHorizontal/Vertical, unbound paddings/widths), raw visual properties (cornerRadius, unbound fills), variable VALUE changes, style content, and metadata edits made while the plugin was disconnected. See scope_coverage and notes[] for the full coverage map and complementary tools.
Inputs: to_version (required), from_version (required), mode, fileUrl, +1 more.
figma_ds_analyzeA
Analyze one or more production app codebases as the first step of design system extraction. Detects framework (React/Next/Angular/Web Components), styling methods (Tailwind v3/v4, CSS Modules, SCSS, Emotion, styled-components), and vendor component layers (shadcn/ui, Radix, MUI, Chakra, etc.); builds a component inventory with per-component classification (vendored / wrapped / pure-vendor / bespoke), prop contracts, real usage counts (porting rank), observed prop values (variant inference), and duplicate detection. Pass multiple targets to find the shared design language across several apps. Writes the full manifest to /.extraction/analysis.json and returns a compressed summary — read slices of the manifest for detail. Run this before figma_ds_extract_tokens and figma_ds_scaffold. Local Mode only.
Inputs: targets (required), outDir, exclude, include, +1 more.
figma_ds_extract_componentA
Deep-extract ONE component from the inventory for porting into the design system: returns its source (capped), local import closure (relative imports to follow), prop contract, observed call-site variants, vendor classification, style touchpoints (classNames, CSS-module imports, custom properties referenced), and a ready-to-adapt CSF3 story scaffold with variant stories inferred from real usage. The agent then ports the component into /src/components// and records progress with figma_ds_status. Local Mode only.
Inputs: outDir (required), component (required).
figma_ds_extract_tokensA
Extract design tokens from analyzed codebases into canonical DTCG JSON (plus optional CSS variables / Tailwind / SCSS / TypeScript projections). Mines declared styling intent first — :root and @theme custom properties (light+dark → multi-mode tokens), SCSS variables, tailwind.config theme values, shadcn HSL triples — then promotes recurring raw values (hex colors, spacing/radius/font sizes) above a frequency threshold. Every token carries provenance (source file:line, confidence, frequency) in $extensions. Names are structural as-mined; do a semantic-naming review pass with the user afterwards. The DTCG output is directly importable into Figma variables with figma_import_tokens (top-level groups become collections). Requires figma_ds_analyze to have run for the same outDir. Local Mode only.
Inputs: write, outDir, formats, targets, +2 more.
figma_ds_scaffoldA
Generate the design-system package skeleton at outDir from a completed analysis + token extraction: package.json (app framework as peer deps), src/components layout, token files via the shared formatter engine, a framework-neutral token-showcase MDX docs page (the bird's-eye view), and a README with the workflow. Storybook itself is NOT installed by this tool — after scaffolding, run npm create storybook@latest inside outDir (the CLI auto-detects the framework and installs the current Storybook version). Additive by default: existing files are skipped unless force. Local Mode only.
Inputs: outDir (required), force, formats, framework, +2 more.
figma_ds_setup_storybookA
Wire a freshly-initialized Storybook workshop to the extracted design system — run AFTER npm create storybook@latest inside outDir. Generates .storybook/preview.css (Tailwind entry importing the extracted tokens plus the SOURCE app's @theme utility mapping, custom @utility definitions, @layer base, and @font-face rules mined from its stylesheets, with a dark variant covering both .dark and [data-theme] conventions), copies self-hosted font files into staticDirs, and patches main.js (tailwind vite plugin + automatic JSX runtime — without it stories throw 'React is not defined') and preview.jsx (preview.css import + a theme toolbar/decorator using the extracted mode names). Idempotent; anything it can't patch safely is returned as a manual step. Local Mode only.
Inputs: outDir (required).
figma_ds_statusA
Read or update design-system extraction porting progress (persisted in /.extraction/status.json so long engagements survive session boundaries). Call with only outDir to get a progress summary; pass update to record a component's porting status. Local Mode only.
Inputs: outDir (required), update.
figma_ds_verifyA
Run the deterministic fidelity evals on an extracted design system package — the governance gate before handing off or pushing to Figma. Checks: tokens.json parses as DTCG and every alias resolves (import-ready); no quoted CSS functional expressions in generated token files (kills transitions); every var() consumed in component/preview CSS resolves in the workshop; every component directory has a stories file and index barrel; every portable inventory component has a porting status. Each check encodes a failure class found in real extraction runs. Also reports Figma round-trip readiness with the exact figma_import_tokens call for design-led orgs (ask the user code-led vs design-led). Local Mode only.
Inputs: outDir (required).
figma_duplicate_slideB
Duplicate an existing slide. The clone is placed adjacent to the original.
Inputs: slideId (required).
figma_edit_component_propertyB
Edit an existing component property. Can change the name, default value, or preferred values (for INSTANCE_SWAP). Use the full property name including the unique suffix.
Inputs: nodeId (required), newValue (required), propertyName (required).
figma_executeA
Execute arbitrary JavaScript in Figma's plugin context with full access to the figma API. Use for complex operations not covered by other tools. Requires Desktop Bridge plugin. CAUTION: Can modify your document.
COMPONENT INSTANCES: For instances (node.type === 'INSTANCE'), use figma_set_instance_properties — direct text editing FAILS SILENTLY. Check instance.componentProperties for available props (may have #nodeId suffixes).
RESULT ANALYSIS: Check resultAnalysis.warning for silent failures (empty arrays, null returns).
VALIDATION: After creating/modifying visuals: screenshot with figma_capture_screenshot, check alignment/spacing/proportions, iterate up to 3x.
PLACEMENT: Always create components inside a Section or Frame, never on blank canvas. Use parent.insertChild(0, bg) for z-ordering backgrounds behind content.
HOUSEKEEPING (MANDATORY): Before creating: screenshot the target page to see existing content and find clear space. When creating: place inside a named Section, positioned BELOW or AWAY from existing content. Never overlap. After creating: screenshot to verify clean placement and no overlaps. On failure/retry: DELETE any partial artifacts (empty frames, orphaned layers, blank pages) before retrying. Use node.remove() to clean up. Pages: NEVER create a new page if one with that name already exists — use the existing one. If you created a blank page during a failed attempt, delete it. Layers: If your code creates helper frames, placeholder nodes, or intermediate layers that aren't part of the final result, remove them.
MULTI-FILE (Local Mode only): Pass fileKey to run this in a specific connected file without switching the active file/target lock (see figma_list_open_files). To run the same code across several connected files at once, use figma_execute_across_files instead. Cloud Mode pairs with a single plugin instance and rejects fileKey.
Inputs: code (required), fileKey, timeout.
figma_execute_across_filesA
Run the same JavaScript against multiple Figma files connected via the Desktop Bridge plugin, IN PARALLEL, without touching the active file or target lock. Built for cross-file consistency work — e.g. running the same structural check or fix against every file in a multi-file design system and diffing the results — instead of switching the active file and running figma_execute once per file in sequence. Each file's code runs in that file's own plugin context (same 'figma' global as figma_execute). You must say which files to target: pass fileKeys (read them from figma_list_open_files first — strongly preferred for anything that writes), or pass allFiles: true to hit every connected file. Requires Desktop Bridge plugin open in each target file. Local Mode only.
Inputs: code (required), timeout, allFiles, fileKeys.
figma_export_animationA
Export an animated frame as MP4, GIF or WebM. The node should be the frame that holds the Motion timeline (its top-level frame). The file is written to outputPath (default: the OS temp folder) and the path is returned. An existing file is never replaced unless overwrite is true.
Inputs: format (required), fps, scale, width, +7 more.
figma_export_tokensA
Export Figma variables to design token files in your codebase. Bidirectional with figma_import_tokens — together they replace Style Dictionary and Tokens Studio's export pipeline for the popular styling methods.
FULLY-IMPLEMENTED OUTPUT FORMATS:
• dtcg — W3C DTCG JSON. Canonical pivot format. Round-trip safe via $extensions["figma-console-mcp"].
• css-vars — CSS custom properties with mode-aware selectors (:root, .dark, [data-theme=...]).
• tailwind-v4 — Tailwind v4 @theme inline block. Token-to-namespace mapping (color/, spacing/, radius/*, etc.) generates Tailwind utility classes.
• tailwind-v3 — tailwind.config.js theme.extend object grouped under Tailwind's theme keys (colors, spacing, fontFamily, etc.).
• scss — $var: value; declarations. Multi-mode emits a primary variable + a mode-keyed SCSS map for runtime access.
• ts-module — export const tokens = { ... } as const with derived Tokens type. Multi-mode tokens emit as { Light: ..., Dark: ... } objects.
• json-flat — flat key-value JSON ({"ds-color-primary": "#4085F2"}) for custom build scripts.
• json-nested — nested object JSON mirroring the token path tree.
• style-dictionary-v3 — SD v3 source format with bare value/type keys (back-compat for existing SD users).
• tokens-studio — Tokens Studio multi-file layout ($themes.json + $metadata.json + per-set files). Preserves Figma collection/mode bindings for round-trip with the TS plugin.
ZERO-ARG USAGE: With a tokens.config.json at your project root, just call the tool with no args — it picks up source dir, output formats, modes, prefix, etc. from config. See the response's suggestedScaffold payload when no config is detected — present it to the user, write the scaffold via your file tools, then call again.
WRITE SAFETY: Export REPLACES the contents of each target file with the current Figma state — it does not merge into it. Under the default strategy: "merge" the tool refuses to write (and changes nothing) when overwriting an existing DTCG file would delete tokens it does not manage: tokens added by hand, or tokens from collections outside this export. It also refuses when a requested collectionId is not in the file it read, or when the export is empty — both usually mean a different file is active in Figma than you intended. Variables deleted in Figma are removed from the file as normal. Use dry-run to preview, replace to overwrite unconditionally. Generated files record the Figma file they came from (a Source: Figma file <key> header line; figmaFileKey in DTCG), and the default strategy also refuses to overwrite a file that was generated from a DIFFERENT Figma file. Plain-JSON formats (json-flat, json-nested, style-dictionary-v3, tokens-studio) cannot carry that record — pin figmaFile in tokens.config.json for a hard guarantee. Every response includes source (the Figma file name/key the data was read from) — check it.
DTCG DIALECT (dtcgDialect, applies to dtcg/json-flat/json-nested outputs): legacy (default): hex-string colors, maximum compatibility (Style Dictionary v4, Tokens Studio). 2025: DTCG 2025.10 object colors/dimensions (Style Dictionary v5+). figma_import_tokens accepts BOTH dialects regardless of this setting.
ROUND-TRIP SAFETY: Figma variable IDs are preserved in DTCG $extensions["figma-console-mcp"] so renames on either side don't create duplicates. The same metadata enables non-destructive incremental sync via figma_import_tokens. Variable scopes (when non-default) and per-platform codeSyntax (when set) are stashed there too and round-trip through import.
Inputs: modes, scope, format, prefix, +11 more.
figma_focus_slideB
Navigate to and focus a specific slide in single-slide view.
Inputs: slideId (required).
figma_generate_changelogA
Generate a human-readable markdown changelog between two versions. Wraps figma_diff_versions and enriches the output with author labels and timestamps via figma_get_file_versions lookback (one extra cheap API call). Returns BOTH a markdown string (paste into release notes / PRs / Storybook MDX) and the structured diff data. Same component_ids and mode semantics as figma_diff_versions. Use 'current' for to_version to changelog against HEAD.
Inputs: to_version (required), from_version (required), mode, fileUrl, +1 more.
figma_generate_component_docA
Generate AI-complete component documentation from a Figma component. Produces structured markdown with anatomy, per-variant color tokens, typography, content guidelines (parsed from Figma description), design annotations (animation timings, interaction specs, accessibility notes from Dev Mode), icon mapping, spacing tokens, and design-code parity analysis. Merges Figma design data with optional code-side info (CVA definitions, sub-component APIs, source files). Output works with any docs platform. For richest output, read the component source code first and pass codeInfo. Pass history: { figma: true, git: true } to add an ongoing '## History' section: per-version design changes pulled from Figma version history and scoped to this component, plus recent git commits touching its source files.
Inputs: nodeId (required), enrich, fileUrl, history, +5 more.
figma_get_animationsA
Read a node's Motion animations: applied animation styles (Figma presets and custom styles, with their entries), manual keyframe tracks, timelines and the playhead. Easing comes back with a CSS equivalent (cubic-bezier) where one exists, and token bindings come back as EASING/TIMING variable references. Set includeDescendants to also list animated layers inside it. Requires Desktop Bridge and Figma Desktop with the Motion API (beta).
Inputs: limit, nodeId, fileKey, includeDescendants.
figma_get_annotation_categoriesA
List available annotation categories in the current Figma file. Categories group annotations by purpose (e.g., interactions, accessibility, development notes). Use the returned category IDs when creating annotations with figma_set_annotations. Requires Desktop Bridge plugin.
Inputs: no named parameters.
figma_get_annotationsA
Read annotations from a Figma node. Annotations are designer-authored specs attached to nodes — they can include notes (plain text or markdown), pinned design properties (fills, width, fontSize, etc.), and category labels. Use this to discover animation timings, interaction specs, accessibility requirements, and other implementation details that designers annotate directly on the design. Set include_children=true to get annotations from child nodes too (useful for full component documentation). Requires Desktop Bridge plugin.
Inputs: nodeId (required), depth, include_children.
figma_get_changes_since_versionA
Convenience wrapper for figma_diff_versions: compares a given version against the current HEAD. Same output shape as figma_diff_versions, with to_version implicitly 'current'. Useful for 'what's changed since the last code-sync' workflows.
Inputs: since_version (required), mode, fileUrl, component_ids.
figma_get_code_layersA
Find code layers (Figma's React code layers, node type CODE_INSTANCE) on the current page or across the file, with position, size, page, and any dev resources or related links (e.g. the GitHub source). The Plugin API and REST API expose code layers as rendered layers only: their source and props can't be read or edited, and new code layers can't be created through them. Create or edit code layers in Figma, through a GitHub import, or with Figma's own MCP server (send_code_to_figma). Use figma_capture_screenshot with a code layer's id to see it. Figma only returns links while the file's window is focused; otherwise the result has linksUnavailable: true and omits them. Requires Desktop Bridge.
Inputs: limit, scope, fileKey.
figma_get_commentsA
Get comment threads on a Figma file. Returns threads (root comment + replies) sorted by latest activity, in a compact format by default (author handle, message, timestamps, pinned node, reaction counts). Narrow the result with an explicit node_id (includes comments pinned to nested nodes), thread_id or since, and page with limit/offset — files often have hundreds of comments. Use include_resolved to also see resolved threads and format='full' for raw Figma API objects.
Inputs: as_md, limit, since, format, +6 more.
figma_get_componentA
Get a SINGLE component's metadata or reconstruction specification. Two export formats: (1) 'metadata' (default) - comprehensive documentation with properties, variants, and design tokens for style guides and references, (2) 'reconstruction' - node tree specification compatible with Figma Component Reconstructor plugin for programmatic component creation. IMPORTANT: For local/unpublished components with metadata format, ensure the Figma Desktop Bridge plugin is running (Right-click in Figma → Plugins → Development → Figma Desktop Bridge) to get complete description data. TIP: To get ALL components with visual specs in one call, prefer figma_get_design_system_kit instead.
Inputs: nodeId (required), enrich, format, fileUrl.
figma_get_component_detailsA
Get full details for a specific component including all variants, properties, and keys needed for instantiation. Use the component key or name from figma_search_components.
Inputs: componentKey, componentName.
figma_get_component_for_developmentA
Get component data optimized for high-fidelity UI implementation. Returns a deep component tree (depth 4) with design tokens (boundVariables), interaction states (reactions), sizing constraints (min/max/layoutSizing), text behavior (autoResize, truncation), Figma slots (named freeform-content regions on a component, with the components each accepts and any min/max limit violations), and design annotations. Automatically includes 2x rendered image. Use when user asks to: 'build this component', 'implement this in React/Vue', 'generate code for', or needs both visual reference and technical specs for production-quality, accessible, token-aware code. For just metadata/descriptions, use figma_get_component. For just image, use figma_get_component_image. For full annotation details, use figma_get_annotations. To resolve variable IDs to names/values, use figma_get_variables.
Inputs: nodeId (required), fileUrl, codebasePath, includeImage.
figma_get_component_for_development_deepA
Get a deeply nested component tree with full visual properties, resolved design token names, instance references, prototype interactions, and annotations at every level. Uses the Desktop Bridge Plugin API for unlimited depth traversal — essential for complex components like data tables, nested menus, date pickers, and compound form fields where the standard depth-4 REST API tool misses deeper structure. Returns boundVariables resolved to actual token names (not just IDs), mainComponent references for INSTANCE nodes, and reactions for interaction states. Requires Desktop Bridge plugin. For simpler components (depth ≤ 4), use figma_get_component_for_development instead.
Inputs: nodeId (required), depth.
figma_get_component_imageA
Render a specific component or node as an image (PNG, JPG, SVG, PDF). Returns image URL valid for 30 days. Use when user asks for: component screenshot, visual preview, rendered output, or 'show me'. NOT for component metadata/properties (use figma_get_component). NOT for getting code/layout data (use figma_get_component_for_development). Best for: visual references, design review, documentation.
Inputs: nodeId (required), scale, format, fileUrl.
figma_get_console_logsA
Retrieve console logs captured by the Desktop Bridge plugin: console output from code run through it (figma_execute and the other write tools) and from the bridge itself. It does NOT capture another plugin's console — Figma runs one plugin at a time in a file, each in its own sandbox, so the bridge cannot see a plugin you are developing. To debug your own plugin's logic, run that code through figma_execute and read the logs here, or use Figma's own developer console for the plugin.
Inputs: count, level, since.
figma_get_design_changesA
Get recent document changes detected in Figma. Returns buffered change events including which nodes changed, whether styles were modified, and change counts. WebSocket-only — events are captured via Desktop Bridge plugin. Use this to understand what changed since you last checked.
Inputs: clear, count, since.
figma_get_design_system_kitA
PREFERRED TOOL for design system extraction — replaces separate figma_get_styles, figma_get_variables, and figma_get_component calls. Returns tokens, components, and styles in a single optimized response with adaptive compression for large systems. Includes component visual specs (exact colors, padding, typography, layout), rendered screenshots, token values per mode (light/dark), and resolved style values. Use this instead of calling individual tools to avoid context window overflow. Ideal for AI code generation — use visualSpec for pixel-accurate reproduction. Variant specs are delta-encoded: the base variant carries the full visualSpec, siblings carry visualSpecDelta with only the properties that differ. Tokens/variables are read through the connected Desktop Bridge or cloud relay and work on ANY Figma plan — no Enterprise required. If a tokens fetch ever reports the Variables REST API is plan-limited (403), the bridge/relay is the plan-independent path: ensure it's connected and retry rather than abandoning variables.
Inputs: format, fileKey, include, componentIds, +1 more.
figma_get_design_system_summaryA
Get a compact overview of the design system. Returns categories, component counts, and token collection names WITHOUT full details. Use this first to understand what's available, then use figma_search_components to find specific components. This tool is optimized for minimal token usage.
Inputs: forceRefresh.
figma_get_file_at_versionA
Fetch a Figma file (or specific nodes) as it existed at a past version_id. Thin snapshot tool — same shape as figma_get_file_data but bound to a historical version. Use figma_get_file_versions to discover version IDs. Combine with depth and node_ids to keep payloads small. Required scope: file_content:read (already standard).
Inputs: version_id (required), depth, fileUrl, node_ids.
figma_get_file_dataA
Get full file structure and document tree. WARNING: Can consume large amounts of tokens. NOT recommended for component descriptions (use figma_get_component instead). Best for understanding file structure or finding component nodeIds. Start with verbosity='summary' and depth=1 for initial exploration.
Inputs: depth, enrich, fileUrl, nodeIds, +1 more.
figma_get_file_for_pluginA
Get file data optimized for plugin development with filtered properties (IDs, structure, plugin data, component relationships). Excludes visual properties (fills, strokes, effects) to reduce payload. Use when user asks for: plugin development, file structure for manipulation, node IDs for plugin API. NOT for component descriptions (use figma_get_component). NOT for visual/styling data (use figma_get_component_for_development). Supports deeper tree traversal (max depth=5) than figma_get_file_data.
Inputs: depth, fileUrl, nodeIds.
figma_get_file_versionsA
List a Figma file's version history with metadata (label, description, author, timestamp). Auto-paginates up to max_versions. By default returns only labeled versions (skips auto-saves). Pass include_autosaves=true to see every saved state. Use the returned pagination.next_cursor to continue paging. Required scope: file_versions:read (OAuth) or 'Versions' Read (PAT).
Inputs: cursor, fileUrl, max_versions, include_autosaves.
figma_get_focused_slideB
Get the slide currently focused in single-slide view.
Inputs: no named parameters.
figma_get_library_component_by_keyA
Get full property definitions, variants, and visual specs for a SINGLE published library component using only its component key.
USE THIS when you have a component key (the 40-char hex returned by figma_search_components, figma_get_library_components, or search_design_system) and want to inspect what properties/variants it exposes before instantiating it — without first needing the source library file's URL.
RESOLVES: componentKey → file_key + node_id → componentPropertyDefinitions + variants + visualSpec.
WORKFLOW:
Pass the componentKey from search results
Tool tries /v1/component_sets/{key} first (most common case — buttons, inputs with variants)
On 404 falls back to /v1/components/{key} (standalone components)
Fetches the parent COMPONENT_SET at depth=2 to read componentPropertyDefinitions and per-variant visual data
For COMPONENT_SET keys, also fetches the source file's /components list to map each variant's node to its published variant key (needed for figma_instantiate_component)
REQUIRES FIGMA_ACCESS_TOKEN with library_assets:read and files:read scopes.
Inputs: componentKey (required), format, includeVisualSpecs.
figma_get_library_componentsA
Discover published components from a shared/team library file.
USE THIS when you need to use components from a published design system library (a different file than the one currently open). This bridges the gap between library discovery and instantiation.
WORKFLOW:
Call this tool with the library file's URL or file key
Browse the returned components — results include COMPONENT_SET (with variants array) and standalone COMPONENT types
Use figma_instantiate_component with a VARIANT key (from the variants array inside a COMPONENT_SET result, NOT the component set key itself)
SEARCH NOTE: The query filter matches both component names AND descriptions. If you get unexpected results (e.g., "Accordion" when searching "Button"), verify the result name matches what you need — it may have matched on a description mention.
MULTI-FILE TIP: If you need to find a specific component and REST API search returns too many results, you can switch to the library file via figma_navigate, use figma_execute to find the exact component and its variant key, then switch back.
NOTE: Requires FIGMA_ACCESS_TOKEN to be set (uses the Figma REST API to read the library file).
Inputs: limit, query, offset, libraryFileKey, +2 more.
figma_get_library_variablesA
List all variables from team libraries the current file has subscribed.
USE THIS when you want to see what design tokens (colors, spacing, typography sizes, booleans, strings) are available from shared libraries — without needing the library file's URL or REST API Enterprise plan.
HOW IT WORKS: Calls figma.teamLibrary.getAvailableLibraryVariableCollectionsAsync() + getVariablesInLibraryCollectionAsync() via the Desktop Bridge. Only libraries the user has explicitly enabled in the current file appear (Figma security model).
WORKFLOW:
Call this tool to inventory available library variables
Find the variable you want (use libraryName + collectionName + variable name to identify)
Pass its key to figma_import_library_variable to bring it into the current file
Once imported, the variable's id can be used with figma_set_fills / figma_update_variable / any standard variable-binding tool
Filters: libraryName/collectionName accept partial case-insensitive matches.
REQUIRES the Desktop Bridge plugin to be running in Figma Desktop.
Inputs: libraryName, resolvedType, collectionName.
figma_get_selectionA
Get the currently selected nodes in Figma. Returns node IDs, names, types, and dimensions. WebSocket-only — requires Desktop Bridge plugin. Use this to understand what the user is pointing at instead of asking them to describe it.
Inputs: verbose.
figma_get_slide_contentB
Get the content tree of a specific slide including all text, shapes, and frames. Returns node hierarchy with properties.
Inputs: slideId (required).
figma_get_slide_gridB
Get the 2D slide grid layout showing how slides are organized in rows and columns.
Inputs: no named parameters.
figma_get_slide_transitionA
Get the current transition settings for a slide (style, duration, easing curve, timing).
Inputs: slideId (required).
figma_get_slotsA
List SlotNode children on a component, component set, or instance. Returns slot IDs, names, property keys, dimensions, and current child nodes. Use on instances before figma_append_to_slot to discover slot names/IDs.
MULTI-FILE (Local Mode only): Pass fileKey to run this against a specific connected file without switching the active file/target lock (see figma_list_open_files). Does not change the active file or target lock. Cloud Mode pairs with a single plugin instance and rejects fileKey.
Inputs: nodeId (required), fileKey.
figma_get_statusA
Check connection status to Figma Desktop. Reports transport status and connection health via the Desktop Bridge plugin (WebSocket transport). Use probe:true for an active roundtrip verification that the plugin is actually responding.
Inputs: probe.
figma_get_stylesA
Get all styles (color, text, effects, grids) from a Figma file with optional code exports. Use when user asks for: text styles, color palette, design system styles, typography, or style documentation. Returns organized style definitions with resolved values. NOT for design tokens/variables (use figma_get_variables). Set enrich=true for CSS/Tailwind/Sass code examples. Supports verbosity control to manage payload size. TIP: For full design system extraction (tokens + components + styles combined), prefer figma_get_design_system_kit instead — it returns everything in one optimized call.
Inputs: enrich, fileUrl, verbosity, include_usage, +2 more.
figma_get_text_stylesA
Get all local text styles in the current file. Returns style IDs, names, font info, and sizes. Use these IDs when setting textStyleId on text nodes via figma_execute.
Inputs: no named parameters.
figma_get_token_valuesA
Get actual values for design tokens (colors, spacing, etc). Use after figma_get_design_system_summary to get specific token values for implementation.
Inputs: type, limit, filter.
figma_get_variablesA
Extract design tokens and variables from a Figma file with code export support (CSS, Tailwind, TypeScript, Sass). Use when user asks for: design system tokens, variables, color/spacing values, theme data, or code exports. Handles multi-mode variables (Light/Dark themes). NOT for component metadata (use figma_get_component). Returns a compact summary by default — pass format='full' for the complete dataset or format='filtered' with collection/namePattern/mode filters for specific variables. Supports verbosity control to prevent token exhaustion. Resolution order: Desktop Bridge plugin (works on any plan) → Variables REST API (Enterprise only) → Styles API as a partial fallback. TIP: For full design system extraction (tokens + components + styles combined), prefer figma_get_design_system_kit instead — it returns everything in one optimized call.
Inputs: mode, page, enrich, format, +15 more.
figma_import_library_variableA
Import a single variable from a subscribed team library into the current file.
After import, the variable becomes locally addressable by its returned 'id' and can be passed to any tool that binds variables to nodes (fills, strokes, paddings, etc.). The import is idempotent — calling it twice returns the same local id.
WORKFLOW:
Run figma_get_library_variables to find the variable key
Call this tool with that key
Use the returned 'id' with figma_set_fills (boundVariables), figma_update_variable, or other binding tools
REQUIRES the Desktop Bridge plugin and that the source library is subscribed by the current file (otherwise importVariableByKeyAsync rejects).
Inputs: variableKey (required).
figma_import_tokensA
Push design tokens from your codebase into Figma as variables. Bidirectional with figma_export_tokens.
ACCEPTS: DTCG JSON (canonical, fully supported including round-trip metadata preservation). Tokens Studio JSON, CSS custom properties, Tailwind v4 @theme, SCSS, and Style Dictionary v3 are scaffolded but return a NotImplementedError — convert to DTCG first via figma_export_tokens or hand-author DTCG. Use format: "auto" to sniff the input.
APPLY PHASE (full bidirectional sync): toCreate entries create missing collections (with the token file's full mode list) and missing variables in one batched plugin round-trip — literal values first, alias values in a second pass so aliases between newly-created variables resolve. toUpdate entries push value updates in a batched round-trip, INCLUDING alias-target updates: when a token's value is a reference, it's written as a Figma variable alias if the reference resolves to an existing or just-created variable (unresolvable references skip with a warning). toDelete entries are STRICTLY gated behind strategy: "replace" — in replace mode, Figma variables absent from the token file are permanently deleted (a loud warning lists the count); merge (default) preserves them and only reports. Deletes only ever touch collections the token files contain: variables in collections the import doesn't include are left alone. An import that parses 0 tokens is refused, and the diff is computed against live Figma state. Motion tokens are written as TIMING (DTCG duration; a bare number is milliseconds) and EASING (DTCG cubicBezier) variables; springs and holds round-trip through $extensions["figma-console-mcp"].spring. Variable scopes and per-platform codeSyntax (from $extensions["figma-console-mcp"].scopes/.codeSyntax) are diffed and applied too — absent fields mean "no opinion" (Figma-side metadata is preserved), an explicit value is authoritative. Partial-success semantics: per-item errors surface in applyResult.errors[] without failing the batch.
DIFF-AWARE: Default strategy: "merge" diffs against current Figma state and applies only deltas. The hacked-color scenario — designer edits one hex value in their CSS — produces exactly one Figma API update, not a full collection rewrite. Match priority: Figma variable ID (in $extensions["figma-console-mcp"].variableId), then exact token path, then value fingerprint.
CONFLICT HANDLING: When BOTH Figma and code changed the same token since the last sync, onConflict: "ask" (default) surfaces the conflict and writes nothing. Use figma-wins / code-wins to auto-resolve, or skip to leave conflicts alone and proceed with the rest.
DRY-RUN: Default first call after detecting changes is dry-run for safety. The response includes the full diff plan; user confirms, then call again with dryRun: false (or strategy other than dry-run) to apply.
Inputs: files, dryRun, format, prefix, +6 more.
figma_instantiate_componentA
Create an instance of a component from the design system.
CRITICAL: Always pass BOTH componentKey AND nodeId together! Search results return both identifiers. Pass both so the tool can automatically fall back to nodeId if the component isn't published to a library. Most local/unpublished components require nodeId.
IMPORTANT: Always re-search before instantiating! NodeIds are session-specific and may be stale from previous conversations. ALWAYS search for components at the start of each design session to get current, valid identifiers.
VISUAL VALIDATION WORKFLOW: After instantiating components, use figma_take_screenshot to verify the result looks correct. Check placement, sizing, and visual balance.
Inputs: nodeId, variant, parentId, position, +2 more.
figma_lint_designA
Run comprehensive accessibility (WCAG 2.2) and design quality checks on the current page or a specific node tree. WCAG conformance checks (10 rules): color contrast (AA), non-text contrast (1.4.11), color-only differentiation (1.4.1), focus indicators (2.4.7), touch targets (2.5.8), image alt text (1.1.1), heading hierarchy (1.3.1), reflow/responsive (1.4.10), reading order (1.3.2), and disabled context (4.1.2). Best-practice readability hints (opt-in via rules: ['best-practice'] or ['all']): text sizing, line height, letter spacing, paragraph spacing. Note: line/paragraph spacing below 1.5x/2x is NOT a WCAG 1.4.12 failure — 1.4.12 requires supporting user spacing overrides without breaking (a code concern, see figma_scan_code_accessibility), not specific design values — so these are non-normative hints scoped to multi-line text only. Design system checks (5 rules): hardcoded colors, missing text styles, default names, detached components, and token misuse (a semantic token bound to the wrong property, e.g. a bg/* or surface/* variable used as a text fill). Layout checks: missing auto-layout, empty containers. Default audit runs WCAG + design-system + layout (best-practice hints excluded). Returns categorized findings with severity levels (critical/warning/info) and WCAG conformance level (a/aa/aaa/best-practice) so teams can filter by target level. Use natural language like 'check my design for accessibility issues' or 'lint this page'. Requires Desktop Bridge plugin.
Inputs: rules, nodeId, maxDepth, maxFindings.
figma_list_open_filesA
List all Figma files currently connected via the Desktop Bridge plugin. Shows which files have the plugin open and which one is the active target for tool calls. Use figma_navigate to switch between files. WebSocket multi-client mode — each file with the Desktop Bridge plugin maintains its own connection.
Inputs: no named parameters.
figma_list_shadersA
List shaders: the ones applied in this file (fills, strokes and effects), with each property's name, type and default, and the layers using them; plus shaders from the user's libraries (figma.listAvailableShaders). Use the property names with figma_apply_shader. Shaders are created in Figma, not through the Plugin API. Requires Desktop Bridge.
Inputs: scope, nodeId, fileKey.
figma_list_slidesA
List all slides in the current Figma Slides presentation with their IDs, names, grid positions, and skip status. Only works in Slides files.
Inputs: no named parameters.
figma_manage_animation_stylesA
Manage reusable Motion animation styles, the motion layer of a design system.
list_presets: Figma's built-in animation styles with each one's props and defaults.
list: local custom animation styles and their entries.
create: a custom style (name, description) from entries, each a preset with duration, offset, easing and props. Durations and easings can bind to TIMING/EASING variables.
update: rename, change the description, or append entries.
remove_entry: drop one entry (entryId from list).
delete: remove the style. Apply a custom style with figma_apply_animation customStyleId.
Inputs: action (required), name, entries, entryId, +3 more.
figma_move_nodeC
Move a node to a new position within its parent.
Inputs: x (required), y (required), nodeId (required).
figma_post_commentA
Post a comment on a Figma file, optionally pinned to a specific design node. Use after figma_check_design_parity to notify designers of drift when code is the canonical source. Supports replies to existing comment threads. Limitation: @mentions are a Figma UI-only feature — including '@name' in the message renders as plain text, not a clickable mention tag, and does not trigger Figma notifications.
Inputs: message (required), x, y, fileUrl, +2 more.
figma_reconnectA
Force a complete reconnection to Figma Desktop. Use when connection seems stale or after switching files.
Inputs: no named parameters.
figma_reload_pluginA
Reload the current Figma page/plugin to test code changes. Optionally clears console logs before reload. Use when user says: 'reload plugin', 'refresh page', 'restart plugin', 'test my changes'. Returns reload confirmation and current URL. Best for rapid iteration during plugin development.
Inputs: clearConsole.
figma_remove_animationA
Remove animations from a node: one applied animation style (appliedId, from figma_get_animations), one manual keyframe track, or everything (all: true). Returns what's left.
Inputs: nodeId (required), all, fileKey, appliedId, +1 more.
figma_rename_modeB
Rename an existing mode in a Figma variable collection. Requires the Desktop Bridge plugin to be running.
Inputs: modeId (required), newName (required), collectionId (required).
figma_rename_nodeC
Rename a node in the layer panel.
Inputs: nodeId (required), newName (required).
figma_rename_variableA
Rename an existing Figma variable. This updates the variable's name while preserving all its values and settings. Requires the Desktop Bridge plugin to be running.
Inputs: newName (required), variableId (required).
figma_reorder_slidesA
Reorder slides by providing a new 2D array of slide IDs. Each inner array represents a row in the grid. WARNING: This is a destructive operation.
Inputs: grid (required).
figma_reset_slotA
Reset a slot on a component instance to its default (empty) state from the main component. Uses SlotNode.resetSlot().
MULTI-FILE (Local Mode only): Pass fileKey to run this against a specific connected file without switching the active file/target lock (see figma_list_open_files). Does not change the active file or target lock. Cloud Mode pairs with a single plugin instance and rejects fileKey.
Inputs: slotId, fileKey, slotName, instanceId.
figma_resize_nodeB
Resize a node to specific dimensions. By default respects child constraints; use withConstraints=false to ignore them.
Inputs: width (required), height (required), nodeId (required), withConstraints.
figma_scan_code_accessibilityA
Scan HTML code for accessibility violations using axe-core (Deque). Runs structural/semantic checks via JSDOM: ARIA attributes, roles, labels, alt text, form labels, heading order, landmarks, semantic HTML, tabindex, duplicate IDs, lang attribute, and ~50 more rules. Visual checks (color contrast, focus visibility) are disabled in this mode — use figma_lint_design for visual a11y on the design side. Also surfaces a WCAG 1.4.12 (Text Spacing) / 1.4.4 (Resize Text) advisory when typography is locked to fixed px units — the code side is where text-spacing override support is actually verified (a sub-1.5 line height in a design is not itself a failure). Together, these two tools provide full-spectrum accessibility coverage across design and code. Pass component HTML directly or use with figma_check_design_parity for design-to-code a11y comparison. No Figma connection required — this is a standalone code analysis tool.
Inputs: html (required), tags, context, mapToCodeSpec, +1 more.
figma_search_componentsA
Search for components by name, category, or description. Returns paginated results with component keys for instantiation. Automatically loads the design system cache if needed.
NEW: Cross-file library search! Pass a libraryFileKey or libraryFileUrl to search for components in a published shared library (different file). This uses the REST API and requires FIGMA_ACCESS_TOKEN.
Without libraryFileKey/libraryFileUrl, searches the currently open file (local components via Plugin API).
Inputs: limit, query, offset, category, +2 more.
figma_set_annotationsA
Write or clear annotations on a Figma node. Annotations communicate design specs to developers — use them to document animation timings, easing curves, interaction behaviors, accessibility requirements, and implementation notes. Supports plain text labels, rich markdown labels, pinned design properties, and annotation categories. Pass an empty array to clear all annotations. Use mode='append' to add to existing annotations, or mode='replace' (default) to overwrite. Requires Desktop Bridge plugin. This operation is undoable in Figma (Cmd+Z).
Inputs: nodeId (required), annotations (required), mode.
figma_set_descriptionB
Set the description text on a component, component set, or style. Descriptions appear in Dev Mode and help document design intent. Supports plain text and markdown formatting.
Inputs: nodeId (required), description (required), descriptionMarkdown.
figma_set_fillsA
Set the fill colors on a node. Accepts hex or CSS colors, including oklch() and color(display-p3 …). To bind a fill to a design token / color variable, pass that fill's variableId — the variable drives the color and this works on any Figma plan via the bridge (no raw figma_execute needed).
Inputs: fills (required), nodeId (required).
figma_set_image_fillA
Set an image fill on one or more Figma nodes. The imageData parameter accepts a base64-encoded image string (JPEG/PNG). The image is decoded in the browser bridge and passed as raw bytes to the Figma plugin. Requires Desktop Bridge plugin.
Inputs: nodeIds (required), imageData (required), scaleMode.
figma_set_instance_propertiesA
Update component properties on a component instance. IMPORTANT: Use this tool instead of trying to edit text nodes directly when working with component instances. Components often expose TEXT, BOOLEAN, INSTANCE_SWAP, and VARIANT properties that control their content. SLOT properties CANNOT be set here — use figma_append_to_slot to populate slot content. Direct text node editing may fail silently if the component uses properties. This tool handles the #nodeId suffix pattern automatically. Requires Desktop Bridge connection.
Inputs: nodeId (required), properties (required).
figma_set_layoutA
Set a frame's auto layout or grid layout in one call, and place its children. Auto layout: mode HORIZONTAL or VERTICAL, gap, padding, primaryAlign (MIN, CENTER, MAX, SPACE_BETWEEN, SPACE_EVENLY, SPACE_AROUND), counterAlign, wrap with counterAxisGap and alignContent, and sizing (FIXED, HUG, FILL). Grid: mode GRID with tracks written CSS-style (grid.columns: '240px 1fr 1fr', 'repeat(3, 1fr)', 'auto 1fr', or a count), gaps, autoRows, autoFlow, and per-child row, column, spans and alignment. Only the fields you pass change. Returns the resulting layout, with grid tracks as CSS. Requires Desktop Bridge.
Inputs: nodeId (required), gap, grid, mode, +13 more.
figma_set_slide_backgroundB
Set the background color of a slide. Creates or updates a full-slide background rectangle.
Inputs: color (required), slideId (required).
figma_set_slides_view_modeA
Toggle the Figma Slides viewport between grid view and single-slide view.
Inputs: mode (required).
figma_set_slide_transitionB
Set the transition effect for a slide (style, duration, easing curve). Triggers on click by default.
Inputs: style (required), slideId (required), curve, duration.
figma_set_strokesA
Set the stroke (border) on a node. Accepts hex or CSS colors (including oklch() and color(display-p3 …)) and an optional stroke weight. To bind a stroke to a design token / color variable, pass that stroke's variableId — works on any Figma plan via the bridge.
Inputs: nodeId (required), strokes (required), strokeWeight.
figma_set_textA
Set the text content of a text node. Optionally adjust font size and the font family/style, the text wrap style (BALANCE or PRETTY, like CSS text-wrap), and variable-font axes (fontVariations, e.g. {wght: 550}). Font style names are space-sensitive ('Semi Bold', not 'SemiBold'), but this tool auto-corrects common no-space variants and falls back gracefully — so you don't need raw figma_execute to change typography. text can be left out to change only the styling.
Inputs: nodeId (required), text, fontSize, fontStyle, +3 more.
figma_setup_design_tokensA
Create a complete design token structure in one operation: collection, modes, and all variables. Ideal for importing CSS custom properties or design tokens into Figma. Values may be literals OR DTCG-style brace references ('{color.blue.600}', or set-qualified '{primitives.color.blue.600}') that resolve to variable ALIASES — first against variables created in this same call, then against existing local variables. Unresolvable references skip that value with a per-item warning (the rest of the batch still applies), so semantic collections referencing primitives no longer need raw figma_execute. Requires Desktop Bridge plugin.
Inputs: modes (required), tokens (required), collectionName (required).
figma_skip_slideB
Toggle whether a slide is skipped during presentation mode.
Inputs: skip (required), slideId (required).
figma_take_screenshotA
Export an image of the current Figma page or specific node. Uses the Desktop Bridge plugin (exportAsync) when connected — works on any plan, no REST token needed, reflects current runtime state. Falls back to the Figma REST API when the bridge is unavailable or for PDF format. Use for visual validation after design changes — check alignment, spacing, proportions. Pass nodeId to target specific elements. For components, prefer figma_get_component_image.
Inputs: scale, format, nodeId.
figma_update_variableA
Update a single variable's value and/or its description. Pass modeId+value to change the value in a mode; pass description to set the 'How to use this variable' text shown in the Variables panel (and exported as DTCG $description). At least one of {modeId+value} or {description} is required. For many value updates at once, use figma_batch_update_variables (10-50x faster). Use figma_get_variables first for IDs. COLOR: hex '#FF0000', FLOAT: number, STRING: text, BOOLEAN: true/false. Requires Desktop Bridge plugin.
Inputs: variableId (required), value, modeId, description.
figma_watch_consoleA
Stream console logs captured by the Desktop Bridge plugin in real-time for a specified duration (max 5 minutes). Covers code run through the bridge (figma_execute and the write tools) — not other plugins, which run in their own sandboxes. Returns all logs captured during the watch period with summary statistics. NOT for retrieving past logs (use figma_get_console_logs). Best for: watching long-running figma_execute scripts, debugging race conditions, monitoring async operations.
Inputs: level, duration.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 130 tools
Several tools overlap heavily in purpose, especially screenshot/capture tools (figma_take_screenshot, figma_capture_screenshot, figma_get_component_image), component inspection tools (figma_get_component, figma_get_component_for_development, figma_get_component_for_development_deep, figma_analyze_component_set), and variables/token retrieval tools (figma_get_variables, figma_get_library_variables, figma_get_token_values, figma_get_design_system_kit). Descriptions help somewhat, but the boundaries between these retrieval tools are unclear enough that an agent could easily choose the wrong one.
Most tools follow a predictable snake_case pattern with a domain prefix and verb-oriented action (figma_get_*, figma_create_*, figma_set_*, figjam_create_*, figma_ds_*). There are minor deviations such as figma_take_screenshot vs. figma_capture_screenshot and some awkward names like figma_get_design_system_kit, but the overall convention is readable and stable.
130 tools is far beyond what is reasonably scoped for a single MCP server, even one covering as broad a domain as Figma design systems, FigJam, and Slides. The surface is sprawling and includes many niche, overlapping, or workflow-specific tools that should likely be consolidated or split into separate servers.
The server covers an unusually broad lifecycle: variables/tokens, components, node manipulation, comments, version history, accessibility, FigJam, Slides, animations, and shaders. There are still some gaps, such as limited local style creation/editing and no explicit effect-style management, but these are workaroundable via figma_execute and do not represent severe missing operations.
Maintenance
Related MCP Connectors
The Figma MCP server brings Figma design context directly into your AI workflow.
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
A Model Context Protocol server for Wix AI tools
Build and manage your design system with AI: tokens, themes, components, icons, Figma and code.
Related MCP Servers
- FlicenseBqualityNot gradedmaintenanceA Model Context Protocol server that provides access to Figma API functionality, allowing AI assistants like Claude to interact with Figma files, comments, components, and team resources.18826 npm4-
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that integrates Figma design files with AI coding tools like Cursor, Windsurf, and Cline, allowing AI tools to access and understand Figma design data for generating more accurate code.236 npm30MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that connects AI tools and LLMs to Figma designs, enabling them to extract design data, analyze design systems, and generate development documentation.2ISC
- AlicenseBqualityDmaintenanceA Model Context Protocol server that enables AI agents to programmatically create, modify, and manage Figma documents via a WebSocket bridge and Figma plugin.116MIT