Figma Comments MCP
Related Servers
Alternatives to Figma Comments MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to read every comment and reply in a Figma file—including authors, timestamps, resolution state, and pin metadata—and to post new comments, threaded replies, or frame-pinned comments via the official Figma REST API. It authenticates locally with a personal access token and never alters or deletes designs.MIT
- AlicenseNot gradedqualityCmaintenanceEnables reading and acting on comments in Figma and FigJam, resolving which layer each comment is pinned to, complementing the official Figma MCP server.10MIT
- AlicenseAqualityDmaintenanceMCP server that fetches and replies to Figma file comments, with filtering and a triage skill to organize them into decisions, questions, and to-dos.5MIT
- AlicenseNot gradedqualityBmaintenanceEnables agents to subscribe to comments in selected Figma files, pages, frames, folders, teams, or organizations, optionally filtered by tag, and retrieve new comment events over MCP stdio. It polls Figma's REST API locally so the receiving agent can decide how to react.5 npmMIT
- AlicenseAqualityDmaintenanceEnables interaction with the Figma API through MCP tools for managing files, projects, and comments, plus a real-time observability dashboard.75 npm2ISC
- FlicenseNot gradedqualityDmaintenanceCustom MCP server for the Figma REST API that enables inspecting file structures, nodes, styles, components, variables, and exporting images, with optional comment posting. It is read-only except for posting comments and is designed for use with Claude Code.-
TDQS
Scored across 8 tools
Most tools map cleanly to distinct comment actions: list, get thread, post, reply, delete, and reactions. The only likely confusion is figma_delete_comment versus figma_delete_comments, though the descriptions clarify single-ID deletion versus explicit bulk deletion.
All tools use a consistent figma_ prefix followed by clear snake_case verb_noun or verb_noun_object patterns. The naming is predictable and readable throughout.
Eight tools are well-scoped for a Figma comments server, covering reading, writing, deletion, and reactions without excessive surface area.
The surface covers the main comment lifecycle: list threads, read threads, post top-level comments, reply, delete individually or in bulk, and manage reactions. Minor gaps include no explicit edit/update operation and no resolve/unresolve tool, though these may reflect Figma API limitations.