Talk to Figma MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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_document_infoB | Get detailed information about the current Figma document |
| get_selectionB | Get information about the current selection in Figma |
| read_my_designA | Get detailed information about the current selection in Figma, including all node details |
| get_node_infoB | Get detailed information about a specific node in Figma |
| get_nodes_infoA | Get detailed information about multiple nodes in Figma |
| create_rectangleB | Create a new rectangle in Figma |
| create_frameC | Create a new frame in Figma |
| create_textB | Create a new text element in Figma |
| set_fill_colorC | Set the fill color of a node in Figma can be TextNode or FrameNode |
| set_stroke_colorB | Set the stroke color of a node in Figma |
| move_nodeA | Move a node to a new position in Figma |
| clone_nodeB | Clone an existing node in Figma |
| resize_nodeC | Resize a node in Figma |
| delete_nodeC | Delete a node from Figma |
| delete_multiple_nodesA | Delete multiple nodes from Figma at once |
| export_node_as_imageB | Export a node as an image from Figma |
| set_text_contentA | Set the text content of an existing text node in Figma |
| get_stylesA | Get all styles from the current Figma document |
| get_local_componentsA | Get all local components from the Figma document |
| get_annotationsA | Get all annotations in the current document or specific node |
| set_annotationC | Create or update an annotation |
| set_multiple_annotationsC | Set multiple annotations parallelly in a node |
| create_component_instanceC | Create an instance of a component in Figma |
| get_instance_overridesA | Get all override properties from a selected component instance. These overrides can be applied to other instances, which will swap them to match the source component. |
| set_instance_overridesA | Apply previously copied overrides to selected component instances. Target instances will be swapped to the source component and all copied override properties will be applied. |
| set_corner_radiusA | Set the corner radius of a node in Figma |
| scan_text_nodesB | Scan all text nodes in the selected Figma node |
| scan_nodes_by_typesA | Scan for child nodes with specific types in the selected Figma node |
| set_multiple_text_contentsC | Set multiple text contents parallelly in a node |
| set_layout_modeB | Set the layout mode and wrap behavior of a frame in Figma |
| set_paddingA | Set padding values for an auto-layout frame in Figma |
| set_axis_alignA | Set primary and counter axis alignment for an auto-layout frame in Figma |
| set_layout_sizingB | Set horizontal and vertical sizing modes for an auto-layout frame in Figma |
| set_item_spacingA | Set distance between children in an auto-layout frame |
| get_reactionsA | Get Figma Prototyping Reactions from multiple nodes. CRITICAL: The output MUST be processed using the 'reaction_to_connector_strategy' prompt IMMEDIATELY to generate parameters for connector lines via the 'create_connections' tool. |
| set_default_connectorB | Set a copied connector node as the default connector |
| create_connectionsA | Create connections between nodes using the default connector style |
| join_channelB | Join a specific channel to communicate with Figma |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| design_strategy | Best practices for working with Figma designs |
| read_design_strategy | Best practices for reading Figma designs |
| text_replacement_strategy | Systematic approach for replacing text in Figma designs |
| annotation_conversion_strategy | Strategy for converting manual annotations to Figma's native annotations |
| swap_overrides_instances | Guide to swap instance overrides between instances |
| reaction_to_connector_strategy | Strategy for converting Figma prototype reactions to connector lines using the output of 'get_reactions' |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 38 tools
Most tools have distinct purposes, but some overlap exists, such as 'get_node_info' and 'read_my_design' (both retrieve node details), and 'delete_node' and 'delete_multiple_nodes' (similar deletion functions). The descriptions help clarify differences, but agents might occasionally misselect between closely related tools.
The tool names follow a consistent verb_noun pattern throughout, using snake_case uniformly, which aids readability. Minor deviations include 'read_my_design' (which uses 'my' instead of a direct verb_noun) and 'join_channel' (which is less descriptive of the domain), but overall the naming is predictable.
With 38 tools, the count is excessive for a Figma interaction server, making it heavy and potentially overwhelming for agents. While Figma has a broad API, many tools could be consolidated (e.g., multiple set_* tools for styling), indicating poor scoping and an unnecessarily large surface.
The tool set provides comprehensive coverage for Figma operations, including CRUD for nodes (create, get, update, delete), styling (colors, layout, annotations), export, and component management. No obvious gaps exist; agents can perform full design workflows without dead ends.