Help us improve
Share bugs, ideas, or general feedback.
Read, post, reply to, and delete comments on a Figma file via the REST API, including pinning to a node and threading replies. Requires a personal access token.
npx claudepluginhub southleft/figma-console-mcp-skills --plugin figma-console-mcp-skillsHow this skill is triggered — by the user, by Claude, or both
Slash command
/figma-console-mcp-skills:figma-commentsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Comments live only in Figma's **REST API** — the Plugin API (`use_figma`) and the native Figma MCP
Handles Figma Comments and Version History APIs via TypeScript fetch calls. Manages user data privacy with GDPR/CCPA compliance and redaction.
Posts generated design behavior questions as pinned comments on Figma frames using node IDs, file keys, and positioning from manifest.json. Used after generate-behavior-questions when user confirms posting.
Automates Figma tasks via Rube MCP/Composio: inspect files/nodes/components, extract design tokens/comments, export/render images. Use for design data extraction in code workflows.
Share bugs, ideas, or general feedback.
Comments live only in Figma's REST API — the Plugin API (use_figma) and the native Figma MCP
can't touch them. This skill reads comment threads, posts new comments (optionally pinned to a node),
replies to existing threads, and deletes comments.
Setup — terminal + token required. This skill runs shell commands, so it works in Claude Code (including the "Code" tab inside Claude Desktop), Cursor, Codex, or Gemini CLI — it does not run in plain Claude Desktop or claude.ai chat (no shell). The Figma connector's OAuth login does not authorize these REST calls, so you must supply your own Figma personal access token: in Figma go to Settings → Security → Personal access tokens, generate one with scope File content: read (plus Comments: read/write), then set it in your shell:
export FIGMA_TOKEN="figd_…". The script reads it from the environment at runtime — never put the token in a skill file.
X-Figma-Token: $FIGMA_TOKEN against https://api.figma.com.@mentions are a Figma UI-only feature. Putting @name in a message renders as plain text,
not a clickable mention, and does not trigger a Figma notification.FILE_KEY=$(echo "$FILE_URL" | sed -E 's#.*/(design|file)/([A-Za-z0-9]+).*#\2#')
scripts/get-comments.sh lists threads with author, message, timestamps,
pinned node, and resolution state. Resolved threads are filtered out by default:
./scripts/get-comments.sh ABC123def456 # active comments only
./scripts/get-comments.sh ABC123def456 --include-resolved
./scripts/get-comments.sh ABC123def456 --md # request markdown message bodies
Raw endpoint:
curl -s -H "X-Figma-Token: $FIGMA_TOKEN" \
"https://api.figma.com/v1/files/ABC123def456/comments?as_md=true"
scripts/post-comment.sh posts a top-level comment, a node-pinned
comment, or a threaded reply:
# Plain file-level comment
./scripts/post-comment.sh ABC123def456 "Heads up: the button radius drifted from code."
# Pinned to a node (appears on that element). x/y default to 0,0 if omitted.
./scripts/post-comment.sh ABC123def456 "Padding here should be 16, not 12." --node 695:313 --x 40 --y 12
# Reply to an existing thread (get IDs from get-comments.sh)
./scripts/post-comment.sh ABC123def456 "Fixed in the latest sync." --reply 123456789
The raw POST body shape:
curl -s -X POST -H "X-Figma-Token: $FIGMA_TOKEN" -H "Content-Type: application/json" \
-d '{"message":"Pinned note","client_meta":{"node_id":"695:313","node_offset":{"x":0,"y":0}}}' \
"https://api.figma.com/v1/files/ABC123def456/comments"
client_meta with node_id and a node_offset ({x,y} relative to the
node). Figma requires node_offset whenever node_id is present — the script defaults it to
(0,0).comment_id (the id of the comment you're replying to) to the body. The script's
--reply flag does this. Replies form a thread under the original comment.scripts/delete-comment.sh removes a comment by id (find ids via
get-comments.sh):
./scripts/delete-comment.sh ABC123def456 123456789
Raw:
curl -s -X DELETE -H "X-Figma-Token: $FIGMA_TOKEN" \
"https://api.figma.com/v1/files/ABC123def456/comments/123456789"
403 on post/delete means your PAT lacks Comments: Read and write — reissue the token.post-comment.sh --node <id> to leave an
actionable note pinned to the offending element so designers see it in context.