# Figma [Health: Active]

**Category:** 📐 Architecture & Design  
**Repository:** https://github.com/planetabhi/figma-mcp-server  
**GitHub Stars:** 10  
**npm Downloads (last month):** 11842  
**Views:** 8  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/figma-2

## Description
A local MCP server with full Figma REST API coverage.

## Tools
Capabilities this server exposes over MCP:

- **list_file_variables**
- **get_published_variables**
- **modify_variables**

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `bunx` (confidence: high):

```json
"mcpServers": {
  "figma": {
    "command": "bunx",
    "args": ["figma-mcp-server"],
    "env": {
      "FIGMA_API_KEY": ""
    }
  }
}
```

**Requires environment variables:** `FIGMA_API_KEY` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## 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.

_Full upstream README: https://allmcps.com/mcp/figma-2/readme_