Talk to Figma MCP

MCP bridge between an agent (Cursor, Claude Code, Codex) and Figma for reading designs and editing them on the canvas

  • 7,105 ★ on the repository
  • Last commit
  • MIT
MCP server

Extended access

Why this level

  • Modifies Figma file content on the agent's commands
  • Runs a local WebSocket server and exchanges data over the network
All reasons and checks

grab/cursor-talk-to-figma-mcp

Install

Manual install

{
  "mcpServers": {
    "TalkToFigma": {
      "command": "bunx",
      "args": ["cursor-talk-to-figma-mcp@latest"]
    }
  }
}

Fragment for ~/.cursor/mcp.json. bun setup registers the server in the active project automatically.

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • Modifies Figma file content on the agent's commands
  • Runs a local WebSocket server and exchanges data over the network

This is third-party code. Review the repository files before installing.

What it does

The project links an agent to Figma through an MCP server, a Figma plugin and a local WebSocket. The agent reads the document, the selection and individual nodes, creates rectangles, frames, sections and text, and sets auto layout, padding, alignment, fills, strokes and corner radius. It supports bulk text replacement, propagation of component instance overrides, annotations and FigJam connectors built from prototype flows. The server and the plugin talk over a channel that the agent joins with join_channel.

Who it is for. For designers and developers who automate routine Figma work through an agent.

Good fit when

  • You need bulk text replacement or to propagate overrides across many instances
  • You need to build or adjust layout and styles from the agent
  • You need to place annotations or connectors along a prototype flow

Not a fit when

  • The Figma plugin is not installed or the WebSocket server is not running
  • You need precise manual work on the file rather than batch operations

Example request

Join the Figma channel and replace the text in every button from English to Russian

MCP

Transport
stdio
Authentication
not required

Limitations

It needs Bun, a running local WebSocket server and the installed Figma plugin, and the agent must join a shared channel. On Windows with WSL you must open hostname 0.0.0.0 in src/socket.ts. Figma access from Russia is restricted, so use without a VPN is not guaranteed.

How to disable. Remove the TalkToFigma entry from the agent's MCP configuration, stop the WebSocket server and remove the plugin in Figma under Plugins, Development.

FAQ

Why is a separate WebSocket server needed?

The MCP server and the Figma plugin exchange messages through it. Without a running server and a joined channel, commands never reach Figma.

Which agents does it work with?

Cursor, Claude Code and Codex through the standard MCP configuration. The plugin installs in Figma in development mode or from the community page.

Discussion

No questions or reviews yet.

An MCP server that lets an agent read and edit Figma designs: colors, typography, components and export

MCP serverExtended access678Repository stars

A community MCP server with a Figma plugin: the agent creates frames, text and components in the open file, not just reads them

MCP serverBroad access177Repository stars

An MCP server and a Figma plugin that let an agent read and draw on the canvas safely: with layout checks and no broken screens.

MCP serverExtended access107Repository stars
Editors’ pick

An MCP server that gives the agent simplified Figma layout data from a link so it can build the screen more accurately than from a screenshot

MCP serverExtended access16.2KRepository stars

figma-ui-mcp is an MCP bridge that draws interfaces on the Figma canvas through code and reads designs back, no API key.

MCP serverExtended access266Repository stars
Official

A free, two-way Figma MCP server: turns designs into framework-aware code and pushes code back to the canvas

MCP serverExtended access1.4KRepository stars

README in short

The README describes three parts: a TypeScript MCP server, a Figma plugin and a WebSocket server that connects them. Setup runs through Bun: bun setup registers the MCP in a Cursor project and bun socket starts the channel. The plugin installs from the Figma community page or locally via manifest.json. The tools are then listed by group: document and selection, annotations, prototyping and connectors, element creation, text editing, auto layout and styling. MIT license.

README badge

Report a problem