Figma

Provides access to Figma files, nodes, and image exports via an MCP interface for integrated workflows.

rust

7

GitHub Stars

rust

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "paulvandermeijs-figma-mcp": {
      "command": "figma-mcp",
      "args": [],
      "env": {
        "FIGMA_TOKEN": "YOUR_TOKEN_HERE"
      }
    }
  }
}

You deploy a Model Context Protocol (MCP) server that gives you controlled access to Figma files and design assets through a consistent interface. It handles file structures, specific nodes, image exports, and safe depth-limited responses so you can integrate Figma data into your apps and pipelines with confidence.

How to use

Start by configuring authentication and launching the local MCP server. Once the server is running, you can query it to retrieve file structures, navigate nodes, and export images for use in your applications.

How to use with an MCP client

Obtain a Figma access token from your Figma account. Set it in your environment as FIGMA_TOKEN so the MCP server can access Figma data.
Start the MCP server using one of the provided runtime options. If you installed the binary, run the local server directly. If you built from source, run the project with its build command.

Notes on usage patterns

Use the parse_figma_url tool to extract a file key from any Figma URL. This key is then used with other tools to access file data.
Use depth control to manage response size. A depth of 1 returns pages and top-level objects, while higher depths traverse more levels. Choose the depth based on your token limits and data needs.
Exported images are available as MCP resources and can be read as base64-encoded data. You can list and read these resources through your MCP client.

Supported URLs and keys

The MCP server accepts common Figma URL patterns to extract file keys, including URLs like https://www.figma.com/file/FILE\_ID/filename and https://www.figma.com/design/FILE\_ID/filename, with optional node-id query parameters.

Security and tokens

Keep your FIGMA_TOKEN secure. Do not expose it in client-side code or logs. The MCP server uses this token to access Figma data on your behalf.

Resource access

Exported images are exposed as MCP resources. You can list resources to see all exports and read a resource to obtain the base64-encoded image data. Resource URIs follow the format figma://file/{file_key}/node/{node_id}.{format}.

Available tools

parse_figma_url

Extracts the Figma file key from a Figma URL so you can identify the file to query.

get_file

Retrieves the file structure with an adjustable depth to limit response size.

get_file_nodes

Fetches specific nodes within a file, with depth control.

export_images

Exports images from selected nodes in formats like PNG, JPG, SVG, or PDF and makes them available as MCP resources.

get_me

Tests authentication and confirms access to the MCP server.

help

Displays usage instructions and available commands.