MCP server

Figma Unified MCP: Read, Create and Generate Code in Figma

Figma Unified MCP lets an AI coding agent read, create and edit Figma designs, manage variables over the REST API and export CSS, React, SwiftUI, HTML and Tailwind code.

Run
./setup.sh
View on GitHub

Stars, license and last push from GitHub. Install count as reported by the open skills directory.

What is Figma Unified MCP?

Figma Unified MCP is a Node.js MCP server that lets an AI coding agent read, create, edit and generate code from Figma designs. Reads and variable edits use a Figma access token, and canvas writes go through a Figma plugin bridge on port 18211.

Figma Unified MCP is a Model Context Protocol server for working in Figma. An agent can read file structure, nodes, styles, components, variables and comments, then create frames, shapes, text, components and pages.

It also modifies colors, gradients, auto-layout and effects, adds prototype interactions, and exports nodes as PNG, JPG, SVG or PDF. Code generation targets CSS, React, SwiftUI, HTML and Tailwind.

Three data paths

  • REST API reads. File data, styles, components and variables need only a Figma access token and no plugin.
  • REST API writes. Variable and token create, update and delete work without the plugin.
  • WebSocket plus plugin. Canvas writes such as frames, shapes, text, auto-layout and prototyping need the Figma plugin connected.

Tool profiles

The TOOL_PROFILE environment variable controls how many tools register: minimal, standard or full. Non-full profiles include the figma_run escape hatch, which runs an excluded tool by name when you need it.

Where it fits

Best for

  • Reading a Figma file and exporting its design tokens as CSS variables or a Tailwind config.
  • Creating components and screens on the canvas, such as a button or a mobile login screen.
  • Linking Figma components to code with Code Connect: scan a codebase, fuzzy-match components and publish dev resources.

Not for

  • Querying, transforming and creating elements in a Penpot design file by running code through the Plugin API, which the Penpot MCP server covers.
  • Validating every edit inside the design tool and refusing unsafe changes before they run, which the Figma Edit MCP server covers.
  • Turning frames into platform-ready specs for React Native, Flutter and Unity and writing implementation contracts, which the Figma Spec MCP server covers.