figmma
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_current_userA | See who you're authenticated as in Figma. The user profile is fetched automatically at startup, so this is a quick cached lookup. |
| parse_figma_urlA | Extract the file key, file name, and node ID from a Figma URL. Use this when a user provides a Figma link instead of a raw file key. |
| list_team_projectsA | List all projects in a Figma team. If no team_id is provided, uses the configured default. |
| list_project_filesA | List all files in a Figma project. Use list_team_projects first to find project IDs. |
| get_file_infoA | Get metadata about a Figma file (name, last modified, version) without downloading the full document. Accepts a file key or a Figma URL. |
| search_projectsA | Search for Figma files by name across all projects in a team. If no team_id is provided, uses the configured default. |
| get_file_commentsA | Retrieve all comments on a Figma file. Shows who commented, when, the message content, and whether the comment is resolved. Accepts a file key or a Figma URL. |
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 7 tools
Most tools are distinct: get_current_user, parse_figma_url, get_file_info, and get_file_comments have clear separate purposes. However, list_project_files and search_projects both retrieve files and could cause confusion, especially since search_projects is misnamed (it searches files, not projects). The overlap is manageable with careful descriptions.
The naming pattern is mostly consistent with verb_noun (e.g., get_current_user, list_team_projects, get_file_comments). The exception is search_projects, which uses a verb but the noun does not match its actual function (searching files, not projects). This deviation slightly undermines predictability.
With 7 tools, the server is well-scoped. It covers auth, URL handling, navigation, metadata retrieval, and comments without being overwhelming. Each tool serves a clear purpose and the count is within the ideal 3-15 range for a focused integration.
The tool surface is heavily read-only and misses core Figma operations. There is no way to fetch actual design content (nodes, layers, styles) or export images, which are essential for a design tool. Additionally, there are no create, update, or delete operations, leaving the server limited to metadata and comment retrieval.