figma
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FIGMA_TOKEN | Yes | Figma personal access token with read-only access to file content (Settings → Security → Personal access tokens). Set it in .env after FIGMA_TOKEN=. Only needed the first time a file is read; once a file is cached, the server runs without it. |
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
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": false,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_framesB | The frames in a Figma file (page, id, name, size). Start here, then pass a frame id to the other tools. |
| get_layoutB | One frame as a compact layout tree: auto layout as flexbox (direction, gap, padding, justify, align), text with its font, colours as hex, sizes in px. Build the page from this. |
| get_tokensC | The file's colour and text styles as CSS custom properties, for :root. |
| export_iconsC | Every icon in the frame as inline SVG, keyed by the icon's name. Paste them into the page as-is. |
| render_frameC | A picture of the frame (PNG), so you can see the design you're building and compare against it. |
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
Each tool has a clearly distinct role in a design-to-code pipeline: list frames, extract layout, extract tokens, export icons, and render a preview. The descriptions explicitly sequence them, with list_frames as the entry point and frame id passed to the others.
All names follow a consistent verb_noun snake_case pattern: list_frames, get_layout, get_tokens, export_icons, render_frame. The convention is predictable and easy to scan.
Five tools is well-scoped for a focused Figma extraction server. Each tool earns its place by covering a distinct artifact needed to build a page from a design.
The surface covers the core workflow: discover frames, inspect layout, get design tokens, export icons, and visually compare via render. Minor gaps exist for other asset types or broader file-level operations, but the main build path is complete.