@mp3wizard/figma-console-mcp
v1.17.3
Published
MCP server for accessing Figma plugin console logs and screenshots via Cloudflare Workers or local mode
Maintainers
Readme
Figma Console MCP Server
Your design system as an API. Model Context Protocol server that bridges design and development—giving AI assistants complete access to Figma for extraction, creation, and debugging.
🔒 Security Reviewed Fork: This fork (
@mp3wizard/figma-console-mcp) has passed a full security review following OWASP Top 10 and CWE standards, including automated scanning (Semgrep, Trivy, TruffleHog) and manual vulnerability analysis. Review reports are available in theSecurity review report/folder.
🆕 FigJam + Slides — AI Across All Figma Products: 24 new tools bring AI to FigJam boards and Figma Slides. Create stickies, flowcharts, and tables on whiteboards. Manage entire presentations — slides, transitions, content, and reordering. FigJam Guide → | Slides Guide →
What is this?
Figma Console MCP connects AI assistants (like Claude) to Figma, enabling:
- 🐛 Plugin debugging - Capture console logs, errors, and stack traces
- 📸 Visual debugging - Take screenshots for context
- 🎨 Design system extraction - Pull variables, components, and styles
- ✏️ Design creation - Create UI components, frames, and layouts directly in Figma
- 🔧 Variable management - Create, update, rename, and delete design tokens
- ⚡ Real-time monitoring - Watch logs as plugins execute
- 📌 FigJam boards - Create stickies, flowcharts, tables, and code blocks on collaborative boards
- ☁️ 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
⚡ 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) | Cloud Mode | ~5 min | | Contribute to the project | Local Git Setup | ~15 min | | Just explore my design data (read-only) | Remote SSE | ~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) | ✅ | ❌ | ❌ | | Desktop Bridge plugin | ✅ | ✅ | ❌ | | Requires Node.js | Yes | No | No | | Total tools available | 84+ | 43 | 22 |
Bottom line: Remote SSE is read-only with ~38% of the tools. Cloud Mode unlocks write access from web AI clients without Node.js. NPX/Local Git gives the full 84+ tools with real-time monitoring.
🚀 NPX Setup (Recommended)
Best for: Designers who want full AI-assisted design capabilities.
What you get: All 84+ 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 MCP - 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 @mp3wizard/figma-console-mcp@latestCursor / Windsurf / Claude Desktop:
Add to your MCP config file (see Where to find your config file below):
{
"mcpServers": {
"figma-console": {
"command": "npx",
"args": ["-y", "@mp3wizard/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 | ~/Library/Application Support/Claude/claude_desktop_config.json | %APPDATA%\Claude\claude_desktop_config.json |
| Claude Code (CLI) | ~/.claude.json | %USERPROFILE%\.claude.json |
| Cursor | ~/.cursor/mcp.json | %USERPROFILE%\.cursor\mcp.json |
| Windsurf | ~/.codeium/windsurf/mcp_config.json | %USERPROFILE%\.codeium\windsurf\mcp_config.json |
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)
- Go to Plugins → Development → Import plugin from manifest...
- Select
~/.figma-console-mcp/plugin/manifest.json(stable path, auto-created by the MCP server) - Run the plugin in your Figma file — the bootloader finds the MCP server and loads the latest UI automatically
One-time setup. The plugin uses a bootloader that dynamically loads fresh code from the MCP server — no need to re-import when the server updates.
Upgrading from v1.14 or earlier? Your existing plugin still works, but to get the bootloader benefits (no more re-importing), do one final re-import from
~/.figma-console-mcp/plugin/manifest.json. The path is created automatically when the MCP server starts. Runnpx @mp3wizard/figma-console-mcp@latest --print-pathto see it. After this one-time upgrade, you're done forever.
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 84+ 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: 9 read-only tools — view data, take screenshots, read logs, 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
- Name:
- 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: 76 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 plugin - The 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 | 84+ | 43 | 84+ | 22 (read-only) |
| 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 | ✅ (@latest) | ✅ | Manual (git pull) | ✅ |
| 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 84+ 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
- Add to MCP config as
FIGMA_ACCESS_TOKENenvironment variable
🛠️ Available Tools
Navigation & Status
figma_navigate- Open Figma URLsfigma_get_status- Check connection status
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- Capture UI screenshots
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 data
☁️ 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 designs- Create frames, shapes, text, components
- Apply auto-layout, styles, effects
- Build complete UI mockups programmatically
figma_arrange_component_set- Organize variants into professional component sets- Convert 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 descriptions- Add descriptions to components, component sets, and styles
- Supports markdown formatting for rich documentation
- Descriptions appear in Dev Mode for developers
🔍 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
🔧 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
📌 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_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 specific slidefigma_add_shape_to_slide- Add rectangle or ellipse shapes with colorfigma_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 blocks - Components are instantiated with proper variants and properties via
figma_instantiate_component - Custom elements are created using the full Figma Plugin API via
figma_execute - Visual 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-desktop-bridge/manifest.jsonfrom the figma-console-mcp directory - 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_execute - Variable 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 84+ 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.
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 bootloader plugin scans all ports and connects to every active server
- Orphaned processes from closed tabs are automatically cleaned up on startup
- No re-importing, no manual port management
🧩 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
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 Official MCP
Figma Console MCP (This Project) - Debugging, data extraction, and design creation
- ✅ Real-time console logs from Figma plugins
- ✅ Screenshot capture and visual debugging
- ✅ Error stack traces and runtime monitoring
- ✅ Raw design data extraction (JSON)
- ✅ FigJam board creation and reading (stickies, flowcharts, tables)
- ✅ Works remotely or locally
Figma Official Dev Mode MCP - Code generation
- ✅ Generates React/HTML code from designs
- ✅ Tailwind/CSS class generation
- ✅ Component boilerplate scaffolding
Use both together for the complete workflow: generate code with Official MCP, then debug and extract data with Console MCP.
🛤️ Roadmap
Current Status: v1.17.0 (Stable) - Production-ready with FigJam + Slides support, Cloud Write Relay, Design System Kit, WebSocket-only connectivity, smart multi-file tracking, 84+ tools, Comments API, and MCP Apps
Recent Releases:
- [x] v1.17.0 - Figma Slides Support: 15 new tools for managing presentations — slides, transitions, content, reordering, and navigation. Inspired by Toni Haidamous (PR #11).
- [x] v1.16.0 - FigJam Support: 9 new tools for creating and reading FigJam boards — stickies, flowcharts, tables, code blocks, and connection graphs. Community-contributed by klgral and lukemoderwell.
- [x] v1.12.0 - Cloud Write Relay: web AI clients (Claude.ai, v0, Replit, Lovable) can create and modify Figma designs via cloud relay pairing — no Node.js required
- [x] v1.11.2 - Screenshot fix:
figma_take_screenshotworks without explicitnodeIdin WebSocket mode - [x] v1.11.1 - Doc generator fixes: clean markdown tables, Storybook links, property metadata filtering
- [x] v1.11.0 - Complete CDP removal, improved multi-file active tracking with focus detection
- [x] v1.10.0 - Multi-instance support (dynamic port fallback 9223–9232, multi-connection plugin, instance discovery)
- [x] v1.9.0 - Figma Comments tools, improved port conflict detection
- [x] v1.8.0 - WebSocket Bridge transport (CDP-free connectivity), real-time selection/document tracking,
figma_get_selection+figma_get_design_changestools - [x] v1.7.0 - MCP Apps (Token Browser, Design System Dashboard), batch variable operations, design-code parity tools
- [x] v1.5.0 - Node manipulation tools, component property management, component set arrangement
- [x] v1.3.0 - Design creation via
figma_execute, variable CRUD operations
Coming Next:
- [ ] Component template library - Common UI pattern generation
- [ ] Visual regression testing - Screenshot diff capabilities
- [ ] Design linting - Automated compliance and accessibility checks
- [ ] AI enhancements - Intelligent component suggestions and auto-layout optimization
💻 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
- 🐛 Report Issues
- 💬 Discussions
- 🌐 Model Context Protocol
- 🎨 Figma API
