PlugWiki
Figma MCP Bridge logo

Figma MCP Bridge: Setup for Claude, Cursor and Other Apps

CommunityLocal
Getnpm@gethopp/figma-mcp-bridgegethopp/figma-mcp-bridge

Not the official Figma MCP server. This one is built by the community. Figma makes its own: Figma MCP Server →

Lets Claude, Cursor and other assistants read and edit the Figma or FigJam file you have open, without using Figma's API.

Figma MCP Bridge is a community project that lets your assistant read and edit the Figma or FigJam file you have open. It works through a plugin you import into the Figma desktop app, so it does not use Figma's API or its request limits. The assistant can read layers, styles and variables, and it can also change and delete things in your file. Use it on a copy if the file matters.

Good for

  • Designers who want an assistant to edit layers, text and layout in the open file
  • Developers turning Figma frames into code on a free Figma plan
  • FigJam users who want stickies, shapes and connectors made for them

Works in

12 should work

Tap an app to see how to set it up and any known problems.

Install Figma MCP Bridge

Claude Code

  1. 1

    Copy this prompt.

    Add the Figma MCP Bridge server to Claude Code. Run this command:
    
    claude mcp add figma-bridge -- npx -y @gethopp/figma-mcp-bridge
    
    Then check that it loaded and tell me if I need to sign in or restart.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

Requires Node.js, Figma desktop app + bridge plugin.

Read-only mode: There is no read-only setting. Run the plugin in Figma Dev Mode and edits fail with an error.

Import the bridge plugin in the Figma desktop app (Plugins, Development, Import plugin from manifest, using the manifest.json from the latest release), then run it in the file you want to work on. The browser version of Figma cannot import development plugins. The server starts on demand over stdio, and no account or key is needed.

Built from the package data we hold. Not yet tested by us.

Tools

  • Lists the Figma files that are connected

    Shows each open Figma or FigJam file that has the plugin running, with its file key. Use the key to aim other tools at one file.

    Try: “Which Figma files are connected right now?”

    Read · list_files

  • Reads what you have selected in Figma

    Returns the nodes you currently have selected in the open file.

    Try: “Describe the layers I have selected.”

    Read · get_selection

  • Reads the layer tree of the current page

    Returns the document tree for the page open in Figma or FigJam.

    Try: “Give me an outline of the current page.”

    Read · get_document

  • Reads one layer by its ID

    Fetches a single node by ID, including nodes inside component instances. It can also include the prototype links on that node and its children.

    Try: “Read node 4029:12345 and tell me its padding and colors.”

    Read · get_node

  • Summarizes the design around your selection

    Returns a trimmed tree for the selection or page that is meant to help the assistant understand the design before it builds code.

    Try: “Build a React component from my selected frame.”

    Read · get_design_context

  • Reads exact positions and sizes of layers

    Returns absolute transforms and layout bounds for a chosen root layer. The docs warn that separate screenshot calls are not taken at the same moment.

    Try: “Get exact positions for every layer in the hero frame.”

    Read · get_layout_tree

  • Lists the file's saved styles

    Returns every local paint, text, effect and grid style in the document.

    Try: “List the text styles in this file.”

    Read · get_styles

  • Lists design variables and tokens

    Returns variable collections, their modes and values, which hold colors, numbers, strings and booleans used as design tokens.

    Try: “Export our color variables as CSS custom properties.”

    Read · get_variable_defs

  • Reads the file name, pages and current page

    Returns basic facts about the open document: its name, its pages and which page is showing.

    Try: “What pages does this file have?”

    Read · get_metadata

  • Takes an image of selected or named layers

    Exports the selection or listed node IDs as an image and returns it to the assistant as base64 data.

    Try: “Show me a screenshot of the checkout frame.”

    Read · get_screenshot

  • Saves layer images to a folder on your computer

    Exports several nodes and writes each image to a file inside the server's working directory. It refuses to overwrite an existing file and returns file details only.

    Try: “Save PNGs of all frames in this section to ./exports.”

    Write · save_screenshots

  • Lists prototype links on a layer and its children

    Read-only. Returns Figma's own trigger and action data for each interaction, with destinations named. It does not work in FigJam.

    Try: “What happens when someone taps the Sign up button?”

    Read · get_prototype_connections

