Log inSubmit server
Figma logo

Figma

Figma REST API access over a local stdio MCP server, with tools for files, variables, comments, webhooks, and more.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Figma

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "figma-2": {
      "command": "bunx",
      "args": [
        "figma-mcp-server"
      ],
      "env": {
        "FIGMA_API_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

The Figma MCP server exposes Figma REST API endpoints as self-describing MCP tools that AI clients can discover at startup. It runs locally over stdio with Bun and authenticates through a Figma personal access token in FIGMA_API_KEY. Reach for it when an MCP client needs to inspect or modify Figma data, including file variables, published variables, and design-system resources. Some variable, analytics, and organization tools require Figma Enterprise or other higher-tier plans.

Use cases

  • Read file and node data from Figma
  • Inspect and modify Figma variables
  • Retrieve published design resources
  • Query comments, components, and styles
  • Access Figma webhooks and library data

Key features

  • Local stdio MCP server
  • Bun-native startup with bunx
  • Self-describing REST endpoint tools
  • Required-parameter validation
  • Figma personal access token authentication
  • Broad non-deprecated REST API coverage

Tools3

What Figma lets your agent do. Expand a tool for its parameters.

Self-reported~15 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

4/4 checks healthy over the last 39d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 12d ago via OSV.dev · figma-mcp-server (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars10Stargazers on the source repository.
npm downloads11kPackage downloads in the last 30 days.
Last commit5d agoMost recent push to the default branch.
Tools exposed3Callable tools this server registers over MCP.
Directory activity8 viewsConfig copies, upvotes, and views on AllMCPs.

How Figma works

What Figma MCP server does

The Figma MCP server connects MCP-compatible AI clients to the Figma REST API through a local process. Its documented coverage includes files and nodes, image rendering, image fills, metadata, version history, variables, components, styles, comments, reactions, folders, users, developer resources, webhooks, library analytics, organization logs, embeds, and payments.

The currently highlighted tools are list_file_variables, get_published_variables, and modify_variables. These focus on reading file-level variables, retrieving published variables, and changing variables. The repository describes broader coverage of non-deprecated Figma REST endpoints, with the full current tool and parameter list available in the connected MCP client.

This server belongs in the Architecture & Design category when an agent needs to work with Figma data as part of design-system maintenance, file inspection, collaboration workflows, or related development tasks.

How it works

At startup, endpoint definitions in the server's tools/figma/ directory are discovered and exposed as MCP tools. Each endpoint becomes a self-describing tool, and required parameters are checked before a request is made. Adding another endpoint follows the repository's file-based tool structure.

Communication uses stdio rather than a hosted service. An MCP client starts the process with bunx figma-mcp-server, then passes the Figma token through the process environment. Because the package is Bun-native, the documented launcher is bunx; Node and npx are not supported.

Setup and configuration

Install Bun version 1.2 or newer before configuring the Figma MCP server. Create a personal access token in Figma under Settings, Security, and Personal access tokens. Store that value as FIGMA_API_KEY, preferably in the MCP client's environment configuration rather than directly in application prompts.

A typical configuration uses bunx as the command and figma-mcp-server as its argument. Claude Desktop uses its developer configuration file, Cursor uses a global or project MCP file, and Gemini CLI uses its settings file. VS Code uses .vscode/mcp.json or a user-level mcp.json; its input mechanism can prompt for the token and keep it in operating-system secret storage. Restart the client after changing configuration.

Tools and capabilities

The Figma MCP server can expose up to 50 documented tools across the REST API areas listed above. Its capabilities include reading and updating design variables, accessing published resources, inspecting files and node trees, working with components and styles, handling comments and reactions, querying webhooks, and accessing library or organization data where the Figma account permits it.

Plan level matters for some operations. The three variable tools require an Enterprise organization. Library analytics requires an Organization or Enterprise plan. Activity logs, developer logs, and AI usage require an Enterprise organization plus an administrator or plan access token. Most other tools work with a personal access token on any plan, according to the repository documentation.

Limitations and notes

The server requires Bun 1.2 or later and does not support Node-based npx startup. Authentication depends on a valid Figma personal access token, and the token's permissions and account plan determine which endpoints succeed. The repository describes the endpoint set as non-deprecated, while the connected client's tool list remains the authoritative place to inspect available names and parameters.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Figma

Figma is an MCP server that connects AI clients to the Figma REST API. Its main tools include listing file variables, retrieving published variables, and modifying variables, with broader endpoint coverage documented by the package. It runs locally over stdio and authenticates with a Figma personal access token supplied through FIGMA_API_KEY.

Install Bun 1.2 or newer, then configure your MCP client to run bunx with figma-mcp-server as its argument. Set FIGMA_API_KEY to a Figma personal access token in the client environment and restart the client after saving the configuration.

Yes, Figma works with Cursor through its MCP configuration. Add the server to ~/.cursor/mcp.json or a project-level .cursor/mcp.json, use bunx with figma-mcp-server, provide FIGMA_API_KEY, and restart Cursor.

The variable tools require an Enterprise organization. This applies to list_file_variables, get_published_variables, and modify_variables; the token must also provide access to the relevant Figma organization.

No, use bunx instead of npx. The package is Bun-native, requires Bun 1.2 or newer, and does not support Node-based startup.

Related MCP servers

All in Architecture & Design All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewFigma AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/figma-2?style=directory)](https://allmcps.com/mcp/figma-2)
HTML Embed
<a href="https://allmcps.com/mcp/figma-2"><img src="https://allmcps.com/api/badge/figma-2?style=directory" alt="Figma on AllMCPs" /></a>