PlugWiki
Talk to Figma MCP logo

Talk to Figma MCP Server: Setup for Claude, Cursor and Other Apps

CommunityLocal
Getnpmcursor-talk-to-figma-mcpgrab/cursor-talk-to-figma-mcp

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

Lets Claude and Cursor read and edit your Figma designs, from text and colours to layout and components.

Talk to Figma connects an AI app to the Figma file you have open, so the assistant can read a design and change it. It can create frames and text, restyle layers, adjust auto layout, edit annotations and delete layers. Setup has three parts: the MCP server, a small relay that runs on your computer with Bun, and a Figma plugin. The assistant then joins a channel to link them.

Good for

  • Designers who want an assistant to make bulk text or style changes in Figma
  • Developers who want Cursor or Claude Code to read a design before writing code
  • Product teams turning prototype flows into connector lines and annotations
  • Anyone who already uses Bun and the Figma desktop app

Works in

12 should work

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

Install Talk to Figma MCP

Claude Code

  1. 1

    Copy this prompt.

    Add the Talk to Figma MCP server to Claude Code. Run this command:
    
    claude mcp add cursor-talk-to-figma -- npx -y cursor-talk-to-figma-mcp
    
    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.

Also needed: Bun, the Figma plugin from the Figma Community page, and the relay started with the repository's socket script. Then ask the assistant to join a channel.

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

Tools

  • Reads full details of what you have selected in Figma

    Returns detailed information about every node in your current selection, with no parameters.

    Try: “Read the design I have selected and describe its layout.”

    Read · read_my_design

  • Shows basic facts about the open Figma file

    Returns information about the current Figma document.

    Try: “What is in my open Figma file?”

    Read · get_document_info

  • Shows what is selected in Figma

    Returns information about the current selection.

    Try: “What do I have selected in Figma right now?”

    Read · get_selection

  • Reads details of one layer

    Returns detailed information about a single node, by its ID.

    Try: “Give me the details of node 12:34.”

    Read · get_node_info

  • Reads details of several layers at once

    Returns detailed information about many nodes, given a list of IDs.

    Try: “Get the details for nodes 12:34, 12:35 and 12:40.”

    Read · get_nodes_info

  • Finds every piece of text inside a selected layer

    Scans a selected node for text nodes, in chunks so large designs do not time out.

    Try: “List all the text in the selected frame.”

    Read · scan_text_nodes

  • Finds child layers of given types

    Scans a selected node for child nodes of the types you name, which helps when matching annotations to elements.

    Try: “Find all buttons and inputs inside the selected frame.”

    Read · scan_nodes_by_types

  • Lists the file's styles

    Returns all styles in the current Figma document.

    Try: “Which color and text styles does this file define?”

    Read · get_styles

  • Lists the file's local components

    Returns all local components in the document.

    Try: “List the components defined in this file.”

    Read · get_local_components

  • Lists annotations in the file or on a layer

    Returns all annotations in the document, or only those on one node.

    Try: “What annotations are on this screen?”

    Read · get_annotations

  • Reads prototype links between screens

    Returns the prototype reactions from nodes. The tool's own text says its output must be passed through the 'reaction to connector' prompt straight away to build connector lines.

    Try: “Read the prototype flow from the selected screens.”

    Read · get_reactions

  • Copies the custom settings from a component instance

    Extracts the override properties from a selected component instance, so they can be applied to other instances.

    Try: “Copy the overrides from the selected button instance.”

    Read · get_instance_overrides

Read from the source code

Permissions

high risk · 5 things to watch

High risk

The assistant can read everything in the open Figma file and also change it and delete layers. Work on a copy of the file, and use Figma's version history to roll back a bad edit.

What it can do

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

Watch out for

  • It can delete layers

    Two tools delete one or many layers in the open file. Work on a duplicate, and check Figma version history if something goes missing. github.com

  • The relay has no sign-in and sets no host

    The relay on port 3055 only asks clients to join a named channel, allows any origin, and its source sets no host (the only hostname line is commented out). Bun listens on all interfaces when no host is set, so another device on your network may be able to join your channel and send edit and delete commands. Run it on a trusted network or behind a firewall. github.com

  • It edits the open file directly

    Most tools create, move, restyle or retext layers as soon as they are called. Review large batch changes before you accept them. github.com

  • Four tools are not published yet

    Filling a layer from a local file or URL, renaming, creating sections and moving layers into a parent exist on the main branch only. The image tool can read a file path or fetch a URL from your machine. github.com

  • The plugin source sends anonymous usage events to Google Analytics

    The plugin source on the main branch sends plugin opens, command names and success or error to Google Analytics, and says no file content or personal data is collected. Check the plugin version you install. github.com

Security advisories

No published security advisories as of Nov 1, 2026.

Technical details
Turning on read-onlyNo read-only mode is documented. Most tools edit the open Figma file, and two delete layers.
Talks toLocal relay on port 3055. The Figma plugin. Google Analytics (anonymous plugin usage events, per the plugin source)
Sign-in and keysNo account or API key. The assistant reaches Figma through a plugin you run yourself and a relay on your computer. The relay does not check who connects.
Scopes
  • The open Figma file, through the plugin

Questions

What do I need besides the MCP server?

You need Bun to run the relay, which you start from a clone of the repository, and the Figma plugin from the Figma Community page. Then the assistant joins a channel so the plugin and server can talk. The install box covers the server config only.

Is the Talk to Figma MCP server official?

No. It is a community project from Grab's open-source repository, not made by Figma.

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

Talk to Figma reads and edits the file you have open through a plugin. Figma's own server is a separate product with its own setup, so see the Figma MCP servers page to compare them.

Does it work with Claude Code?

Yes. The README says it is for Cursor and Claude Code, and the install box gives the Claude Code command. You still need the relay and the plugin.

Where does the npm package come from?

The README itself tells you to run bunx cursor-talk-to-figma-mcp@latest, and the repository's setup script writes that config, so the package is the one the project points to. But the package is published by an individual npm account (webrangeriit), its package.json has no repository field, and nothing on npm links it back to the Grab repository. The install box shows npx instead of the README's bunx; the package's entry file starts with a Node shebang, so both run it. The relay still needs Bun.

Can it delete things in my file?

Yes. It can delete one or many layers. Work on a copy and use version history if you need to undo.

Does it use Figma's API or a token?

No token is mentioned in the README. It works through a plugin that runs inside the Figma app.

Does it send any data to a third party?

The Figma plugin source on the main branch sends anonymous usage events (plugin opens, command names, success or error) to Google Analytics and says no file content or personal data is collected. The MCP server itself needs no account. The relay listens on port 3055 and is not signed in, so keep it on a trusted network.

Information

updated Nov 2, 2026

Publisher
Community
Package
cursor-talk-to-figma-mcp
Registry
npm
Transport
stdio
Auth
None
License
MIT
Last commit
Jul 26, 2026
Open issues
68

WebsiteGitHubIssues

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 5
  1. github.com · github.com
  2. github.com · github.com
  3. github.com · github.com
  4. github.com · github.com
  5. registry.npmjs.org · registry.npmjs.org

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