Read from the source code

Permissions

high risk · 5 things to watch

High risk

The assistant can change and delete layers in the Figma file where the plugin is running. Use a duplicate of important files, or run the plugin in Dev Mode when you only want it to read.

What it can do

  • Read your data
  • Create and change things
  • Delete things
  • Read-only mode

Watch out for

  • It can delete layers and remove frames

    delete_nodes removes layers once confirm is true, and ungroup_node removes the wrapper frame. Keep the Figma file's version history handy and use a copy for big jobs. github.com

  • It edits your file directly

    More than 30 tools change layers, text, fills and layout in the file where the plugin runs. Open the plugin in Dev Mode if you only want the assistant to read. github.com

  • Opt-in tool runs any code in Figma

    run_script appears only if FIGMA_BRIDGE_ENABLE_RUN_SCRIPT is 1. It runs arbitrary JavaScript against your open file, and the README says its remove guard is not a security boundary. github.com

  • Local port has no sign-in

    The server listens on 127.0.0.1 port 1994 by default and has no authentication. Setting FIGMA_BRIDGE_HOST to 0.0.0.0 opens it to your network, so leave it at the default. github.com

  • It writes and reads files in its working folder

    save_screenshots writes image files, and the image, SVG and HTML import tools read files. Paths for exports and imports must stay inside the folder the server starts in. github.com

Security advisories

No published security advisories as of Nov 1, 2026.

Technical details
Turning on read-onlyNo read-only switch is documented. Dev Mode is read-only, and the edit tools return an error there.
Talks toWeb addresses you give to the image tool
Sign-in and keysNo account or API key. The server talks to the Figma plugin on your computer, and Figma's own permissions decide which files you can edit.

Questions

Is Figma MCP Bridge official?

No. It is a community project by the gethopp organization and is not made by Figma. Figma publishes its own server, covered at /mcp/figma.

Do I need a Figma API key or paid plan?

No key is needed. The project says it avoids Figma's API limits by streaming data from a plugin running in the Figma desktop app, which does not work in the browser version.

Can it run read-only?

Not with a setting. Running the plugin in Dev Mode makes edits fail with an error, so only the read tools work.

Can it delete things in my file?

Yes. It can delete layers when the assistant sets the confirm flag, and ungrouping can remove a frame. Page and document nodes cannot be deleted by that tool.

What does the run_script tool do?

It runs JavaScript inside your open file. It is off unless you set FIGMA_BRIDGE_ENABLE_RUN_SCRIPT to 1 in the server's environment, which is why the list shows 55 tools but 54 appear by default.

Can I use it with several Figma files at once?

Yes. Open the plugin in each file and tell the assistant which file to use. The first tool lists the connected files.

How is it different from Figma's own MCP server?

This bridge needs no Figma sign-in or API key, because a plugin in the Figma desktop app streams the open file to it, while Figma's official server (see /mcp/figma) is hosted at https://mcp.figma.com/mcp and uses your Figma account, with call limits that depend on your plan. The bridge README says it exists to avoid the 6-requests-a-month free limit that it saw in another server. The trade-offs: the bridge works only on a file you have open in the desktop app, it runs only on your computer, and its edit tools include delete_nodes, run_script (opt-in) and many layer edits. Its README says it has no component, instance or variable authoring yet.

How do I add it to Cursor or Claude?

Use the install box above, then import the Figma plugin from the project's releases page. The plugin step is needed on every app.

Information

updated Nov 2, 2026

Publisher
Community
Package
@gethopp/figma-mcp-bridge
Registry
npm
Transport
stdio
Auth
None
Version
0.0.25
License
MIT
Last commit
Oct 21, 2026
Open issues
4

GitHubnpmChangelogIssues

Other Figma MCP servers

Sources

Docs, issue trackers and discussions this page is built from. Issues, quotes and findings above link to their own source.

Show all 3
  1. github.com · github.com
  2. github.com · github.com
  3. github.com · github.com

Facts from the official MCP registry, GitHub, npm, PyPI and the Docker catalog. Updated Nov 2, 2026.