add_figma_file
Add a Figma file to your context
LABSCO SUMMARY
Feedback lands where the designer will find it, not in a chat log they were not in.
A posted comment takes a node id plus x and y, so a note about a misaligned button is attached to that button in the file, and replies keep a thread together instead of scattering. Reading is at thumbnail level rather than structural — a node comes back as an image, not as layer properties — so this supports review and discussion rather than generating code from a design.
What it is
A server over the Figma API for reading a file and working its comment threads, in 5 tools.
What you get
- A Figma file brought into context from its URL, which is where the file_key the other tools take comes from
- A thumbnail of a single node, so one frame or component can be looked at instead of the whole file
- Every comment on a file read back in one call
- A comment posted against a node at given x and y coordinates, so feedback sits on the element it is about
- Replies onto an existing thread by comment_id rather than a new comment beside it
Requirements
FIGMA_API_KEY and the URL of a file that key can open.
Setup effort
One command plus a key — npx figma-mcp, then supply credentials
USE CASES
01
Reviewing a design without opening Figma
Bring the file in by URL, look at the specific frame as a thumbnail rather than pulling the whole file, and read what has already been said about it in the comments.
02
Leaving feedback on the exact element it is about
Post the comment against the node with x and y coordinates so it is pinned where the designer will see it, and keep the follow-up in the same thread rather than starting a new one.
5 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
post_comment
Post a comment on a node in a Figma file
read_comments
Get all comments on a Figma file
reply_to_comment
Reply to an existing comment in a Figma file
view_node
Get a thumbnail for a specific node in a Figma file
BEFORE YOU INSTALL
What to know first
Tools you get
5 tools when we connected.
Requires
- npx on PATH
- FIGMA_API_KEY in your environment
Where it runs
The documented client runs the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 5 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx figma-mcpMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"figma-mcp": {
"command": "npx",
"args": [
"figma-mcp"
],
"env": {
"FIGMA_API_KEY": "<YOUR_API_KEY>"
}
}
}
}
