Figma MCP Bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| figma_get_contextB | Состояние моста и доступного документа. Не требует сессии. |
| figma_get_treeC | Ограниченное дерево узлов текущей сессии. |
| figma_find_nodesC | Поиск узлов в явно заданной области текущего документа. |
| figma_get_nodesC | Чтение запрошенных свойств по nodeId. |
| figma_get_local_resourcesB | Чтение локальных компонентов, стилей и переменных. |
| figma_navigateC | Явный переход к узлам и изменение выделения. |
| figma_apply_batch | Пакет структурированных изменений с предусловиями и ссылками на предыдущие шаги. |
| figma_get_operationC | Чтение известного состояния операции без повторного исполнения. |
| figma_cancel_operationB | Запрос остановки операции без отката применённых изменений. |
| figma_export_nodeC | Экспорт выбранного узла в PNG или SVG. |
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 10 tools
The read tools are mostly separable by scope: get_tree returns structure, find_nodes searches a bounded region, get_nodes fetches properties by nodeId, and get_context reports bridge state. The main soft spot is the tree/nodes/find_nodes cluster plus get_operation vs get_context, which an agent could plausibly swap, but the descriptions do enough to steer selection.
All ten tools share a `figma_` prefix with a verb_noun pattern (get_tree, find_nodes, apply_batch, cancel_operation, export_node). The only deviation is `figma_navigate`, which drops the object noun, but the convention remains predictable overall.
Ten tools is a well-scoped surface for a Figma bridge: reads, search, navigation, batched mutation, operation lifecycle, and export. Each tool maps to a distinct capability without padding.
The surface covers discovery, reading, mutation via apply_batch with preconditions, operation polling/cancel, and PNG/SVG export, so core workflows are closed. Minor gaps: no rollback/undo for applied batches (cancel explicitly does not revert), no file/document switching, and export limited to two formats.