figma-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FIGMA_ACCESS_TOKEN | Yes | Figma access token required for authentication |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| validate_tokenA | Test if the configured token has access to a Figma file |
| get_file_infoB | Get basic metadata about a Figma file |
| get_node_detailsB | Get detailed information about a specific node (component, frame, etc.) |
| extract_stylesB | Extract color, text, and effect styles from a Figma file |
| get_assetsB | Get image URLs for nodes in a Figma file |
| get_variablesB | Get variables and variable collections from a Figma file (new Figma Variables API) |
| identify_componentsA | Identify UI components in a Figma design (charts, tables, forms, etc.) |
| detect_variantsC | Detect component variants and group them |
| detect_responsiveC | Detect responsive variations of components |
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 9 tools
Each tool targets a distinct aspect of Figma data: token validation, file metadata, node details, styles, assets, variables, and three specific component analyses (identification, variants, responsive). The overlapping-sounding component tools are clearly differentiated by their descriptions.
All tool names follow a consistent verb_noun pattern using clear verbs (validate, get, extract, identify, detect) and specific nouns. The convention is uniform across the entire set.
Nine tools is well within the ideal range for a specialized server, covering a cohesive set of read-only Figma operations without redundancy or bloat. Each tool earns its place.
The server covers the core read-only surface for Figma: file access, node introspection, styles, assets, variables, and component analysis. No create/update operations are included, but the server's apparent purpose is analysis; minor gaps like commenting or file search are not critical.