home / mcp / figma mcp server

Figma MCP Server

Provides MCP tools to list Figma teams/projects, list project files, fetch file data, and generate frontend assets from Figma frames.

Installation
Add the following to your MCP client configuration file.

Configuration

View docs
{
  "mcpServers": {
    "anishtejwanigemi-max-mcp": {
      "command": "node",
      "args": [
        "server.js"
      ],
      "env": {
        "FIGMA_TOKEN": "YOUR_TOKEN"
      }
    }
  }
}

This minimal MCP server exposes a set of Figma-related tools over stdio so you can build and test LLM-assisted workflows. It can list teams’ projects, enumerate project files, fetch full file JSON or specific nodes, and generate a simple React+Vite frontend from a Figma frame. Run it locally and connect with any MCP-capable client to perform these actions without exposing HTTP endpoints.

How to use

You run the server locally and connect to it with an MCP-capable client over stdio. The client discovers four tools, then you invoke them by name with the required inputs. The server validates inputs, executes the requested action against the Figma API when a token is provided, and returns both a human-friendly content view and a structured payload for the client UI.

How to install

Prerequisites you need installed on your machine before you begin.

# 1) Ensure you have Node.js 18+ installed
node -v
# should be >= 18

# 2) Install project dependencies
npm install

# 3) Optionally provide your Figma token for discovery or calls that access Figma
# Create a .env file with the token if you will access Figma
# FIGMA_TOKEN=your_figma_personal_access_token

Next, start the server. It runs via Node.js and does not expose an HTTP port; it communicates over stdio for MCP clients.

# Windows CMD
set FIGMA_TOKEN=your_token
node server.js

# PowerShell
$env:FIGMA_TOKEN = "your_token"
node server.js

Troubleshooting and tips

If the client reports no tools or startup errors, verify that the server is running and that the MCP tools are registered before connecting.

Common checks:

- Ensure the environment variable FIGMA_TOKEN is set if you plan to call the Figma API.

- Confirm you are using Node.js 18+ to guarantee fetch support.

- Run node server.js by itself to observe any startup errors before connecting your MCP client.

Generated frontend workflow (optional)

If you generate a frontend from a Figma frame, you will receive a set of files (for example, App.jsx, index.html, package.json, etc.). To run the generated React app locally after saving the files into a new directory, install dependencies and start the dev server.

Tool reference

The server provides four tools over stdio. Use them via your MCP client by name and provide the required inputs.

Available tools

list_projects

Input: { team_id: string, token?: string }. Output: { projects: [{ id: string, name: string, last_modified?: string }] }

list_project_files

Input: { project_id: string, token?: string }. Output: { files: [{ id: string, name: string, thumbnailUrl?: string }] }

get_file

Input: { file_id: string, node_ids?: string[], token?: string }. Output: { file: any } β€” full Figma file JSON or nodes response

generate_frontend

Input: { file_id: string, node_id?: string, token?: string, framework?: "react"|"html" }. Output: { files: Record<string, string> } β€” generated filename β†’ content