Figma MCP Server

Integrates Figma's API with Claude and other Model Context Protocol (MCP) compatible clients, providing read-only access to Figma files and projects.

Local serverstdioTypeScript 150

What is the Figma MCP server?

Figma MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Integrates Figma's API with Claude and other Model Context Protocol (MCP) compatible clients, providing read-only access to Figma files and projects.

What you get

A Model Context Protocol (MCP) server that provides integration with Figma's API through Claude and other MCP-compatible clients. Currently supports read-only access to Figma files and projects, with server-side architecture capable of supporting more advanced design token and theme management features (pending Figma API enhancements or plugin development).

  • 🔑 Secure authentication with Figma API
  • 📁 File operations (read, list)
  • 🎨 Design system management
  • Variable creation and management
  • Theme creation and configuration
  • Reference handling and validation

Setting it up

figma-mcp-server on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Configuration and credentials

You will need one environment variable: FIGMA_ACCESS_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

  • Node.js 18.x or higher - Figma access token with appropriate permissions - Basic understanding of MCP (Model Context Protocol)

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. It is maintained by TimHolden; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the figma mcp server does with a few real requests.

How to install the Figma MCP server

{
  "mcpServers": {
    "figma-2": {
      "command": "npx",
      "args": ["-y", "figma-mcp-server"],
      "env": {
        "FIGMA_ACCESS_TOKEN": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

  • Node.js 18.x or higher - Figma access token with appropriate permissions - Basic understanding of MCP (Model Context Protocol)
VariableDescriptionRequired
FIGMA_ACCESS_TOKENCredential the server authenticates with.Yes

Frequently asked questions

The Figma MCP Server is a tool that integrates Figma's API with Claude and other Model Context Protocol (MCP) compatible clients. It provides read-only access to Figma files and projects, enabling you to leverage Figma data within AI workflows.