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.
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.
- 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
A Figma API token, supplied at launch through --figma-token.
One command plus a key — npx @smithery/cli@latest install @thirdstrandstudio/mcp-figma --client claude, then supply credentials