figma_delete_comment
Delete a comment from a Figma file
LABSCO SUMMARY
Exporting frames by hand every time you need to see what a design actually looks like now.
Files, nodes and rendered images are one call each, and figma_get_images does the export itself at the scale and format you ask for, so getting a frame in front of a model is not a manual step. The library analytics tools answer the question a design system owner keeps asking and cannot easily see — which components, styles and variables are in use — and the webhook tools are what turn a change in a team file into something happening on your side.
What it is
A Figma REST client with 31 tools: files, nodes and rendered images, comments and reactions, team and project inventories, components, component sets and styles, webhooks, and library analytics.
What you get
- A whole file by key or a specific set of node ids, with depth, geometry, plugin data and version controls
- Frames rendered as images at a chosen format and scale, with SVG options for ids, outlined text and simplified strokes, plus a file's image fills
- Version history of a file, paged
- Comments read as markdown or raw, posted, deleted, and reacted to with an emoji
- Team projects and project files, and the components, component sets and styles held in a team or in a single file, each also fetchable by key
- Webhooks created against a team and event type with an endpoint and passcode, then listed, updated and deleted
- Library analytics for component, style and variable usage, grouped and paged with a cursor
Requirements
A Figma API token, supplied at launch through --figma-token.
Setup effort
One command plus a key — npx @smithery/cli@latest install @thirdstrandstudio/mcp-figma --client claude, then supply credentials
USE CASES
01
Getting a design in front of a model
Pull the file or just the node ids you care about, then render those frames as images at the scale and format you want — the export step happens in the call.
02
Finding out which components a file is built from
Components and component sets in the file, resolved by key against the team library — the lookup you do before deciding whether a screen uses the design system or a copy of it.
03
Keeping up with a file's comment thread
Read the comments as markdown, reply in place, react rather than reply where a reaction is enough, and delete what was resolved.
04
Finding out what the design system is actually used for
Usage data for components, styles and variables, grouped and paged — the evidence for deprecating something, rather than an assumption about it.
05
Reacting to a design change automatically
Register a webhook against a team and event type with an endpoint and passcode, then list, update or remove it as the integration changes.
06
Auditing styles across a team
Team styles against file styles answers where a colour or type ramp drifted, and version history says when it happened.
31 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
figma_delete_comment_reaction
Delete a reaction from a comment
figma_delete_webhook
Delete a webhook
figma_get_comment_reactions
Get reactions for a comment
figma_get_comments
Get comments in a Figma file
figma_get_component
Get a component by key
figma_get_component_set
Get a component set by key
figma_get_file
Get a Figma file by key
figma_get_file_component_sets
Get component sets in a file
figma_get_file_components
Get components in a file
figma_get_file_nodes
Get specific nodes from a Figma file
figma_get_file_styles
Get styles in a file
figma_get_file_versions
Get version history of a Figma file
figma_get_image_fills
Get image fills in a Figma file
figma_get_images
Render images from a Figma file
figma_get_library_analytics_component_usages
Get library analytics component usage data
figma_get_library_analytics_style_usages
Get library analytics style usage data
figma_get_library_analytics_variable_usages
Get library analytics variable usage data
figma_get_me
Get the current user
figma_get_project_files
Get files in a project
figma_get_style
Get a style by key
figma_get_team_component_sets
Get component sets in a team
figma_get_team_components
Get components in a team
figma_get_team_projects
Get projects in a team
figma_get_team_styles
Get styles in a team
figma_get_team_webhooks
Get webhooks for a team
figma_get_webhook
Get a webhook by ID
figma_post_comment
Add a comment to a Figma file
figma_post_comment_reaction
Add a reaction to a comment
figma_post_webhook
Create a webhook
figma_update_webhook
Update a webhook
BEFORE YOU INSTALL
What to know first
Tools you get
31 tools when we connected. None of the tools edits a design: writes are limited to comments, comment reactions and webhooks. On large files, call figma_get_file with depth = 1 first.
Requires
- npx on PATH
- Node.js
- FIGMA_API_KEY in your environment
CONTEXT COST
Moderate Standing cost
Rated by the size of the 31 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
Claude Desktop — Smithery
TERMINAL
npx @smithery/cli@latest install @thirdstrandstudio/mcp-figma --client claudeMCP Clients
Claude Desktop — npx
CLAUDE DESKTOP — NPX · JSON
{
"mcpServers": {
"figma": {
"command": "npx",
"args": [
"@thirdstrandstudio/mcp-figma",
"--figma-token",
"<YOUR_FIGMA_API_KEY>"
]
}
}
}Claude Desktop — Local, env token
CLAUDE DESKTOP — LOCAL, ENV TOKEN · JSON
{
"mcpServers": {
"figma": {
"command": "node",
"args": [
"<YOUR_PATH_TO_MCP_FIGMA>/dist/index.js"
],
"env": {
"FIGMA_API_KEY": "<YOUR_FIGMA_API_KEY>"
}
}
}
}Claude Desktop — Local, token flag
CLAUDE DESKTOP — LOCAL, TOKEN FLAG · JSON
{
"mcpServers": {
"figma": {
"command": "node",
"args": [
"<YOUR_PATH_TO_MCP_FIGMA>/dist/index.js",
"--figma-token",
"<YOUR_FIGMA_API_KEY>"
]
}
}
}
