Read and modify Figma designs programmatically via LLM
MCP server that enables LLMs to programmatically read and modify Figma designs through a standardized interface for AI-driven design automation.
Why it matters
Enable AI language models to directly interact with Figma files, allowing them to read design properties and make programmatic modifications to designs without manual export or conversion steps.
Outcomes
What it gets done
Query design properties and layer information from Figma files
Modify existing design elements programmatically through LLM commands
Read component structures and design tokens from Figma projects
Update design attributes based on natural language instructions
Install
Add it to your toolbox
Run in your project directory:
curl -fsSL https://spark.entire.vc/get/vb-talk-to-figma | bash Overview
Talk To Figma MCP Server
This MCP server provides a programmatic interface for large language models to interact with Figma design files. It enables AI assistants to read design properties, inspect layers, and make modifications to Figma designs through the Model Context Protocol, translating natural language requests into Figma operations. Use this when you want to automate design workflows through AI assistants, query Figma specifications conversationally, or build tools that let LLMs modify designs based on natural language instructions. It's designed for developers and designers working in MCP-compatible environments like Cursor or Claude Desktop who need programmatic Figma access without leaving their AI-powered workflow.
What it does
The Talk To Figma MCP Server creates a bridge between large language models and Figma, allowing AI assistants to programmatically interact with design files. It exposes Figma's capabilities as MCP tools that LLMs can invoke to read design properties, inspect layers, and make modifications to designs directly through conversational interfaces.
When to use - and when NOT to
Use this connector when you need to automate design workflows through natural language, query design specifications programmatically, or build AI assistants that can inspect and modify Figma files based on user requests. It's ideal for scenarios where developers or designers want to use LLM-powered tools like Cursor or Claude Desktop to interact with Figma without switching contexts.
Do not use this if you need real-time collaborative editing with human designers in the Figma UI, as this is designed for programmatic AI access rather than human-in-the-loop workflows. Avoid this tool if you require direct API access without the MCP abstraction layer, as you would be better served using Figma's REST API directly.
Inputs and outputs
Users provide natural language requests or commands through an MCP-compatible AI client that communicates with the server. The server translates these into Figma API operations. Users receive design data, confirmation of modifications, or structured information about Figma file contents depending on the operation requested. The interaction model follows the Model Context Protocol specification, where the LLM decides which tools to invoke based on user intent.
Who it's for
This connector serves developers and designers who work with AI coding assistants and want to extend their capabilities to include Figma design manipulation. It's particularly valuable for teams building design automation workflows, developers who need to query design tokens or specifications programmatically through conversational interfaces, and anyone looking to reduce context-switching between code editors with AI assistants and the Figma application. The tool assumes familiarity with MCP-compatible clients and basic understanding of how LLMs interact with external tools through structured protocols.
Source README
Talk to Figma MCP
This project implements a Model Context Protocol (MCP) integration between AI agent (Cursor, Claude Code) and Figma, allowing AI agent to communicate with Figma for reading designs and modifying them programmatically.
https://github.com/user-attachments/assets/129a14d2-ed73-470f-9a4c-2240b2a4885c
Project Structure
src/talk_to_figma_mcp/- TypeScript MCP server for Figma integrationsrc/cursor_mcp_plugin/- Figma plugin for communicating with Cursorsrc/socket.ts- WebSocket server that facilitates communication between the MCP server and Figma plugin
How to use
- Install Bun if you haven't already:
curl -fsSL https://bun.sh/install | bash
- Run setup, this will also install MCP in your Cursor's active project
bun setup
- Start the Websocket server
bun socket
- NEW Install Figma plugin from Figma community page or install locally
Quick Video Tutorial
Design Automation Example
Bulk text content replacement
Thanks to @dusskapark for contributing the bulk text replacement feature. Here is the demo video.
Instance Override Propagation
Another contribution from @dusskapark
Propagate component instance overrides from a source instance to multiple target instances with a single command. This feature dramatically reduces repetitive design work when working with component instances that need similar customizations. Check out our demo video.
Manual Setup and Installation
MCP Server: Integration with Cursor
Add the server to your Cursor MCP configuration in ~/.cursor/mcp.json:
{
"mcpServers": {
"TalkToFigma": {
"command": "bunx",
"args": ["cursor-talk-to-figma-mcp@latest"]
}
}
}
WebSocket Server
Start the WebSocket server:
bun socket
Figma Plugin
- In Figma, go to Plugins > Development > New Plugin
- Choose "Link existing plugin"
- Select the
src/cursor_mcp_plugin/manifest.jsonfile - The plugin should now be available in your Figma development plugins
Windows + WSL Guide
- Install bun via powershell
powershell -c "irm bun.sh/install.ps1|iex"
- Uncomment the hostname
0.0.0.0insrc/socket.ts
// uncomment this to allow connections in windows wsl
hostname: "0.0.0.0",
- Start the websocket
bun socket
Usage
- Start the WebSocket server
- Install the MCP server in Cursor
- Open Figma and run the Cursor MCP Plugin
- Connect the plugin to the WebSocket server by joining a channel using
join_channel - Use Cursor to communicate with Figma using the MCP tools
Local Development Setup
To develop, update your mcp config to direct to your local directory.
{
"mcpServers": {
"TalkToFigma": {
"command": "bun",
"args": ["/path-to-repo/src/talk_to_figma_mcp/server.ts"]
}
}
}
MCP Tools
The MCP server provides the following tools for interacting with Figma:
Document & Selection
get_document_info- Get information about the current Figma documentget_selection- Get information about the current selectionread_my_design- Get detailed node information about the current selection without parametersget_node_info- Get detailed information about a specific nodeget_nodes_info- Get detailed information about multiple nodes by providing an array of node IDsset_focus- Set focus on a specific node by selecting it and scrolling viewport to itset_selections- Set selection to multiple nodes and scroll viewport to show them
Annotations
get_annotations- Get all annotations in the current document or specific nodeset_annotation- Create or update an annotation with markdown supportset_multiple_annotations- Batch create/update multiple annotations efficientlyscan_nodes_by_types- Scan for nodes with specific types (useful for finding annotation targets)
Prototyping & Connections
get_reactions- Get all prototype reactions from nodes with visual highlight animationset_default_connector- Set a copied FigJam connector as the default connector style for creating connections (must be set before creating connections)create_connections- Create FigJam connector lines between nodes, based on prototype flows or custom mapping
Creating Elements
create_rectangle- Create a new rectangle with position, size, and optional namecreate_frame- Create a new frame with position, size, and optional namecreate_section- Create a section to group related content on the canvascreate_text- Create a new text node with customizable font properties
Modifying text content
scan_text_nodes- Scan text nodes with intelligent chunking for large designsset_text_content- Set the text content of a single text nodeset_multiple_text_contents- Batch update multiple text nodes efficiently
Auto Layout & Spacing
set_layout_mode- Set the layout mode and wrap behavior of a frame (NONE, HORIZONTAL, VERTICAL)set_padding- Set padding values for an auto-layout frame (top, right, bottom, left)set_axis_align- Set primary and counter axis alignment for auto-layout framesset_layout_sizing- Set horizontal and vertical sizing modes for auto-layout frames (FIXED, HUG, FILL)set_item_spacing- Set distance between children in an auto-layout frame
Styling
set_fill_color- Set the fill color of a node (RGBA)set_stroke_color- Set the stroke color and weight of a nodeset_corner_radius- Set the corner radius of a node with optional per-corner controlset_image_fill- Fill a node with an image from a local file path, URL, or base64 data (FILL, FIT, CROP, or TILE)
Layout & Organization
move_node- Move a node to a new positionresize_node- Resize a node with new dimensionsdelete_node- Delete a nodedelete_multiple_nodes- Delete multiple nodes at once efficientlyclone_node- Create a copy of an existing node with optional position offsetrename_node- Rename a nodeset_parent- Move a node into a new parent (section, frame or group), preserving its absolute position by default
Components & Styles
get_styles- Get information about local stylesget_local_components- Get information about local componentscreate_component_instance- Create an instance of a componentget_instance_overrides- Extract override properties from a selected component instanceset_instance_overrides- Apply extracted overrides to target instances
Export & Advanced
export_node_as_image- Export a node as an image (PNG, JPG, SVG, or PDF) - limited support on image currently returning base64 as text
Connection Management
join_channel- Join a specific channel to communicate with Figma
MCP Prompts
The MCP server includes several helper prompts to guide you through complex design tasks:
design_strategy- Best practices for working with Figma designsread_design_strategy- Best practices for reading Figma designstext_replacement_strategy- Systematic approach for replacing text in Figma designsannotation_conversion_strategy- Strategy for converting manual annotations to Figma's native annotationsswap_overrides_instances- Strategy for transferring overrides between component instances in Figmareaction_to_connector_strategy- Strategy for converting Figma prototype reactions to connector lines using the output of 'get_reactions', and guiding the use 'create_connections' in sequence
Development
Building the Figma Plugin
Navigate to the Figma plugin directory:
cd src/cursor_mcp_pluginEdit code.js and ui.html
Best Practices
When working with the Figma MCP:
- Always join a channel before sending commands
- Get document overview using
get_document_infofirst - Check current selection with
get_selectionbefore modifications - Use appropriate creation tools based on needs:
create_framefor containerscreate_rectanglefor basic shapescreate_textfor text elements
- Verify changes using
get_node_info - Use component instances when possible for consistency
- Handle errors appropriately as all commands can throw exceptions
- For large designs:
- Use chunking parameters in
scan_text_nodes - Monitor progress through WebSocket updates
- Implement appropriate error handling
- Use chunking parameters in
- For text operations:
- Use batch operations when possible
- Consider structural relationships
- Verify changes with targeted exports
- For converting legacy annotations:
- Scan text nodes to identify numbered markers and descriptions
- Use
scan_nodes_by_typesto find UI elements that annotations refer to - Match markers with their target elements using path, name, or proximity
- Categorize annotations appropriately with
get_annotations - Create native annotations with
set_multiple_annotationsin batches - Verify all annotations are properly linked to their targets
- Delete legacy annotation nodes after successful conversion
- Visualize prototype noodles as FigJam connectors:
- Use
get_reactionsto extract prototype flows, - set a default connector with
set_default_connector, - and generate connector lines with
create_connectionsfor clear visual flow mapping.
FAQ
Common questions
Discussion
Questions & comments · 0
Sign In Sign in to leave a comment.