// MCP TOOL REFERENCE

FIGMA API INTEGRATION TOOLS

18 tools from the Figma API Integration MCP Server, categorised by risk level.

READ TOOLS

check_api_key Check if a Figma API key is already configured get_comments Get comments on a Figma file get_component Get a component by key get_file Get a Figma file by key get_file_components Get components from a file get_file_nodes Get specific nodes from a Figma file get_file_styles Get styles from a file get_image Get images for nodes in a Figma file get_image_fills Get URLs for images used in a Figma file get_project_files Get files for a project get_style Get a style by key get_team_component_sets Get component sets for a team get_team_components Get components for a team get_team_projects Get projects for a team get_team_styles Get styles for a team

WRITE TOOLS

post_comment Post a comment on a Figma file 2/5 set_api_key Set your Figma API personal access token (will be saved to ~/.mcp-figma/config.json) 3/5

DESTRUCTIVE TOOLS

delete_comment Delete a comment from a Figma file 4/5

// FAQ

How many tools does the Figma API Integration MCP server have? +

The Figma API Integration MCP server exposes 18 tools across 3 categories: Read, Write, Destructive.

How do I enforce policies on Figma API Integration tools? +

Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Figma API Integration server.

What risk categories do Figma API Integration tools fall into? +

Figma API Integration tools are categorised as Read (15), Write (2), Destructive (1). Each category has a recommended default policy.

Enforce policies on Figma API Integration

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept

github.com/policylayer/intercept →