Figma MCP Bridge
Provides tools for interacting with Figma design files and FigJam boards through a Figma plugin, enabling AI agents to read document structure, selections, nodes, styles, variables, prototypes, and screenshots, and to author/update components, variants, instances, text, shapes, images, SVG layers, auto-layout, effects, animations, and other node properties.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Figma MCP Bridge
This is a fork ofgethopp/figma-mcp-bridge that adds authoring tools for components, variants, component properties, instances, styles, variables, per-range text styling and boolean operations (see the Available Tools table). The npx @gethopp/figma-mcp-bridge package and the published plugin do not include them: build this repo and use the Local development setup instead. The development plugin is named MCP Bridge LOCAL + Components so it can't be confused with the published one.
Requires the Figma desktop app (macOS/Windows). The browser version of Figma does not support importing development plugins.
While other amazing Figma MCP servers like Figma-Context-MCP exist, one issues is the API limiting for free users.
The limit for free accounts is 6 requests per month, yes per month.
Figma MCP Bridge is a solution to this problem. It is a plugin + MCP server that streams live Figma document data to AI tools without hitting Figma API rate limits, so its Figma MCP for the rest of us ✊
It supports multiple Figma files connected simultaneously; open the plugin in each file and your AI agent can query any of them by fileKey. Single-file setups work exactly as before with no changes required.
It also includes a small, opt-in set of write tools for safe agent-driven edits — see Editing Notes below.
Demo
Watch a demo of building a UI in Cursor with Figma MCP Bridge

