tr-figma-mcpserver
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FIGMA_ACCESS_TOKEN | Yes | Your Figma personal access token (format: figd_...) |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| download_figma_imagesA | Download images from Figma designs using access token and file URL. Supports both /file/ and /design/ URL formats with node-id parameters. |
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 1 tool
There is only one tool, so there is no ambiguity or overlap with other tools. The tool's purpose is clearly defined in its description.
The single tool name follows a consistent verb_noun pattern (download_figma_images). With only one tool, the naming convention is trivially uniform.
One tool feels thin for a server named 'tr-figma-mcpserver', which implies a broader Figma integration. The count is borderline because the tool may be intentionally scoped to image downloads, but the server name suggests more capability is expected.
The tool only covers downloading images from Figma designs. Missing operations such as fetching file metadata, listing nodes, or exporting assets create significant gaps that would cause agent failures for any non-trivial Figma workflow.