Figma MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FIGMA_API_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": true
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetch_figma_node_imageB | Fetches a PNG image of a Figma node or frame using the file key and node ID. Returns the image as base64. |
| generate_pseudo_code_from_figma_frameB | It will generates JSX and CSS pseudo-code for a Figma frame or node, given its file key and node ID. Useful for converting Figma designs to code. Can also be used to generate code for specific components or frames in Figma. |
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 2 tools
The two tools have clearly distinct purposes: one fetches an image of a Figma node, while the other generates pseudo-code from a Figma frame. There is no overlap or ambiguity in their functions, making it easy for an agent to select the correct tool based on the task.
The tool names follow a consistent verb_noun pattern (fetch_figma_node_image, generate_pseudo_code_from_figma_frame), but there is a minor deviation in verb tense ('fetches' vs 'generates') and slight length variation. Overall, the naming is predictable and readable, with only small inconsistencies.
With only two tools, the server feels thin and under-scoped for a Figma integration. While the tools cover image fetching and code generation, a Figma MCP server would typically benefit from more operations, such as listing files, accessing design properties, or managing comments, making this set incomplete for the domain.
The tool surface is significantly incomplete for a Figma server. It lacks basic CRUD operations like listing files or nodes, updating designs, or accessing metadata. The two tools provided are useful but do not cover core workflows, leaving obvious gaps that could cause agent failures in common Figma-related tasks.