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://<your-run>.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

1. Start the Actor with OAuth fields filled and no PAT.
2. Open GET https://<container-url>/oauth/authorize in a browser (normal browser — not an embedded WebView; Figma requirement).
3. 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 (b

... View full README on GitHub