figma-mcp
Allows AI agents to read, inspect, and export from Figma files programmatically.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@figma-mcp Export frame 1:42 as SVG"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
What is this?
figma-mcp is a Model Context Protocol server that gives LLM agents (Claude, GPT, etc.) the ability to read, inspect, and export from Figma files programmatically.
Built with the official MCP Python SDK using the FastMCP API.
Related MCP server: Figma MCP Server
Architecture
┌─────────────────────┐
│ Claude Desktop / │
│ Any MCP Client │
└────────┬────────────┘
│ stdio
┌────────▼────────────┐
│ figma-mcp Server │
│ (FastMCP) │
└────────┬────────────┘
│ HTTPS
┌────────▼────────────┐
│ Figma REST API │
│ api.figma.com/v1 │
└─────────────────────┘Project structure:
src/figma_mcp/
__init__.py # Entry point
config.py # Environment config (dotenv)
utils.py # Logger (stderr) + validation helpers
figma_client.py # Figma API client (requests)
server.py # FastMCP server + all tool definitionsInstallation
git clone https://github.com/Anakintano/figma-mcp.git
cd figma-mcp
pip install -e .Or with uv (recommended):
uv pip install -e .Configuration
1. Get a Figma Token
Click Generate new token
Copy the token
2. Set Environment Variable
Create a .env file in the project root:
FIGMA_ACCESS_TOKEN=figd_your_token_here3. Claude Desktop Setup
Add to your claude_desktop_config.json:
{
"mcpServers": {
"figma": {
"command": "python",
"args": ["-m", "figma_mcp"],
"cwd": "/path/to/figma-mcp",
"env": {
"FIGMA_ACCESS_TOKEN": "figd_your_token_here"
}
}
}
}Tools
Tool | Description | Key Params |
| Get a complete Figma file |
|
| Get specific nodes/frames |
|
| List all components |
|
| List all styles |
|
| Export as PNG/JPG/SVG/PDF |
|
Finding your file key: In any Figma URL like
https://www.figma.com/file/ABC123xyz/My-Design, the file key isABC123xyz.
Use Cases
1. Design System Audit
Prompt: "List all components in my Figma file
abc123and tell me which ones don't follow our naming convention"
The agent uses list_components to fetch every component, then analyzes naming patterns — great for enforcing consistency across large design systems.
2. Developer Handoff
Prompt: "Get the layout details of the login page frame
1:42from filexyz789"
Uses get_frame_nodes to extract exact positions, sizes, colors, fonts, and spacing — giving developers precise specs without leaving the chat.
3. Asset Export Pipeline
Prompt: "Export all icon frames
1:10,1:11,1:12as SVGs from fileabc123"
The agent calls export_assets with format=svg and returns download URLs for each icon, ready for use in code.
4. Style Token Extraction
Prompt: "What are all the color and text styles in file
myDesign? Format them as CSS variables"
Uses list_styles to pull every defined style, then the LLM formats them into usable CSS custom properties:
--color-primary: #3B82F6;
--color-secondary: #10B981;
--font-heading: Inter, 24px, 700;5. Design Review / QA
Prompt: "Get the full structure of file
abc123and check if all frames have consistent padding"
Fetches the entire file with get_figma_file, then the LLM traverses the node tree to flag layout inconsistencies.
6. Multi-File Comparison
Prompt: "Compare the components in file
designV1vsdesignV2and list what changed"
Calls list_components on both files, and the LLM diffs the results to produce a changelog of design changes.
Example Prompts
Here are ready-to-use prompts for Claude Desktop with this MCP server:
"Get the structure of my Figma file with key abc123XYZ"
"Show me all components in this design file"
"Export frame 1:42 as an SVG"
"What text styles are defined in this design?"
"Extract the layout specs for nodes 1:2 and 3:4"
"List all color styles and convert them to a Tailwind config"
"Get the login page frame and describe the UI elements"API Reference
get_figma_file
Param | Type | Description |
|
| Figma file key |
get_frame_nodes
Param | Type | Description |
|
| Figma file key |
|
| Node IDs (e.g., |
list_components
Param | Type | Description |
|
| Figma file key |
list_styles
Param | Type | Description |
|
| Figma file key |
export_assets
Param | Type | Description |
|
| Figma file key |
|
| Node IDs to export |
|
|
|
|
| Scale factor (default: |
Running Tests
pytest tests/ -vLicense
This project is licensed under the MIT License. Copyright © 2026 Aditya Saxena / anakintano
Available Tools
5 toolsexport_assetsC
Export nodes as images (PNG, JPG, SVG, PDF).
Inputs: file_key (required), node_ids (required), format, scale.
get_figma_fileC
Get a complete Figma file by its key.
Inputs: file_key (required).
get_frame_nodesC
Get specific nodes/frames from a Figma file.
Inputs: file_key (required), node_ids (required).
list_componentsB
List all components in a Figma file.
Inputs: file_key (required).
list_stylesC
List all styles in a Figma file.
Inputs: file_key (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: exporting assets, retrieving full files, fetching specific nodes, listing components, and listing styles. No overlap or ambiguity.
All tools follow a consistent verb_noun snake_case pattern (e.g., export_assets, get_figma_file, list_components), making naming predictable.
5 tools is appropriate for a Figma-focused server, covering core read and export operations without being overwhelming or too sparse.
The set covers key read operations (file, nodes, components, styles) and asset export, but is missing file listing, search, and write operations, which are notable gaps for a full Figma API surface.
Maintenance
Related MCP Connectors
Give AI agents your deeepSpace design system: components, tokens, styles and code mappings.
The Figma MCP server brings Figma design context directly into your AI workflow.
Build and manage your design system with AI: tokens, themes, components, icons, Figma and code.
Generate, inspect, and manage Flowstep UI designs directly from your AI assistant.
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables interaction with Figma designs through the Figma API, allowing users to export images in multiple formats, extract style data and CSS, analyze design elements, and retrieve SVG code from Figma files. Supports batch operations and comprehensive design element analysis including images, vectors, and components.713 npm11MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Figma designs using natural language commands, supporting file analysis, component extraction, asset export, comment management, and design system queries through the Figma API.1,123 npm1ISC
- AlicenseAqualityDmaintenanceEnables AI agents to interact with Figma to create, read, and manage designs using the Figma REST API and a dedicated plugin. It supports advanced features like UI generation from text, webpage reconstruction in Figma, and design token synchronization with codebases.20MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to read, analyze, and modify Figma designs, including bulk style updates, accessibility audits, comment triage, and code generation from designs.679 npmMIT