mcp-figma
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 |
|---|---|
| set_api_keyA | Set your Figma API personal access token (will be saved to ~/.mcp-figma/config.json) |
| check_api_keyA | Check if a Figma API key is already configured |
| get_fileC | Get a Figma file by key |
| get_file_nodesC | Get specific nodes from a Figma file |
| get_imageC | Get images for nodes in a Figma file |
| get_image_fillsC | Get URLs for images used in a Figma file |
| get_commentsC | Get comments on a Figma file |
| post_commentC | Post a comment on a Figma file |
| delete_commentC | Delete a comment from a Figma file |
| get_team_projectsC | Get projects for a team |
| get_project_filesC | Get files for a project |
| get_team_componentsC | Get components for a team |
| get_file_componentsC | Get components from a file |
| get_componentC | Get a component by key |
| get_team_component_setsC | Get component sets for a team |
| get_team_stylesC | Get styles for a team |
| get_file_stylesC | Get styles from a file |
| get_styleC | Get a style by key |
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 18 tools
Most tools have distinct purposes targeting specific Figma resources like files, comments, components, styles, and images. However, get_file_nodes and get_image_fills could potentially overlap in purpose since both deal with retrieving node-related data, though their descriptions clarify different focuses (nodes vs. image fills).
All tool names follow a consistent verb_noun pattern using snake_case, with clear actions like get, post, delete, set, and check. This uniformity makes the toolset predictable and easy for an agent to navigate without confusion.
With 18 tools, the count is slightly high but reasonable for a Figma API server that needs to cover multiple resource types (files, comments, components, styles, images, projects, teams). It avoids being overwhelming while providing comprehensive functionality, though it could be trimmed slightly for tighter scoping.
The toolset offers complete coverage for core Figma operations, including CRUD for comments (get, post, delete), retrieval for files, components, styles, images, projects, and teams, and configuration for API keys. There are no obvious gaps, and agents can perform typical workflows without dead ends.