Figma MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FIGMA_TOKEN | Yes | Your Figma personal access token with file_content:read permission. Used in X-Figma-Token headers to https://api.figma.com. | |
| MCP_TRANSPORT | No | Transport mode for the MCP server. Use 'stdio' to run over stdio; otherwise the default loopback HTTP server is started. | http |
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 | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| figma_list_framesB | List Frame, Component, and Instance roots available in a Figma Design file. |
| figma_prepare_designB | Fetch, normalize, render, download, validate, and persist one Figma design root. |
| figma_inspect_designC | Inspect a normal or diagnostic Figma Packet through a compact task-oriented view. |
| figma_generate_unity_prefabB | Generate a staged, statically verified UGUI Direct YAML Prefab snapshot. |
| figma_verify_unity_prefabA | Statically verify generated Prefab YAML, ownership metadata, source map, sprites, and file ids. |
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 targets a distinct stage of the Figma-to-Unity pipeline: listing frames, preparing design data, generating prefabs, inspecting, and verifying. No two tools appear to overlap in purpose.
All tools follow a consistent `figma_` prefix with a verb_noun pattern: list_frames, prepare_design, generate_unity_prefab, inspect_design, verify_unity_prefab. This makes the toolset predictable and easy to navigate.
Five tools is well-scoped for a focused Figma-to-Unity design-to-prefab workflow. Each tool fills a clear role without unnecessary bloat or missing core steps.
The workflow covers the essential stages: discover frames, prepare a design, generate a prefab, inspect it, and verify it. Minor gaps exist, such as no explicit tool for cleanup or batch operations, but these do not impede the primary pipeline.