Figma Comments MCP

An MCP server for Claude Code that fetches comments from any Figma file link, plus a triage skill that sorts them into what the team needs to do: decisions, open questions, who's waiting on whom, and who owns each to-do.

Tools

The fetch tools take a figma.com link (or bare file key) and return threads grouped by the canvas element each comment is pinned to, with authors, replies, @mentions, age, the page it sits on, and a deep link back to the comment in Figma.

Output is deliberately compact to keep Claude's context cost low: resolved threads come back as a count only, messages are capped at 300 characters, and at most max_threads unresolved threads (default 50, newest first) are shown, with a note on how to narrow further. Deep links are built from one pattern in the header rather than repeated per thread.

Every fetch tool also accepts three optional narrowing arguments. In Claude Code, just say it: "unresolved comments on the Homepage page of ", "what has Sarah commented?", "any comments about the pricing table?".

• page — one page only, by name ("Homepage") or id ("1:2" / "1-2"). If the name doesn't match, the error lists the file's pages. Figma's comments API itself is file-wide, so comments are anchored via the page's top-level frames; in rare cases a comment pinned to a deeply nested element may not resolve to a page and only appears in unfiltered results.

• author — threads where this person wrote a message (partial, case-insensitive).

• search — threads whose text contains a keyword (case-insensitive).

reply_to_comment lets Claude answer a thread for you ("reply 'on it' to that one"). It posts as the token owner and only works if your token has the File comments (write) scope; with a read-only token the fetch tools still work and only replying fails.

Related MCP server: Talk to Figma MCP

Setup

1. Figma token. figma.com → Settings → Security → Personal access tokens. Create one with the File comments scope: read is enough for fetching, write if you also want reply_to_comment.

2. Save the token. Paste this in the terminal, replacing your-token-here with the token you copied:

   echo "FIGMA_TOKEN=your-token-here" > ~/.figma-comments-mcp.env

   That creates a small file in your home folder. The token stays on your machine and is only ever sent to Figma. When the token expires, repeat this step with a new one. (A FIGMA_TOKEN environment variable also works and takes precedence, if you prefer that.)

3. Register with Claude Code.

   claude mcp add figma-comments -- npx -y figma-comments-mcp

   Or, running from a clone of this repo:

   npm install
   npm run build
   claude mcp add figma-comments -- node /path/to/figma-comments-mcp/dist/server.js

4. Use it. In a Claude Code session:

   Triage the comments in https://www.figma.com/design/abc123/My-File

   The figma-comment-triage skill (in .claude/skills/) handles the sorting: decisions first (including when two people leave conflicting takes on the same element), then open questions with who they're waiting on, blocked threads, and to-dos with owners. Copy the skill folder into your own project's .claude/skills/ to get the same triage.

Quick manual check

Test the fetcher against a real file without going through MCP:

FIGMA_TOKEN=<your-token> npm run probe -- https://www.figma.com/design/abc123/My-File

Prints the token owner, thread counts, and the raw grouped JSON.

Project layout

src/
├── core/          # transport-agnostic: API client, threading, filters
│   ├── figma.ts
│   └── filters.ts
├── tools.ts       # MCP tool definitions (Figma client injected)
├── server.ts      # local stdio entry point (token from env)
└── probe.ts       # manual CLI check

core/ and tools.ts never touch env vars, the filesystem, or stdio. A future hosted version (Cloudflare Workers + Figma OAuth) only needs a new entry point next to server.ts.

A note from the maker

I'm a designer, and this is my first published developer tool. I built it because I kept opening Figma files to forty comment bubbles with no way to tell which ones actually needed me. It's been solid in my own daily use, but there may be rough edges I haven't hit yet. If something breaks or behaves oddly, open an issue and I'll take a look.

Licence

MIT