YetAnotherFigmaMCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FIGMA_API_TOKEN | Yes | Figma API token. Obtain from Figma settings page. |
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": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_cached_figma_fileA | Get cached Figma file metadata and top-level frames. Returns file name, version, last modified date, and a list of main frames. Use this tool first to understand the structure of a Figma file. |
| get_cached_figma_nodeA | Get detailed information for a specific node including all properties (type, name, layout, style, children, etc.). Use this after finding a node ID via search or list_figma_frames. Use 'depth' to limit children depth, 'simplified' for AI-optimized output. |
| search_figma_nodes_by_nameA | Search nodes by name. Supports exact and partial matching. Returns matching nodes with their IDs, types, and paths. Useful for finding specific components, buttons, icons, etc. |
| search_figma_frames_by_titleA | Search frame nodes by title. Useful for finding specific screens, pages, or components. Returns matching frames with their IDs and paths. |
| list_figma_framesA | List all top-level frames in the file (including frames inside sections). Useful for getting an overview of the design structure. Returns frame names, IDs, and their paths in the document hierarchy. |
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
Tools are mostly distinct, but list_figma_frames and get_cached_figma_file both return frame lists, which could cause confusion. Search nodes by name and search frames by title also overlap, though descriptions clarify the scope difference.
All tools follow a consistent <verb>_figma_<resource> pattern, using get for single resources, search/list for plural collections, and qualifiers like by_name or by_title for searches. This makes the set predictable and easy to navigate.
Five tools is a well-scoped size for a read-only Figma caching server, covering file metadata, frame enumeration, node search, and node detail retrieval without unnecessary bloat.
The toolkit covers the core exploration workflow: get file → list frames → search nodes → get node details. Minor gaps exist, such as no direct asset export or style querying, but the stated purpose is served without dead ends.