@nvanexan/figma-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FIGMA_API_KEY | Yes | Your Figma Personal Access Token (PAT). You can generate a token in Figma under Settings > Personal Access Tokens. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_figma_contextA | Extract design context (layout, styles, text, dimensions) from a Figma URL as CSS-like properties |
| get_figma_imageB | Export a rendered image of a Figma node as a URL |
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 extracts design context as CSS-like properties, while the other exports rendered images. There is no overlap in functionality, making it easy for an agent to choose the right tool based on the need for data extraction versus visual output.
Both tools follow a consistent verb_noun pattern with 'get_figma_' as a prefix, using snake_case throughout. This predictable naming scheme enhances readability and makes the tool set coherent and easy to understand.
With only two tools, the server feels thin for a Figma integration, which typically involves more operations like creating or updating designs, listing files, or managing comments. The limited scope may restrict agent workflows, suggesting an incomplete surface for the domain.
The tool set is severely incomplete for a Figma MCP server, covering only context extraction and image export. It lacks core operations such as file management, design creation, or collaboration features, which are essential for comprehensive Figma integration, leading to potential agent failures in broader tasks.