Figma Console MCP - Setup Guide
Complete setup instructions for connecting Figma Console MCP to various AI clients (Claude Desktop, Cursor, Windsurf, etc.).Quick Start: For most users, we recommend Remote Mode with the UI-based setup method - just paste a URL, no config files needed.
🚀 Remote Mode Setup (Recommended)
Prerequisites
- None! Just Claude Desktop installed
Method 1: UI-Based Setup (Recommended)
This is the new, easier way to add MCP servers in Claude Desktop. Steps:-
Open Claude Desktop Settings
- macOS: Claude menu → Settings
- Windows: File menu → Settings
-
Navigate to Connectors
- Click “Connectors” in the left sidebar
-
Add Custom Connector
- Click “Add Custom Connector” button
- You’ll see a dialog with two fields
-
Enter Connection Details
- Name:
Figma Console(or any name you prefer) - URL:
https://figma-console-mcp.southleft.com/sse - Click “Add”
- Name:
-
Verify Connection
- Look for “Figma Console” in your connectors list
- Status should show “Connected” or “CUSTOM” badge
Method 2: JSON Config File (Legacy Method)
Note: This method still works but is more complex. Use Method 1 (UI) unless you have a specific reason to edit the config file.For advanced users who prefer config file editing:
-
Locate config file:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
- macOS:
-
Edit the file:
- Save and restart Claude Desktop
- Verify: Look for 🔌 icon in bottom-right showing “figma-console: connected”
🔧 Local Mode Setup (Advanced)
⚠️ Important: Local mode is for advanced users who need the Figma Desktop Bridge plugin or direct console debugging. Most users should use Remote Mode.
Prerequisites
- Node.js 18+ installed
- Figma Desktop installed
- Git installed
- Terminal access
Installation Steps
1. Install the MCP Server
2. Get Figma Personal Access Token
- Visit https://www.figma.com/developers/api#access-tokens
- Click “Get personal access token”
- Enter description: “Figma Console MCP Local”
- Click “Generate token”
- Copy the token (you won’t see it again!)
3. Configure Claude Desktop (JSON Method Only)
Note: Local mode MUST use JSON config method - UI method only works for remote URLs.
-
Locate config file:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
- macOS:
-
Edit the file:
Important:
- Replace
/absolute/path/to/figma-console-mcpwith actual absolute path - Replace
figd_XXX...with your actual Figma token - Use forward slashes
/even on Windows
- Replace
- Save the file
4. Restart Figma Desktop with Remote Debugging
⚠️ CRITICAL STEP: You MUST restart Figma with the debug flag for local mode to work. macOS:5. Verify Setup
-
Check remote debugging is active:
- Open Chrome browser
- Visit: http://localhost:9222
- You should see a list of inspectable Figma pages
-
Restart Claude Desktop
- Quit completely and relaunch
-
Test the connection:
- Ask Claude: “Check Figma status”
- Should show: ”✅ Figma Desktop connected via port 9222”
📦 NPX Installation (Local Mode Alternative)
Note: This is an alternative to Local Git installation. Both use the same code and require the same prerequisites (Node.js, Figma Desktop with debug port, Personal Access Token).
Why Use NPX?
- ✅ No git clone required
- ✅ Automatic updates with
@latest - ✅ Same functionality as Local Git mode
NPX Configuration
@latest.
What You Get With Each Mode
Remote Mode (UI Setup)
- ✅ All MCP tools
- ✅ OAuth authentication (automatic, no token needed)
- ✅ Design system extraction (variables*, components, styles)
- ✅ Console logs and screenshots
- ✅ Zero maintenance
- ❌ No Desktop Bridge plugin (can’t access local variables without Enterprise)
Local Mode (JSON Setup)
- ✅ All MCP tools
- ✅ Desktop Bridge plugin support (access local variables, no Enterprise needed)
- ✅ Zero-latency console debugging
- ✅ Reliable component descriptions (bypasses API bugs)
- ⚠️ Manual token management (PAT required)
- ⚠️ Requires Figma restart with debug flag
Troubleshooting
Remote Mode Issues
“Connection failed” in UI:- ✅ Check internet connection
- ✅ Try removing and re-adding the connector
- ✅ Restart Claude Desktop
- ✅ This is normal for first design system tool use
- ✅ Your browser will open automatically
- ✅ Click “Allow” to authorize
- ✅ Expected if you don’t have Enterprise plan
- ✅ Solution: Switch to Local Mode + Desktop Bridge plugin
- ✅ See MODE_COMPARISON.md for details
Local Mode Issues
“Failed to connect to Figma Desktop”:- ✅ Verify Figma was restarted with
--remote-debugging-port=9222 - ✅ Visit http://localhost:9222 in Chrome - should show pages
- ✅ If blank, quit Figma and relaunch with debug flag
- ✅ Check token is set in
claude_desktop_config.json - ✅ Verify no typos in token (should start with
figd_) - ✅ Token must be in
envobject as shown above
- ✅ Install Node.js 18+ from https://nodejs.org
- ✅ Restart terminal/Claude Desktop after install
- ✅ Verify with:
node --version
- ✅ Run
npm installin the figma-console-mcp directory - ✅ Run
npm run build:localagain - ✅ Check that
dist/local.jsfile exists
- ✅ Kill other Chrome/Figma processes using that port
- ✅ Run:
lsof -i :9222(macOS) or check Task Manager (Windows) - ✅ Restart Figma with debug flag
Switching Between Modes
Remote → Local
- Remove remote connector from Claude Desktop
- Follow Local Mode setup steps above
- Restart Claude Desktop
Local → Remote
- Remove local MCP config from
claude_desktop_config.json - Use UI method to add remote connector
- Restart Claude Desktop
Next Steps
After connecting:-
Test basic tools:
- “Navigate to https://www.figma.com and check status”
- “Get design variables from [your Figma file URL]”
-
For Local Mode users - Install Desktop Bridge plugin:
- See Figma Desktop Bridge README
- Enables variables without Enterprise API
-
Read tool documentation:
- See TOOLS.md for all 36+ available tools
- See USE_CASES.md for example workflows