Figma MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FIGMA_ACCESS_TOKEN | Yes | Your Figma access token |
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: adding files, posting comments, reading comments, replying to comments, and viewing nodes. There is no overlap in functionality, making it easy for an agent to select the correct tool without confusion.
All tool names follow a consistent verb_noun pattern (e.g., add_figma_file, post_comment, read_comments, reply_to_comment, view_node). This uniformity enhances readability and predictability for agents.
With 5 tools, the server is well-scoped for its purpose of managing Figma files and comments. Each tool serves a specific, necessary function without bloat or redundancy.
The toolset covers core operations for file management and comment interactions, but lacks CRUD coverage for files (e.g., no update or delete file tools). However, agents can likely work around this minor gap for basic workflows.