figmad-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FIGMA_ACCESS_TOKEN | Yes | Figma Personal Access Token used to authenticate with the Figma REST API. |
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_fileA | Get a Figma file structure and metadata. Returns the document tree, components, and styles. |
| get_nodeA | Get specific nodes from a Figma file by their IDs. More efficient than getting the full file when you know what nodes you need. |
| get_componentsA | List all components in a Figma file. Returns component keys, names, and descriptions. |
| get_stylesB | Get all styles (colors, text styles, effects, grids) from a Figma file. |
| get_variablesB | Get design tokens/variables from a Figma file. Includes colors, spacing, and other tokenized values. |
| export_imageA | Export a Figma node as an image (PNG, JPG, SVG, or PDF). Returns a URL to the exported image. |
| create_frameB | Create a new frame in Figma. Frames are the primary container for designs. Requires the Figma plugin to be connected. |
| create_rectangleB | Create a rectangle shape in Figma. Can have fills and rounded corners. |
| create_textB | Create a text node in Figma. Supports font customization and alignment. |
| update_nodeB | Update properties of an existing Figma node. Can modify position, size, text, visibility, and more. |
| apply_auto_layoutB | Apply auto-layout to a frame. Auto-layout automatically arranges children horizontally or vertically with consistent spacing. |
| set_fillsA | Set fill colors/gradients on a node. Replaces all existing fills. |
| delete_nodeB | Delete a node from the Figma document. |
| get_selectionA | Get the currently selected nodes in Figma. |
| capture_webpageA | Capture a webpage screenshot and analyze its DOM structure. Detects UI components like buttons, inputs, cards, navigation. Returns capture ID for use with reconstruct_page. |
| reconstruct_pageA | Reconstruct a captured webpage in Figma. Creates frames, shapes, and text based on the captured DOM structure. Requires capture_webpage to be called first. |
| generate_uiB | Generate a UI design from a text description. Parses the prompt for common UI patterns (header, hero, cards, form, footer) and creates corresponding Figma elements. |
| analyze_codebaseB | Analyze a codebase to extract component definitions, props, and design tokens. Supports React, Vue, Svelte, Angular. Extracts Tailwind config and CSS variables. |
| sync_design_tokensB | Compare and sync design tokens between Figma and code. Can extract tokens from Figma variables/styles or from codebase analysis. |
| plugin_statusA | Check if the Figma plugin is connected. Write operations require the plugin. |
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 20 tools
Most tools have distinct purposes, such as create_frame, create_rectangle, and create_text for different element types, and get_file, get_node, and get_selection for different retrieval methods. However, some overlap exists between analyze_codebase and sync_design_tokens, as both involve code analysis and design tokens, which could cause mild confusion.
Tool names follow a consistent verb_noun pattern throughout, such as create_frame, delete_node, export_image, get_components, and update_node. There are no deviations in naming conventions, making the set predictable and readable.
With 20 tools, the count is slightly high but reasonable for a Figma MCP server covering design operations, code analysis, and webpage capture. It includes core CRUD actions and specialized functions without feeling excessively bloated, though it borders on the upper limit of typical scope.
The tool set provides comprehensive coverage for Figma design workflows, including creation (e.g., create_frame, create_text), retrieval (e.g., get_file, get_node), updates (update_node), deletion (delete_node), export (export_image), and integration with codebases and webpages. No obvious gaps are present, supporting full lifecycle operations.