Schema | figma-comments-mcp

figma-comments-mcp

Describes the environment variables required to run the server.

Name	Required	Description	Default
`FIGMA_TOKEN`	Yes	Figma personal access token with File comments scope

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": true }

Functions exposed to the LLM to take actions

Name	Description
get_all_commentsA	Fetch every comment thread in a Figma file, grouped by page and the canvas element each thread is pinned to. Resolved threads are returned as a count only. Prefer a narrower tool (unresolved/recent/mentions, or the page argument) when it answers the question.
get_unresolved_commentsC	Comment threads not yet marked resolved in Figma.
get_comments_mentioning_meB	Comment threads where the owner of the Figma token is @mentioned.
get_recent_commentsC	Comment threads with activity in the past N hours (default 24).
reply_to_commentA	Post a reply to an existing comment thread in a Figma file. Use a thread id from the [brackets] in fetch output as comment_id. Requires the Figma token to have the File comments write scope.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/processedfood/figma-comments-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server