Figma MCP Server

Name: Figma MCP Server
Author: oabolade

by oaboladeversion 2.1.0i★ –iRuns on your computer

Registry nameio.github.oabolade/figma_mcp_server_actor

Install

Overview

Description from the maker (original English)

MCP server enabling AI assistants to interact with Figma designs via natural language commands

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Design, images & audio
You need to fill in: FIGMA_ACCESS_TOKEN

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: FIGMA_ACCESS_TOKEN

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "figma-actor": {
      "command": "npx",
      "args": [
        "-y",
        "@oabolade-pegasus/figma-mcp-server"
      ],
      "env": {
        "FIGMA_ACCESS_TOKEN": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add figma-actor --env FIGMA_ACCESS_TOKEN=your-value -- npx -y @oabolade-pegasus/figma-mcp-server

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "figma-actor": {
      "command": "npx",
      "args": [
        "-y",
        "@oabolade-pegasus/figma-mcp-server"
      ],
      "env": {
        "FIGMA_ACCESS_TOKEN": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "figma-actor": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@oabolade-pegasus/figma-mcp-server"
      ],
      "env": {
        "FIGMA_ACCESS_TOKEN": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

FIGMA_ACCESS_TOKEN secret required env
Figma Personal Access Token for API authentication. Get yours at https://www.figma.com/developers/api#access-tokens

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account oabolade, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Design, images & audioi

More stars than 0% of the other 2750 servers in this category
Published to the registry more recently than 1% of the other 2750 servers in this category
Basic checks equal to or better than 100% of the other 2750 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Figma MCP Server safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: FIGMA_ACCESS_TOKEN

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (2.1.0) reached the registry 11 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Figma Context MCP, Claude Real Video, Figma MCP Server

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Figma Context MCP

by GLips

Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.

Runs on your computer★ 16,165MITUpdated 5 months ago

Install

Claude Real Video

by HUANGCHIHHUNGLeo

Let any LLM watch a video locally — and search everything it has ever watched.

Runs on your computer★ 2,284MITUpdated 2 months ago

Install

Figma MCP Server

by figma

Figma’s official server gives AI your design data so it can turn designs into code or describe them accurately. Connects to Figma’s cloud.

Runs in the cloud★ 2,152Updated 13 months ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Figma MCP Server (Apify Actor)

Model Context Protocol (MCP) server that exposes Figma REST API capabilities to AI assistants (Cursor, Claude, custom agents). Runs as a long-running web server on the Apify platform (standby / container URL) or locally via apify run.

Features

File analysis — structure, metadata, styles, depth-limited trees
Components — list, details, usage
Assets — export nodes (PNG, SVG, PDF, JPG)
Comments — read and create
Projects / teams — listings and metadata
MCP resources & prompts for guided workflows

Authentication

Personal Access Token (default)

Recommended for solo use. Set `figmaAccessToken` in Actor input (or FIGMA_ACCESS_TOKEN in env).

Generate: Figma → Settings → Security → Personal access tokens
API header: X-Figma-Token
When PAT is set, OAuth is disabled for API calls (and /oauth/* routes return an error).

OAuth 2.0 (optional — team / shared files)

Use when you omit figmaAccessToken and provide a Figma OAuth app:

Input	Purpose
`oauthClientId`	From Figma → Developers → Apps
`oauthClientSecret`	Same app
`oauthRedirectUri`	Exact redirect URL registered on the app, e.g. `https:// .runs.apify.net/oauth/callback`
`oauthScopes`	Optional; comma-separated scopes. Must be a subset of the app’s configured scopes. Defaults include `file_content:read`, `file_content:write`, `file_comments:read`, `file_comments:write`.

Flow

Start the Actor with OAuth fields filled and no PAT.
Open `GET https:// /oauth/authorize` in a browser (normal browser — not an embedded WebView; Figma requirement).
After consent, Figma redirects to `/oauth/callback`; tokens are stored in the run’s default key-value store (FIGMA_OAUTH_SESSION) and refreshed when near expiry.

Token exchange uses Figma’s documented endpoints (https://api.figma.com/v1/oauth/token and .../oauth/refresh). Codes expire quickly — complete the redirect promptly.

Requirements

Node.js ≥ 20
Apify account (for cloud)
Figma PAT and/or OAuth app

Quick start (Apify Cloud)

npm install

apify login apify push

In Apify Console, open the Actor, set input (at minimum figmaAccessToken), start with web server / long-running as required by your template, then use the Container URL from the run.

Deploy reference: apify push builds and publishes; see Apify CLI.

Configuration (input)

Parameter	Type	Default	Description
`figmaAccessToken`	string	—	PAT (recommended). If set, used for all Figma API calls.
`port`	integer	`8080`	HTTP listen port (Apify may override via `web_server_port`).
`oauthClientId`	string	—	OAuth app client ID (only if not using PAT).
`oauthClientSecret`	string	—	OAuth app secret (secret input).
`oauthRedirectUri`	string	—	Must match Figma app redirect URI exactly.
`oauthScopes`	string	—	Optional scope override (comma-separated).
`maxConcurrentRequests`	integer	`10`	Reserved / future use.
`enableCaching`	boolean	`true`	Cache GET responses from Figma.

Local / CLI input file example (apify run):

"figmaAccessToken": "figd_...", "port": 8080 }

HTTP API

Method	Path	Description
`GET`	`/`	Service info and endpoint list
`GET`	`/health`	Liveness; includes `auth_mode`: `pat` \	`oauth` \	`pending_oauth`, `figma_authenticated`
`POST`	`/mcp`	MCP JSON-RPC 2.0 (primary transport for this server)
`GET`	`/oauth/authorize`	Start OAuth (browser); disabled if PAT is set
`GET`	`/oauth/callback`	OAuth redirect handler

Apify MCP path: .actor/actor.json sets webServerMcpPath to `/mcp`. Your MCP client URL is typically:

https:// .runs.apify.net/mcp

(Use the Container URL from the run page + /mcp.)

Cursor IDE

Deploy and start the Actor; copy the run Container URL (while status is RUNNING).
Edit `~/.cursor/mcp.json` (paths differ on Windows/Linux — see Cursor docs).

Example (remote HTTP MCP — adjust to your Cursor version’s expected shape):

"mcpServers": { "figma-mcp-standby": { "url": "https://YOUR_RUN_ID.runs.apify.net/mcp" } } }

Notes

`env.APIFY_TOKEN` in mcp.json is not passed to this Node process; it does not replace Figma auth. Use `figmaAccessToken` (or OAuth) in Actor input.
Container URLs are per run and stop working when the run ends; update mcp.json and restart Cursor after a new run.
If connection fails, use Cursor → Output → MCP and curl https://.../health.

Claude Desktop / other clients

Use your client’s supported way to attach a remote MCP URL (e.g. mcp-remote pointing at https://.../mcp). Paths and query params depend on the client version.

Local development

npm install

apify run

Or run the entry with Node if you inject env / input yourself:

export FIGMA_ACCESS_TOKEN="figd_..."

node src/main.js

Check health (port from logs or input):

curl -s http://localhost:8080/health | jq .

Sample MCP initialize:

curl -s -X POST http://localhost:8080/mcp \

-H "Content-Type: application/json" \ -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

Project structure

figma_mcp_actor/

├── .actor/ │ ├── actor.json # Apify Actor metadata (incl. webServerMcpPath: /mcp) │ ├── input_schema.json │ ├── output_schema.json │ └── dataset_schema.json ├── src/ │ ├── main.js # Express app, /mcp, /oauth/*, Apify bootstrap │ ├── figma/ │ │ ├── auth.js # PAT + OAuth token exchange, refresh, KV hook │ │ └── client.js # Figma REST wrapper │ ├── oauth/ │ │ └── persist.js # Apify KV: FIGMA_OAUTH_SESSION │ ├── mcp/ # Protocol, handlers, server │ ├── tools/ │ ├── resources/ │ └── prompts/ ├── Dockerfile ├── package.json └── README.md

MCP tools (overview)

Includes (names may vary slightly in code): file analysis (analyze_file, get_file_structure, …), components (list_components, …), export (export_node, …), comments (get_comments, create_comment, …), design modification helpers, plus resources (figma://file/..., etc.) and prompts for common tasks.

Limitations

REST vs Plugin API — deep design writes may need the Plugin API; this Actor uses REST where supported.
Ephemeral Apify URLs — each run has a new base URL unless you use a stable hosting pattern.
OAuth — single stored session per run (KV); not multi-user concurrent OAuth in one process.

Scripts

npm run lint

npm run lint:fix npm run format

License

ISC

Changelog

0.2

Optional OAuth 2.0 (Figma authorization code + refresh); PAT remains default when set.
`/oauth/authorize` and `/oauth/callback`; session persisted in default KV (FIGMA_OAUTH_SESSION).
Input: oauthRedirectUri, oauthScopes.
Health JSON: auth_mode, figma_authenticated.

0.1 / 0.0.1

Initial MCP + Figma REST integration, PAT, long-running server, /mcp JSON-RPC.

References: Apify Actors · Figma REST API · Model Context Protocol

Figma MCP Server

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Design, images & audioi

Common questions

Alternatives

Figma Context MCP

Claude Real Video

Figma MCP Server

README from the maker

Figma MCP Server (Apify Actor)

Features

Authentication

Personal Access Token (default)

OAuth 2.0 (optional — team / shared files)

Requirements

Quick start (Apify Cloud)

Configuration (input)

HTTP API

Cursor IDE

Claude Desktop / other clients

Local development

Project structure

MCP tools (overview)

Limitations

Scripts

License

Changelog

0.2

0.1 / 0.0.1