Skip to main content
iansev
iansev
New Member
April 1, 2026
Question

Feature Request: Figma MCP Support for Comments

  • April 1, 2026
  • 16 replies
  • 1098 views

Request: Through the Figma MCP, access contents of comments made in Figma Design file.

Reason: Can provide context for designs, review bugs, etc.

Current response from OpenAI Codex with direct link to comment:

No, not the comment itself.

What I can see from that link is the node it points to:

file: XXXXXX
node: XXXXXX
screen: /sign-up-2 (iOS)
That screen contains:

nav title Sign Up
Email and Password inputs
Sign Up primary CTA
Continue with Apple
Continue with Google
divider Or
Already have an account? Sign in
bottom legal links
But I still cannot read the actual Figma comment thread or the #XXXXXX anchor content from this session.

If you want, paste the comment text here and I can map it to this exact screen and tell you what change it implies.

 

    16 replies

    Show previous replies
    Josh Bromberg
    Josh Bromberg
    New Member
    July 13, 2026

    This is the design equivalent of reviews on a pr, feels like a requirement for truly adopting agents in our design workflow. Can’t really go as deep with figma in our internal workflows as we’d like without it.

    Jeffrey Turnock
    Jeffrey Turnock
    New Member
    July 14, 2026

    Codex just rolled out the ability to leave comments directly on websites while they are being built and have the agent action them. Notion has had this capability for months. Vendors across industries are giving agents ways to access data and feedback from human reviewers

    Allowing agents to see and action comments from humans has become a table-stakes feature and I was genuinely surprised that Figma doesn’t support this yet.

      David Hawkins
      David Hawkins
      New Member
      August 3, 2026

      Any movement on this? Miro can do this, i’ll probably switch to them if this doesn’t ship soon. 

      Teo Maragkakis
      Teo Maragkakis
      New Member
      August 25, 2026

      Any movement on this? Miro can do this, i’ll probably switch to them if this doesn’t ship soon. 

      Also Microsoft Word can do this, maybe switch to that.

      On a more serious note, this would be very useful as we use comments to mark open tasks. Comments should be exposed from all files in the account. I use daily briefs with Claude to see what needs to be done and accessing a list of new and resolved comments would help a lot.

      kubaguzik
      kubaguzik
      New Member
      September 9, 2026

      +1 from a design studio using Claude Code with the Figma MCP daily. What we need is not only the comment text but also what the pin is attached to (node_id / node_offset, the same data the REST comments endpoint already returns), plus resolved state and replies.

      Without it the agent can see the frame but has no idea what the client asked to change. Right now we work around it with a personal access token and GET /v1/files/:key/comments, which means a second auth path next to the MCP OAuth.

      Scott Hildebrand
      Scott Hildebrand
      New Member
      September 11, 2026

      Still nothing in the official MCP, but I've been running a workaround for a couple of months and it's solid enough to share: https://github.com/klezmer41/figma-review-loop

      It goes over the REST API rather than MCP (comments are readable there, just not exposed to agents). A small script plus a Claude Code skill... no server.

      Day to day it's: comment in Figma, tag @claude, then tell Claude Code "catch up on Figma comments." It covers a few things this thread asked for:

      • Reads comments, resolves the pinned node, renders the frame.
      • Acts and replies in-thread — "read my comments and apply the edits" works, with design edits going through use_figma and code edits through Claude Code.
      • Tracks thread state so you're not sifting: new / follow-up / answered / resolved. Follow-up means a human replied after the agent did — that's the one that matters and the one that's easy to lose.
      • Uses emoji reactions for "seen, nothing to change," as someone suggested above.

       

      Setup takes about ten minutes:

      1. Create an email address for Claude. A plus-address (you+claude@gmail.com) is enough; it lands in your own inbox.
      2. Sign up on figma.com with it, and share your file with that account as a Viewer. Viewers can comment.
      3. Generate a personal access token on each account — yours for reading, Claude's for replying — and put them in two env vars.

       

      Or skip the list — install it and tell Claude Code "help me set up figma-review-loop." It checks what's missing and walks you through the rest.

      Replies then show up as Claude, and you get notified like you would for anyone else. It works without the second account too, but then replies post as you (badged [@claude]), and Figma suppresses notifications for your own comments, so you never see them land.

      On a shared file it only acts on your own comments by default; others' are reported but not run, since that's their text executing under your credentials.

      Claude Code only. No Dev Mode annotations. Not a substitute for Figma doing this properly — but it closes the gap today.

      Terms & ConditionsAccessibility statement