Design feedback that is not attached to a specific element is nearly worthless — 'the spacing looks off' on a file with forty frames costs more to locate than to fix. Anchoring comments to nodes, with thumbnails to confirm which node, keeps that context. Note the scope: this reads and comments, it does not edit. That is a narrower surface than the Figma servers that create and modify nodes, and a correspondingly safer one to point at a file somebody else owns.
A Figma client focused on the review loop: add a file to context, view a node as a thumbnail, and read, post and reply to comments.
- read_comments returns all comments on a file, which is the design review as text.
- post_comment attaches a comment to a specific node rather than to the file generally, and reply_to_comment continues an existing thread.
- view_node returns a thumbnail for a node, so the thing being commented on can be looked at.
- add_figma_file brings a file into context to work against.
A Figma access token for the file.
One command plus a key — npx -y @smithery/cli install @deepsuthar496/figma-mcp-server --client claude, then supply credentials