An open-source Chromium extension that bridges Figma node data directly from an active browser tab to a local Model Context Protocol (MCP) server — without a Figma REST API token or Personal Access Token (PAT).
Instead of hitting the REST API, this extension injects a script into the Figma page's MAIN JavaScript world and reads node data directly from window.figma — the same in-memory Plugin API that Figma plugins use. This gives you instant access to the live document tree: typography, fills, auto-layout, dimensions, and the full recursive child hierarchy.
Free Figma MCP Server
स्टार
4
टूल
—
अपटाइम
—
Features
No API Token Required — No Figma PAT, no OAuth, no rate limits.
Full Node Tree — Recursively serializes all children of a node: frames, text layers, images, vectors, and nested components.
Plugin API Access — Reads from window.figma directly (same data source as Figma plugins), not the REST API.
WebSocket Bridge — Connects to a local MCP server at ws://127.0.0.1:9223 with automatic reconnect and exponential backoff.
Real-Time Selection Tracking — Emits SELECTION_CHANGED events when you select a different layer in Figma.
Resilient Service Worker — Keep-alive ports and alarm heartbeats prevent the MV3 service worker from being suspended.
Navigate to a Figma design file in Chrome (URL must contain /design/, /file/, or /board/). The extension auto-injects inject.js into the page's MAIN world as soon as the tab finishes loading.
Step 2 — Register the Figma Object (One-Time Per Session)
Figma exposes its in-memory Plugin API via window.figma, but it initialises asynchronously after the editor boots. You need to hand it to the bridge once per session.
Open DevTools on the Figma tab (F12 or Cmd+Option+I) and run:
injectFigma(window.figma)
You will see this confirmation in the console:
[Figma MCP] figma object registered. Bridge is ready.
Why is this needed?
Figma's window.figma object is only available after the editor fully initialises — not at page load time. The injectFigma() function is exposed by inject.js as a bridge hook so you can hand off the live figma instance once the editor is ready. This is a one-time step per tab session (after reload or navigation you repeat it).
Step 3 — Use the MCP Tools
get_figma_node
Fetch the full node tree for a specific node ID.
fileKey — the segment after /design/ in the Figma URL
nodeId — the node ID (e.g. "474-11039" or "474:11039")
Fetch the node currently selected in the active Figma tab (no arguments needed). The extension tracks URL-based selection changes automatically via a 500ms poller.
Output Format
Each node is serialized recursively, including all children:
The extension wasn't loaded yet or the Figma tab wasn't refreshed after loading the extension. Hard-refresh the Figma tab (Ctrl+Shift+R) and wait for the editor to fully load.
[Figma MCP] figma object registered but requests still fail
The WebSocket connection to the MCP server may be down. Make sure npm start is running in the server/ directory.
Request timeout (10s)
The bridge is connected but window.figma was not registered. Run injectFigma(window.figma) in the DevTools console.
Node not found
The node ID doesn't exist in the currently open Figma file. Check that the fileKey in your request matches the file open in the browser tab.
Service worker suspended
Chrome MV3 service workers go idle after ~30s of inactivity. Selecting a layer in Figma wakes the worker immediately via the content script keep-alive.
अभी टूल सूची नहीं है। रिमोट सर्वर को पहले हेल्थ चेक के बाद सूची मिलती है।
FAQ
सवाल
Figma MCP Browser कैसे इंस्टॉल करें?
इस पेज पर Cursor, Claude Desktop, Claude Code या VS Code के लिए stdio कॉन्फ़िग कॉपी करें। यह पब्लिशर का इंस्टॉल इस्तेमाल करता है, PlugMCP प्रॉक्सी नहीं।
क्या Figma MCP Browser के लिए API key चाहिए?
इस रिकॉर्ड में कोई ज़रूरी एनवायरनमेंट वेरिएबल दर्ज नहीं है।
Figma MCP Browser कौन सा ट्रांसपोर्ट इस्तेमाल करता है?
Figma MCP Browser stdio पर लोकल चलता है।
Figma MCP Browser की पिछली जाँच कब हुई थी?
पिछली जाँच 2026-10-28 को हुई। Free Figma MCP Server