Figma Structured MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| STORAGE_PROVIDER | No | The storage provider to use (e.g., 'custom') | |
| CUSTOM_UPLOAD_KEY | No | Your upload key for the custom upload server | |
| CUSTOM_UPLOAD_URL | No | The URL of your custom upload server | |
| FIGMA_ACCESS_TOKEN | Yes | Your Figma access token (required by Figma API) |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_figma_imagesA | |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'get_figma_images' has a clearly defined and distinct purpose focused on exporting, compressing, and uploading Figma images.
The single tool name follows a clear verb_noun pattern ('get_figma_images'), and with only one tool, there is perfect consistency. No naming conventions are mixed or violated.
A single tool is too few for a server named 'Figma Structured MCP', which implies broader functionality. While the tool is comprehensive, the server lacks basic operations like listing files, getting node details, or managing designs, making it feel incomplete and under-scoped.
The server is severely incomplete for Figma integration. It only provides image export/upload, missing essential operations such as retrieving file metadata, listing components, creating or updating designs, or even basic read operations beyond images. This will cause significant agent failures in typical Figma workflows.