TalkToFigma MCP Server

Content

TalkToFigma MCP Server connects an MCP client to Figma through a TypeScript MCP server, a local WebSocket bridge, and a Figma plugin. It lets agents read Figma documents and selected nodes, then perform design operations such as creating frames and text, changing layout settings, editing styles, replacing copy, managing annotations, exporting nodes, and working with component instances.

This is a write-capable design automation bridge. It is distinct from read-only Figma context extraction because it can modify the active Figma file through the plugin once the WebSocket channel is connected.

Source Review

• https://github.com/grab/cursor-talk-to-figma-mcp
• https://github.com/grab/cursor-talk-to-figma-mcp/blob/main/README.md
• https://github.com/grab/cursor-talk-to-figma-mcp/blob/main/package.json
• https://registry.npmjs.org/cursor-talk-to-figma-mcp

These sources were reviewed on 2026-06-06. Prefer the live repository, README, package metadata, and npm registry metadata for current commands, server package names, WebSocket setup, plugin setup, and supported Figma tools.

Features

• Read Figma document and selection metadata.
• Inspect individual or multiple node records.
• Create rectangles, frames, text nodes, component instances, and connectors.
• Move, resize, clone, delete, and focus nodes.
• Update fills, strokes, corner radius, auto-layout mode, padding, axis alignment, layout sizing, and item spacing.
• Scan and batch-replace text content.
• Read and write annotations.
• Extract and apply component instance overrides.
• Export nodes as images.
• Route communication through WebSocket channels between the MCP server and the Figma plugin.

Installation

Install Bun first, then configure the MCP server in your client:

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

Start the WebSocket bridge from a checkout of the repository:

bun socket

Open Figma, run the TalkToFigma plugin, join a channel with join_channel, and verify the active file before allowing write tools.

Use Cases

• Let Claude inspect selected Figma nodes while implementing UI.
• Create rough frames, text, rectangles, and component instances from prompts.
• Batch update design copy across many text nodes.
• Convert manual annotations into native Figma annotations.
• Propagate component instance overrides to repeated UI patterns.
• Generate connector lines from prototype reactions for FigJam-style flow maps.

Safety and Privacy

Start with read tools such as get_document_info, get_selection, and read_my_design. Move to write tools only after confirming the active Figma document, selected node, and WebSocket channel.

Use duplicate files for experiments. Batch operations such as text replacement, annotation conversion, component override propagation, and node deletion can change large parts of a design quickly.

Treat design data as sensitive model context. Node names, text layers, component metadata, exported images, and prototype flows can reveal product strategy, unreleased UI, customer information, brand assets, and implementation details.

Duplicate Check

No grab/cursor-talk-to-figma-mcp entry, TalkToFigma entry, or matching TalkToFigma source URL was found in content/mcp. Existing Figma-related entries cover different projects and do not document this write-capable TalkToFigma bridge.

• Source repositorygithub.com 2026-07-21T07:17:01+00:00
• Documentationgithub.com
• Submitted by oktofeesh12026-06-06