Figma MCP Server

What Figma MCP Server MCP server does

The Figma MCP Server MCP server gives compatible AI clients an MCP interface to selected Figma REST API operations. It supports file inspection, component discovery, asset export, comments, and project or team metadata. File analysis can return structure, metadata, styles, and depth-limited trees. Component operations cover listing, details, and usage information.

The server also includes MCP resources and prompts intended to guide common Figma workflows. The available tool set includes operations such as analyze_file, get_file_structure, list_components, export_node, get_comments, and create_comment; exact names may vary slightly in the implementation. Design modification helpers are present, but the project notes that REST API coverage may not support deep design writes.

How it works

The Figma MCP Server MCP server exposes MCP JSON-RPC at POST /mcp. On Apify, the endpoint is normally available at the run’s Container URL followed by /mcp. A client sends MCP requests to that URL while the Actor is running. The service also provides / for service information and /health for liveness and authentication status.

Authentication can use a personal access token supplied as figmaAccessToken in Actor input or through FIGMA_ACCESS_TOKEN for local execution. When a token is present, it is used for Figma API calls and OAuth routes are disabled. Alternatively, the server can start an OAuth authorization flow through /oauth/authorize; after consent, Figma redirects to /oauth/callback, and the refreshed session is stored in the Apify key-value store for that run.

Setup and configuration

For Apify deployment, install dependencies, authenticate with the Apify CLI, and run apify push. Start the Actor as a long-running web server, provide at least a Figma token or the required OAuth app fields, and copy the active Container URL into the MCP client configuration. The default local port is 8080, although Apify may override it.

Local development uses npm install followed by apify run. The server can also be started with Node when authentication and input are supplied through the environment or another mechanism. OAuth requires a client ID, client secret, an exact registered redirect URI, and optionally a comma-separated scope list. The documented default scopes include file content and comment read/write access.

Tools and capabilities

The Figma MCP Server MCP server provides capabilities for:

• Analyzing file structure, metadata, styles, and nested content
• Listing components and retrieving component details or usage
• Exporting nodes as PNG, SVG, PDF, or JPG
• Reading and creating Figma comments
• Listing projects and teams with related metadata
• Providing MCP resources and prompts for guided workflows

GET responses can be cached through the enableCaching input, which defaults to true. maxConcurrentRequests is configurable but marked as reserved for future use.

Limitations and notes

Apify Container URLs are tied to individual runs and stop working when those runs end. A new run may therefore require an updated client URL. OAuth stores one session per run in the default key-value store and is not designed for multiple concurrent users in one process.

The Figma MCP Server MCP server uses the REST API rather than the Figma Plugin API. As a result, operations requiring deeper design modification may need a separate Plugin API approach. A personal access token also takes precedence over OAuth: setting one disables the OAuth endpoints for API authentication.