servers / figma-mcp

figma-mcp

communityunknownnpmwrite capablehealthy

ModelContextProtocol server for Figma


01Tools · 5

How to read this: tool names here are observed from a live tools/list handshake. The Risk label is a heuristic inferred from the tool name (write/destructive verbs), not from executing the tool — a conservative guess, not a verified capability. We never escalate risk from a description. Found one that's wrong? Tell us — we fix on report.

ToolRiskSide effectsApproval
add_figma_file
Add a Figma file to your context
writetrueunknown
reply_to_comment
Reply to an existing comment in a Figma file
writetrueunknown
post_comment
Post a comment on a node in a Figma file
writetrueunknown
view_node
Get a thumbnail for a specific node in a Figma file
readfalseunknown
read_comments
Get all comments on a Figma file
readfalseunknown

02Install & source
npx -y figma-mcp
npx

03Access granted
Design tools · write

The access this server can exercise, inferred from its verified tools — not a declared OAuth scope.


05Provenance & freshness
sourcesnpm registry [p4]
last_checked2026-08-16 08:45Z
next_check2026-08-18 08:28Z
cadenceevery 48h
verifiedtools_list:passed handshake:passed metadata:passed tools_list:passed handshake:passed metadata:passed tools_list:passed handshake:passed metadata:passed tools_list:passed
index_statusindex6 unique facts >= 5

06Badge

Add the “as seen on MCPExplorer” badge to your README. figma-mcp MCP — as seen on mcpexplorer.com

[![figma-mcp MCP — as seen on mcpexplorer.com](https://mcpexplorer.com/badge/figma-mcp.svg)](https://mcpexplorer.com/servers/figma-mcp)

Next step

This is one server. A loadout combines the right servers, governance, and proven plays for a whole job — assembled deliberately, not tool-dumped.

Explore loadouts →
figma-mcp — MCPExplorer