Figma Export MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FIGMA_TOKEN | Yes | Figma API token used to authenticate with the Figma REST API. | |
| YANDEX_DISK_TOKEN | Yes | Yandex Disk OAuth token used to upload and manage files on Yandex Disk. |
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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_connectionsA | Checks configuration and reachability without returning secrets. |
| inspect_figma_fileB | Creates or reuses a versioned normalized read-only snapshot and returns a compact summary. |
| analyze_figma_layoutC | Detects adaptive row/column geometry and reports heuristic evidence, confidence, anomalies and samples. |
| query_nodesC | Applies declarative logical selectors without rendering and returns a paginated evidence set. |
| create_export_planC | Materializes selection, ordering, variables, names and paths. Never renders or uploads. |
| preview_export_planA | Returns stable count/order/naming/destination/warnings plus a page of the manifest without bulk render. |
| confirm_export_planA | Unlocks only the exact digest after explicit user approval; rejects unresolved clarifications and changed Figma versions. |
| execute_export_planA | Starts an idempotent background export/upload/verify job and quickly returns its job ID. |
| get_export_statusB | Returns stage totals, safe errors, retry state, verified paths and paginated events. |
| retry_failed_itemsA | Retries only failed/retryable items and never reuploads verified items. |
| verify_yandex_uploadA | Rechecks every expected path, size and comparable checksum without uploading. |
| cleanup_jobA | Deletes local temporary data only after verification, or after explicit risk confirmation for incomplete jobs. |
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 12 tools
Most tools have clearly distinct purposes, especially the phased export plan tools. The only mild ambiguity is among inspect_figma_file, analyze_figma_layout, and query_nodes, though their descriptions separate snapshotting, layout analysis, and node selection well enough.
Tool names consistently follow a consistent verb_noun snake_case pattern (create, preview, confirm, execute, get, retry, verify, cleanup). Names read predictably and map directly to their actions. No naming convention clashes exist.
Twelve tools is well-scoped for a focused export/export-verification workflow. Each tool occupies a meaningful stage from planning to cleanup without redundancy. The count feels intentional rather than padded.
The set covers the full lifecycle: connection checks, inspection, planning, preview, confirmation, execution, status, retry, verification, and cleanup. An explicit cancel/abort operation for running jobs is a minor gap, but agents can still manage the workflow through status, retry, and cleanup.