figma-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FIGMA_ACCESS_TOKEN | Yes | Your Figma personal access token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_figma_fileC | Get a complete Figma file by its key. |
| get_frame_nodesC | Get specific nodes/frames from a Figma file. |
| list_componentsB | List all components in a Figma file. |
| list_stylesC | List all styles in a Figma file. |
| export_assetsC | Export nodes as images (PNG, JPG, SVG, PDF). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.