Related MCP server: Talk to Figma MCP
Quick Start
1. Add the MCP server to your favourite AI tool
Add the following to your AI tool's MCP configuration (e.g. Cursor, Windsurf, Claude Desktop):
{
"figma-bridge": {
"command": "npx",
"args": ["-y", "@gethopp/figma-mcp-bridge"]
}
}That's it — no binaries to download or install.
2. Add the Figma plugin
Download the plugin from the latest release page, then in Figma go to Plugins > Development > Import plugin from manifest and select the manifest.json file from the plugin/ folder. The same plugin runs in Figma design files, Dev Mode (read-only), and FigJam boards.
3. Start using it 🎉
Open a Figma file, run the plugin, and start prompting your AI tool. The MCP server will automatically connect to the plugin.
To work across multiple files, just open the plugin in each Figma file. The bridge keeps all connections active and your AI agent can target any of them by fileKey.
If you want to know more about how it works, read the How it works section.
Available Tools
Tool | Description |
| List all connected Figma files (supports multi-file workflows) |
| Get the current Figma page document tree |
| Get the currently selected nodes in Figma |
| Get a specific Figma node by ID (colon format, e.g. |
| Read prototype interactions on a node and its descendants |
| Trace prototype navigation between screens |
| Get all local paint, text, effect, and grid styles |
| Get file name, pages, and current page info |
| Get a depth-limited tree optimized for understanding design context |
| Get all variable collections, modes, and values (design tokens) |
| Export nodes as PNG/SVG/JPG/PDF (base64-encoded) |
| Export and save screenshots directly to the local filesystem |
| List all available animation presets (beta) |
| Read a node's current animation styles and properties (beta) |
| Apply a preset animation style to a node (beta) |
| Remove an applied animation style from a node (beta) |
| Apply a manual keyframe track to a node property (beta) |
| Remove a manual keyframe track from a node property (beta) |
| Set the duration of a timeline in seconds (beta) |
| Show or hide specific nodes |
| Replace the contents of a text node (TEXT, FigJam sticky, or shape label) |
| Patch font, size, alignment, auto-resize, color, and bounds on text nodes/sublayers |
| Patch common node properties: name, position, size, visibility, opacity, corner radius (single or batch) |
| Set native Figma constraints (horizontal/vertical) for one or multiple compatible nodes |
| Link local Figma Paint Styles to fills or strokes (single or batch), preserving the native style ID |
| Replace a node's fill or stroke with a single solid paint |
| Replace a node's fill or stroke with a linear/radial/angular/diamond gradient |
| Replace a node's effects list (drop/inner shadows, layer/background blurs) |
| Patch stroke weight, align, dash pattern, cap, and join |
| Configure auto-layout direction, padding, gap, alignment, sizing, and wrap (not sections) |
| Create a new page in the document, optionally switching to it |
| Create a new frame, optionally under a parent |
| Create a section — a named, resizable container (Figma and FigJam) |
| Create a new text node |
| Create a rectangle, ellipse, or line |
| Create a FigJam shape with its own text label (SHAPE_WITH_TEXT), incl. text fill |
| Create an image-backed rectangle from a local path, URL, or data URI |
| Import raw SVG markup or a workspace-local SVG file as editable vector layers |
| Create a sticky note in FigJam |
| Create a connector between two nodes in FigJam, with attachment anchors |
| Bulk-import an html-figma layer tree (JSON) as frames, text, rectangles, and vectors |
| Duplicate nodes in place |
| Duplicate nodes and move each duplicate by a fixed offset |
| Resize a SECTION around its children with optional padding |
| Space 3+ nodes with equal horizontal gaps (first/last stay fixed) |
| Space 3+ nodes with equal vertical gaps (first/last stay fixed) |
| Snap node positions to a grid of the given size |
| Move a node below another with gap and start/center alignment |
| Move a node to the right of another with gap and start/center alignment |
| Move nodes into another parent |
| Wrap a list of nodes (sharing a parent) in a new group |
| Ungroup a group or frame — children move up to its parent |
| List local components and component sets (current page, or all pages) |
| Read property definitions of a component/set, or values and bindings of an instance/layer |
| Convert one or multiple nodes into main components |
| Combine components into a component set (variants) |
| Create an instance of a component or of a set's default variant |
| Add a BOOLEAN, TEXT, INSTANCE_SWAP or VARIANT property to a component or set |
| Rename a component property or change its default value |
| Delete a component property with explicit confirmation |
| Bind (or unbind) a layer's visibility, text or nested instance to a component property |
| Set property values on instances (switch variant, toggle, text, swap) |
| Detach instances from their main component into plain frames |
| Combine shapes with union, subtract, intersect or exclude |
| Style a character range of a text layer (font, size, color, links, Text Style) |
| Create a local Paint Style from a solid color |
| Create a local Text Style |
| Create a variable collection with named modes |
| Create a COLOR, FLOAT, STRING or BOOLEAN variable with per-mode values or aliases |
| Set a variable's per-mode values or alias |
| Bind (or unbind) a node's fill, stroke, size, spacing, radius, opacity, visibility or text to a variable |
| Delete a local style with explicit confirmation |
| Delete a local variable with explicit confirmation |
| Delete a local variable collection and its variables with explicit confirmation |
| Set the page selection to a list of node IDs (works in Dev Mode) |
| Frame the viewport around the given nodes (works in Dev Mode) |
| Delete nodes with explicit confirmation |
| Run Plugin API JavaScript in the plugin sandbox (opt-in, see Editing Notes) |
All tools accept an optional fileKey parameter when multiple Figma files are connected. Use list_files to discover connected files and their keys.
Prototype Notes
Prototype tools are read-only and unavailable in FigJam. Set
includePrototype: trueonget_nodeto include the same interactions.Reactions are Figma's own trigger and action data, with destinations, variables, and modes resolved to names.
Flow edges list their enclosing branch
conditionsfrom outermost to innermost (nullmarks an else branch).Observed
AFTER_TIMEOUTvalues are in seconds (for example,0.8for 800 ms).
Editing Notes
Edit tools work only when the plugin is opened in Figma's design editor (Dev Mode is read-only — they will return a clear error there).
In FigJam, read tools plus the write tools (
set_text_content,set_text_properties,set_node_properties,set_solid_fill,create_text,create_shape,create_shape_with_text,create_sticky,create_connector,create_section,duplicate_nodes,duplicate_with_offset,fit_to_content,distribute_horizontally,distribute_vertically,align_to_grid,place_below,place_right_of,delete_nodes, ...) are available. Auto-layout and motion/animation tools return a clear error in FigJam.set_text_content/set_text_propertiesedit a TEXT node's content directly, or the text sublayer of a FigJam STICKY / SHAPE_WITH_TEXT node. Alignment and auto-resize are TEXT-node-only — they return a clear error on stickies and shapes (x/y/width/height still apply to the containing node).set_node_propertiesaccepts eithernodeIdor anodeIdsarray to apply the same property changes to several nodes in one call.apply_paint_styleacceptsnodeIdornodeIds, a localstyleIdfromget_styles, andtarget(filldefault, orstroke). It works in Figma Design only, applies the native style (replacing paints on the selected target), and reports the linked ID; a batch reports successes and per-node errors.get_nodeexposesstyles.fillStyleIdandstyles.strokeStyleIdfor independent verification (an empty ID means unlinked;mixedmeans the property has mixed values across the node). It does not import shared libraries or style individual text ranges.set_node_constraintsacceptsnodeIdornodeIdswithhorizontaland/orvertical(MIN,MAX,CENTER,STRETCH,SCALE).MINmeans Left/Top,MAXRight/Bottom, andSTRETCHLeft & Right/Top & Bottom. Unspecified axes are preserved. It requires nodes inside a Figma frame, component, or instance; Auto Layout children must use absolute positioning. It is unavailable in FigJam and Dev Mode. The response reports previous and applied constraints.set_auto_layouttargets frames; SECTION nodes have no auto-layout in Figma's API and return an explicit error.Component tools (
list_components,get_component_properties,create_component,create_component_set,create_instance,add_component_property,edit_component_property,delete_component_property,bind_component_property,set_instance_properties,detach_instance) work in Figma Design only: they are unavailable in FigJam, and the write tools are unavailable in Dev Mode. Variant properties are derived from component names (State=Hover, Size=Large), so name components withset_node_propertiesaroundcreate_component_set. BOOLEAN, TEXT and INSTANCE_SWAP property names carry a#idsuffix; read exact names withget_component_properties. A variant passed to the property tools resolves to its component set.delete_component_propertyrequiresconfirm: true.list_componentsonly sees local components, not ones from shared libraries.boolean_operation,create_paint_style,create_text_style,create_variable_collection,create_variable,set_variable_valuesandbind_variablework in Figma Design only.set_text_range_stylealso works on FigJam stickies and shapes. All are unavailable in Dev Mode.set_text_range_styletakesstart(inclusive) andend(exclusive) character indexes, defaulting to the whole text. AtextStyleIdis applied first, so other properties in the same call override it. Fonts must be available to Figma.Variable values are keyed by mode name or modeId. COLOR values are hex (
#RRGGBBor#RRGGBBAA); any value can be{ "alias": "<variableId>" }.bind_variableonfillorstrokebinds the first solid paint and adds one if the node has none.delete_style,delete_variableanddelete_variable_collectionrequireconfirm: trueand refuse library items; deleting a collection deletes its variables. Renaming styles, variables and collections, creating effect styles, and setting a frame's variable mode are not covered.fit_to_contentworks on SECTION nodes only (Figma's API exposes no equivalent for other containers): it shifts children so their bounding box starts atpaddingand resizes the section to bbox + 2×padding.The current user must have permission to edit the target file.
delete_nodesis intentionally gated behindconfirm: true.run_scriptexecutes arbitrary JavaScript in the open file, so it is off unless the MCP server runs withFIGMA_BRIDGE_ENABLE_RUN_SCRIPT=1(see Enablingrun_script). The code is the body of an async function withfigmain scope, and itsreturnvalue must be JSON-serializable. Code that calls.remove()is rejected unlessallowRemove: trueis passed; this guards against accidental deletions and is not a security boundary. The server stops waiting after 3 minutes, but a script stuck in a loop keeps the plugin busy until it is closed. Works in Figma and FigJam.Text edits automatically load the fonts currently used by the target text node before applying the new content.
New text nodes default to
Inter Regularunless a font is provided.create_imagereads local paths relative to the MCP server working directory unless you pass an absolute path.create_svgaccepts raw<svg>markup or a local SVG path inside the MCP server working directory. SVG payloads are limited to 2 MiB.import_html_layerstakes a JSON file produced by html-figma's browserhtmlToFigma(). The path resolves relative to the MCP server working directory and must stay inside it, even when absolute. Everything lands inside one wrapper frame, and the response reportslayerCountagainstexpectedLayerCountso partial imports are visible.create_pagereturns the new page's ID — pass it asparentIdtocreate_frame/create_text/create_shape/create_imageto author content on that page without switching the editor.
Enabling run_script
run_script is off by default. To turn it on, add FIGMA_BRIDGE_ENABLE_RUN_SCRIPT to the server's env in your MCP configuration and restart your AI tool:
{
"figma-bridge": {
"command": "npx",
"args": ["-y", "@gethopp/figma-mcp-bridge"],
"env": {
"FIGMA_BRIDGE_ENABLE_RUN_SCRIPT": "1"
}
}
}If several AI tools run the bridge at the same time, set the variable in each of their configurations. Only one bridge process talks to Figma at a time, and it rejects run_script unless it was started with the variable.
What You Can Build
With the current write surface, an agent can build a basic slide deck in a new empty Figma file: create slide frames, style titles and body copy, lay out rectangles/ellipses/lines for cards and dividers, duplicate slide templates, reparent content into the right frame, and adjust common geometry/visual properties — including solid/gradient paints, shadows and blurs, stroke geometry, and auto-layout configuration.
The current version is intentionally limited — no components/instances, no variables/styles authoring, no per-segment text styling, and no vector boolean operations yet.
Local development
This repo uses Bun as its package manager and script runner throughout. Install it first if you don't have it.
1. Clone this repository locally
git clone git@github.com:gethopp/figma-mcp-bridge.git2. Install root tooling
Install the root dependencies once. This runs Husky's prepare script, which installs the Git pre-commit hook that formats staged files with Prettier.
cd figma-mcp-bridge && bun install3. Build the server
cd server && bun install && bun run build4. Build the plugin
cd plugin && bun install && bun run build5. Add the MCP server to your favourite AI tool
For local development, add the following to your AI tool's MCP config:
{
"figma-bridge": {
"command": "node",
"args": ["/path/to/figma-mcp-bridge/server/dist/index.js"]
}
}Code style
The repo is formatted with Prettier (config in .prettierrc). A Husky pre-commit hook runs lint-staged, which formats only your staged files, so commits stay formatted automatically. You can also run it manually:
bun run format # format the whole repo
bun run format:check # verify formatting without writing (useful in CI)Structure
Figma-MCP-Bridge/
├── plugin/ # Figma plugin (TypeScript/React)
└── server/ # MCP server (TypeScript/Node.js)
└── src/
├── index.ts # Entry point
├── bridge.ts # WebSocket bridge to Figma plugin
├── leader.ts # Leader: HTTP server + bridge
├── follower.ts # Follower: proxies to leader via HTTP
├── node.ts # Dynamic leader/follower role switching
├── election.ts # Leader election & health monitoring
├── tools.ts # MCP tool definitions
└── types.ts # Shared typesHow it works
There are two main components to the Figma MCP Bridge:
1. The Figma Plugin
The Figma plugin is the user interface for the Figma MCP Bridge. You run this inside the Figma file you want to use the MCP server for, and its responsible for getting you all the information you need.
2. The MCP Server
The MCP server is the core of the Figma MCP Bridge. It maintains a registry of WebSocket connections keyed by fileKey, so multiple Figma files can be connected simultaneously. The server is responsible for:
Handling WebSocket connections from one or more Figma plugin instances
Routing tool calls to the correct file based on
fileKeyForwarding responses back to the AI client
Handling leader election (as we can have only one WS connection to an MCP server at a time)
The leader listens on 127.0.0.1 only. Its endpoints have no authentication, so other machines on the network must not reach them. If the plugin runs on another host (for example, the MCP server runs in a VM or a container), set FIGMA_BRIDGE_HOST=0.0.0.0 (or ::) in the MCP server environment. Use this only on a network that you trust.
┌─────────────────────────────────────────────────────────────────────────────┐
│ FIGMA (Desktop app) │
│ ┌───────────────────────────────────────────────────────────────────────┐ │
│ │ Figma Plugin │ │
│ │ (TypeScript/React) │ │
│ └───────────────────────────────────────────────────────────────────────┘ │
└─────────────────────────────────────────────────────────────────────────────┘
│
│ WebSocket
│ (ws://localhost:1994/ws)
▼
┌─────────────────────────────────────────────────────────────────────────────┐
│ PRIMARY MCP SERVER │
│ (Leader on :1994) │
│ ┌─────────────────────────────────────────────────────────────────────┐ │
│ │ Bridge Endpoints: │ │
│ │ • Manages WebSocket conn • /ws (plugin) │ │
│ │ • Forwards requests to plugin • /ping (health) │ │
│ │ • Routes responses back • /rpc (followers) │ │
│ └─────────────────────────────────────────────────────────────────────┘ │
└─────────────────────────────────────────────────────────────────────────────┘
▲ ▲
│ HTTP /rpc │ HTTP /rpc
│ POST requests │ POST requests
│ │
┌─────────────────┴───────────┐ ┌─────────────┴───────────────┐
│ FOLLOWER MCP SERVER 1 │ │ FOLLOWER MCP SERVER 2 │
│ │ │ │
│ • Pings leader /ping │ │ • Pings leader /ping │
│ • Forwards tool calls │ │ • Forwards tool calls │
│ via HTTP /rpc │ │ via HTTP /rpc │
│ • If leader dies → │ │ • If leader dies → │
│ attempts takeover │ │ attempts takeover │
└─────────────────────────────┘ └─────────────────────────────┘
▲ ▲
│ │
│ MCP Protocol │ MCP Protocol
│ (stdio) │ (stdio)
▼ ▼
┌─────────────────────────────┐ ┌─────────────────────────────┐
│ AI Tool / IDE 1 │ │ AI Tool / IDE 2 │
│ (e.g., Cursor) │ │ (e.g., Cursor) │
└─────────────────────────────┘ └─────────────────────────────┘Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
The Figma MCP server brings Figma design context directly into your AI workflow.
Give AI agents your deeepSpace design system: components, tokens, styles and code mappings.
A real-time, multiplayer filesystem for agents and humans: shared files, live edits, history.
Live React design-system APIs, patterns, and code validation so AI agents build real UI, not slop.
Related MCP Servers
- -licenseCqualityNot gradedmaintenanceEnables AI agents to interact with Figma in real-time through a WebSocket connection. Supports comprehensive design operations including text manipulation, layouts, components, variables, and export functionality.72207 npm-
- FlicenseBqualityDmaintenanceEnables AI agents to read and modify Figma designs programmatically through WebSocket communication, supporting document manipulation, styling, text replacement, and component management.425-
- AlicenseNot gradedqualityCmaintenanceEnables a locally run agent or script to read and write a real Figma layer tree through a local bridge — inspecting node structure and variables, exporting screenshots into the model's context, and performing batched create/update/move/rename/delete operations that collapse into a single undo step. All traffic stays on localhost between the bridge and the Figma plugin, with design-token auditing, binding, and creation included.MIT
- AlicenseAqualityBmaintenanceEnables AI coding agents to read and edit the file currently open in Figma Desktop through a local development plugin, supporting node inspection, JSON/image exports, and arbitrary Plugin API scripts without REST API rate limits.711 npmMIT