Figma MCP Tool
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FIGMA_TOKEN | Yes | Your Figma access token (starts with 'figd_') |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_figma_imageC | 根据Figma URL获取节点的图片 |
| get_figma_stylesC | 根据Figma URL获取节点的样式数据 |
| export_multiple_imagesC | 批量导出多个节点的图片 |
| get_file_infoC | 获取Figma文件的基本信息 |
| get_node_imagesC | 获取节点中的所有图片资源 |
| get_node_svgC | 获取节点的SVG数据 |
| extract_node_elementsC | 提取节点中的所有设计元素（图片、矢量、组件） |
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 7 tools
Most tools have distinct purposes, but there is some overlap between 'export_multiple_images' and 'get_node_images' that could cause confusion. The descriptions help differentiate them, but the boundaries are not perfectly clear.
The naming follows a consistent verb_noun pattern with minor deviations, such as 'export_multiple_images' using an adjective. Overall, the pattern is readable and predictable across the tool set.
With 7 tools, the count is well-scoped for a Figma integration server. Each tool appears to serve a specific purpose related to extracting or retrieving design assets and data.
The tool set covers key operations for accessing Figma assets and styles, but there are minor gaps such as updating or modifying nodes. Agents can likely work around these limitations for most common workflows.