Figma MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
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.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_figma_fileC | Add a Figma file to your context |
| view_nodeC | Get a thumbnail for a specific node in a Figma file |
| read_commentsC | Get all comments on a Figma file |
| post_commentC | Post a comment on a node in a Figma file |
| reply_to_commentC | Reply to an existing comment in a Figma file |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose with no overlap: adding files, posting comments, reading comments, replying to comments, and viewing nodes. The descriptions make it easy to differentiate between file management, comment operations, and node inspection.
All tool names follow a consistent verb_noun pattern (e.g., add_figma_file, post_comment, read_comments, reply_to_comment, view_node) using snake_case throughout. This predictable naming scheme enhances readability and usability.
With 5 tools, this server is well-scoped for basic Figma interactions, covering file management, comment lifecycle, and node viewing. Each tool earns its place without feeling excessive or insufficient for the domain.
The toolset provides solid coverage for comment workflows (post, read, reply) and file/node basics, but lacks operations like updating or deleting comments, or more advanced file manipulations. Agents can work around these minor gaps for core tasks.