# Act on review comments left on a design

> Act on review comments left on a design: 1 companies fully do it, 7 with a limit, 16 carry the tag. Every listing in Design workspaces & canvases with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/design.review-comments/
- Markdown: https://www.anchorterminal.com/niches/design.review-comments/index.md (~1,200 tokens)
- Slim: https://www.anchorterminal.com/niches/design.review-comments/index.min.md (~280 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/design.review-comments/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

One company's docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 1 | 7 | 16 | 4 | 1 |

## What counts as done

Each open thread on the named file read with the node it is pinned to, the change made, and a reply posted on that thread, with comment text treated as data.

How agents ask for it: address the comments on this file; reply to the design feedback; what did the reviewer ask for on this frame

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **Kite (Kite)**: comment_list reads threads with the frame each is on, request_list finds @-mentions, comment_reply answers in the thread, and layer_edit makes the change.

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **Figma API + MCP (Figma, Inc.)**: MCP has no comment tools. The REST API lists comments, posts replies to root comments with client_meta positions, and deletes, but has no resolve call, so the agent needs a second credential.
- **Melius (Melius AI, Inc.)**: comment_list, comment_reply and comment_resolve exist, but threads are created at a canvas position and the docs don't say a listed comment names the node it sits on.
- **Miro API + MCP (RealtimeBoard Inc. dba Miro)**: comment_list_comments reads comments for a board or item, with reply and resolve, and canvas_update_from_svg makes the change. Board comments are a whiteboard's, not a design file's, and no prompt-injection guidance is given.
- **Penpot API + MCP (Kaleidos Subsidiary SL)**: The plugin API behind execute_code has findCommentThreads, the board a thread is attached to, reply and a resolved flag, so threads can be handled. Whether the MCP plugin holds comment permissions is not stated.
- **Subframe (Atomic Design Inc)**: list_comments returns open threads with the element id they sit on, so edit_page can act on them, but replying and resolving happen only in the Subframe app.
- **UX Pilot MCP server (UX Pilot)**: read returns comments and manage replies and resolves them, with version_from_comments to apply feedback. Whether a comment carries the element it is pinned to isn't stated.
- **Zeplin (Zeplin, Inc.)**: Screen notes with positions and their comments can be listed, created and updated through REST, but notes are pinned to screen coordinates, not layers, and the design itself can't be changed in Zeplin.

## Couldn't check

The docs were closed to us, or silent. These carry no mark either way.

- **Sketch (Sketch B.V.)**: Sketch has document comments, but no MCP tool for them is listed and the docs don't say whether SketchAPI through run_code reaches them.

- not this job: ArtCraft (Storyteller): No comments.
- not this job: Framelink MCP for Figma (Framelink (Graham Lipsman)): No comment tool; only design data and images.
- not this job: Framer Server API (Framer B.V.): No comment reading or replying is described for MCP or the Server API.
- not this job: Impeccable (Renaissance Geek, Inc.): No design-file comments.
- not this job: Magic Patterns (North Park Labs, Inc.): No comment tools in the MCP tool list.
- not this job: pen.dev (High Agency, Inc.): MCP exposes no comments; acc-23 is open asking for it.
- not this job: Presentations.AI MCP server (Presentations.AI): No comment tools.
- not this job: UXKIN (UXKIN (no legal entity named)): No comment tools.

## What stops agents finishing

- comments stored server-side and not exposed to the agent

## Around it

Before: design.edit-canvas. After: design.edit-canvas.

## Where this comes from

Weight 4 of 100 in Design workspaces & canvases: 1 of 42 accounts (pen.dev issue) plus vendor pages for Kite @-mentions and Figma get_comments; weight is a guess

As data: https://www.anchorterminal.com/api/v1/use-cases/design.review-comments.json, or the MCP tool get_use_case with id design.review-comments. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
