figma-mcp-go

Figma MCP — Local Plugin Integration

Open-source Figma MCP server with full read/write access via plugin. Turn text into designs and designs into real code. Works with Cursor, Claude, GitHub Copilot, and any MCP-compatible AI tool.

Highlights

• Operates locally via the Figma Plugin API (no REST API token required)
• Real-time execution directly on your local machine
• Read and Write live Figma data via plugin bridge — 63 tools total
• Full design automation — styles, variables, components, prototypes, content, and transactional batch pipelines
• Design strategies included — read_design_strategy, design_strategy, and more prompts built in

Styles, Variables, Components, Prototypes, and Content

https://github.com/user-attachments/assets/eae41471-fc72-4574-8261-4f42c38b8c99

Text to Design, Design to Code

https://github.com/user-attachments/assets/17bda971-0e83-4f18-8758-8ac2b8dcba62

Why this exists

Most Figma MCP servers rely on the cloud-based Figma REST API.

While the REST API is excellent for server-to-server integrations, experimenting with AI tools often involves making hundreds of rapid tool calls per session. A cloud-based approach can introduce network latency and overhead.

This project takes a different approach by running as a local Figma Plugin. By bridging directly to the Figma Plugin API on your desktop, it provides instant, real-time read/write access to your active documents without relying on external cloud APIs or requiring an API token.

Installation & Setup

Install via npx — no build step required. Watch the setup video or follow the steps below.

1. Configure your AI tool

Claude Code CLI

claude mcp add -s project figma-mcp-go -- npx -y @tunglt1810/figma-mcp-go@latest

Codex CLI

codex mcp add figma-mcp-go -- npx -y @tunglt1810/figma-mcp-go@latest

.mcp.json (Claude and other MCP-compatible tools)

{
  "mcpServers": {
    "figma-mcp-go": {
      "command": "npx",
      "args": ["-y", "@tunglt1810/figma-mcp-go"]
    }
  }
}

.vscode/mcp.json (Cursor / VS Code / GitHub Copilot)

{
  "servers": {
    "figma-mcp-go": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@tunglt1810/figma-mcp-go"
      ]
    }
  }
}

2. Install the Figma plugin

1. In Figma Desktop: Plugins → Development → Import plugin from manifest
2. Select manifest.json from the plugin.zip
3. Run the plugin inside any Figma file

3. Running more than one AI tool at once (optional)

Every MCP client starts its own copy of the server, but only one process can hold the plugin connection on a given port. There are two ways to share, and they do different things.

Same Figma file, no configuration. Leave the default config everywhere. The first process to bind port 1994 owns the WebSocket to the plugin; the others detect the port is taken and proxy their tool calls to it over HTTP. Every client drives the one file the plugin is open in. If the process holding the port exits, another takes over within a few seconds.

Different Figma files, one port each. Give each client its own port and point a separate plugin instance at it:

{
  "mcpServers": {
    "figma-mcp-go": {
      "command": "npx",
      "args": ["-y", "@tunglt1810/figma-mcp-go", "--port", "1995"]
    }
  }
}

Then open the plugin in the second Figma file and set the port to match under the settings gear. Each client now talks to its own file, with no proxying.

Note that the plugin stores host and port in figma.clientStorage, which is shared across files — changing the port makes it the default the next time you open the plugin anywhere, so expect to set it on whichever instance should use 1994.

--ip moves the listener off 127.0.0.1 (use 0.0.0.0 to accept connections from another machine).

Upgrading

Re-download the plugin when you update the server. The server updates itself through npx, but the Figma plugin is installed by hand, so the two can drift apart. A plugin older than the server will reject commands it does not know with Unknown request type.

Breaking changes in 0.1.0

Eight single-purpose tools were replaced by one. Each took nodeIds plus a single property, and they are now combinations of set_node_properties:

Properties can be combined, so what used to take several calls and several undo entries now takes one of each.

Eighteen more tools were merged into four, each selecting between the old tools with one argument. An argument belonging to a different variant is rejected with a message naming it, rather than being ignored:

Two things changed behaviour rather than just name. create_node({type:"ELLIPSE"}) honours startAngle, endAngle and innerRadiusRatio, which create_ellipse declared but ignored — arcs and rings came out as plain ellipses. And name now works on stars, polygons and lines, which read it but never declared it.

create_effect_style's type argument is effectType under create_style, because type names the kind of style. Gradients can only target a fill; set_paint says so rather than accepting target: "stroke" and doing nothing.

Available Tools

Write — Batch & Transactions

Write — Create

Write — Modify

Write — Delete

Write — Prototype

Write — Styles

Write — Variables

Write — Pages

Write — Components & Navigation

Read — Document & Selection

Read — Styles & Variables

Export

MCP Prompts

Contributing

Issues and PRs are welcome.

Star History