Access Figma Designs and Export Assets

Figma MCP Server is an MCP server, written in Rust, that provides access to Figma files and design assets through a standardized interface. It lets an AI assistant retrieve file structures, navigate specific components within a file, and export design assets as PNG, JPG, SVG, or PDF, with depth control to keep responses within token limits.

Use it when an AI assistant needs to read a Figma file's structure, pull specific nodes or components, or export design assets for use elsewhere, for example generating code from a design, auditing components, or pulling icons and images out of a file. It requires a Figma personal access token from Figma's Developer Settings, so it needs at minimum read access to the files in question. Because deep file traversal can produce very large responses, the depth parameter is meant to be tuned deliberately rather than always maxed out; start shallow and increase it only when you need to go further into the tree.

• File access: retrieve Figma file structures with depth control (get_file)
• Node navigation: access specific components within a file, also with depth control (get_file_nodes)
• Image export: export design assets in PNG, JPG, SVG, or PDF formats (export_images)
• URL parsing: extract a file key from any Figma URL, including /file/ and /design/ URL formats and URLs carrying a node-id (parse_figma_url)
• Authentication check (get_me) and built-in usage instructions (help)
• Exported images are exposed as MCP resources with base64-encoded content, addressable at figma://file/{file_key}/node/{node_id}.{format}, and listable and readable like any other MCP resource

The depth parameter controls how much of the tree is returned: depth=1, the default, returns pages only for files or direct children for nodes; depth=2 adds top-level objects or grandchildren; depth=3 and above traverses deeper and should be used carefully to avoid oversized responses.

Install from crates.io:

cargo install figma-mcp

Or build from source:

git clone https://github.com/paulvandermeijs/figma-mcp.git
cd figma-mcp
cargo build --release

Get a Figma token from Figma's Developer Settings, export it as FIGMA_TOKEN, then run figma-mcp, or cargo run --release if built from source. The typical workflow is to call parse_figma_url to extract a file key from a Figma URL, then use that key with the other tools, adjusting the depth parameter to control response size.

Developers and designers building AI workflows that need programmatic access to Figma files - reading structure, pulling specific components, or exporting assets - without going through the Figma UI or writing direct Figma REST API calls. It is released under the MIT License.