figma-comments-mcp
Allows reading Figma file comments, scoped to a specific frame or the whole file, with resolution of comment pins to layer names and rendering of pinned nodes as images.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@figma-comments-mcpWhat comments are on the checkout screen?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
figma-comments-mcp
Lets Claude read your Figma feedback — comment threads and Dev Mode annotations — so you don't have to retype it.
Design feedback lives in Figma. The agent can't see it. So every round meant reading comments in Figma, retyping them into Claude, and getting the change back — with me as the copy-paste layer in between.
Now: leave your comments in Figma, paste the frame link, and Claude reads them and makes the changes.
What it does
Two tools.
list_figma_comments — reads the comment threads and annotations on a file, or on one
frame within it. Each one is resolved to the layer it's pinned to, so a comment arrives as
"on 01 · Results — default" rather than a node id.
rNK3UkoeLnbBHHYQiv9MW8 · frame 132:5 "01 · Results — default" · 1 thread · 1 annotation
1873426532 · Eun Ji Jung · 2026-08-05 19:22
on 132:5 "01 · Results — default" FRAME
have hover states
annotation on 132:258 "Overview" FRAME
allow for collapsing panelsget_figma_comment_image — renders the layer a comment is pinned to. For when the
comment is spatial ("too much space here") and the words alone aren't enough, or when it's
pinned to a pasted screenshot whose layer name is something useless like image 21.
It only reads. It never writes to Figma, edits your designs, or posts replies.
Two behaviours worth knowing:
A frame link reads only that frame. Any Figma URL copied with a frame selected carries
?node-id=, and the tool scopes to it — including everything nested inside, excluding the section around it. It always reports how many threads it left out. Passscope: "file"for the whole file.Annotations are not comments. Dev Mode annotations are a separate Figma feature, invisible to the comments API, and easy to forget you left. Both counts are on the headline so a frame never looks emptier than it is.
Related MCP server: figma-unified-mcp
Setup
Node 20 or newer.
1. Clone and build
git clone https://github.com/ejun-9/figma-comments-mcp.git
cd figma-comments-mcp
npm install
npm run buildThe client runs dist/, not src/, so the build isn't optional.
2. Make a Figma token
Figma → your avatar → Settings → Security → Personal access tokens → Generate new token.
You need two scopes, both read-only:
Scope | Set to |
File content | Read-only |
Comments | Read-only |
File content alone is the easy mistake — the server starts fine, resolves layer names fine, then returns a 403 the moment it asks for comments.
Copy the token when it's shown. Figma won't show it again.
3. Point your client at it
Claude Code:
claude mcp add figma-comments --env FIGMA_TOKEN=figd_your_token_here -- node /absolute/path/to/figma-comments-mcp/dist/index.jsClaude Desktop — edit ~/Library/Application Support/Claude/claude_desktop_config.json
(Windows: %APPDATA%\Claude\claude_desktop_config.json):
{
"mcpServers": {
"figma-comments": {
"command": "node",
"args": ["/absolute/path/to/figma-comments-mcp/dist/index.js"],
"env": { "FIGMA_TOKEN": "figd_your_token_here" }
}
}
}The path must be absolute — ~ won't resolve.
4. Restart the client
MCP servers are spawned once at launch. Editing the config or rebuilding dist/ does nothing
to a session that's already running. This catches everyone at least once.
5. Check it works
Before involving the client at all:
FIGMA_TOKEN=figd_your_token_here npm run try -- "https://figma.com/design/<key>/...?node-id=1-2"If that prints threads and your client shows nothing, the problem is the config or the restart — not the token.
Using it
Copy a link from Figma with the frame selected, and ask:
"Read the comments on https://figma.com/design/abc123/...?node-id=132-5 and apply them."
"What's still open across the whole file?"
"What did I annotate on this frame?"
Troubleshooting
What you see | What it is |
| Token is missing the Comments scope, or it expired. File content alone isn't enough. |
| Token works, but the account can't see this file. Check you can open it in the browser as the same user. |
| Wrong file key, or the file belongs to an org the token's account isn't in. |
| Figma rate limit. Wait and retry. |
| The client isn't passing the env var — it goes in the server's |
Server not listed in the client | Restart it. See step 4. |
Changes to |
|
| The |
Notes
TypeScript on
@modelcontextprotocol/serverv2, over stdio. Hits the Figma REST API withfetch— no SDK.Auth is the
X-Figma-Tokenheader.figd_tokens rejectAuthorization: Bearer, which is the first thing to check on a 401 or 403.Read-only endpoints used:
/v1/files/:key/comments,/v1/files/:key/nodes,/v1/files/:key,/v1/images/:key.Built with Claude.
License
ISC.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- -licenseNot gradedqualityNot gradedmaintenanceA Model Context Protocol (MCP) server that enables Claude to create and manipulate designs in Figma through either a Figma plugin or directly via the Figma API.
- AlicenseCqualityCmaintenanceA comprehensive MCP server that enables Claude to read, create, edit, and generate code from Figma designs. Supports design tokens, code generation to multiple frameworks, and accessibility checks.1003MIT
- AlicenseNot gradedqualityBmaintenanceA lightweight MCP server that adds Figma Comments support to AI assistants, enabling reading, querying, and replying to comments via the Figma REST API.14MIT
- FlicenseNot gradedqualityBmaintenanceAn MCP server that bridges Claude Code to Figma, enabling AI-driven design creation, modification, and export via semantic tools and WebSocket communication.
Related MCP Connectors
The Figma MCP server brings Figma design context directly into your AI workflow.
Augments MCP Server - A comprehensive framework documentation provider for Claude Code
Hosted MCP server connecting claude.ai, ChatGPT and other AI apps to your own computer
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ejun-9/figma-comments-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server