Figma Codex Bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FIGMA_LOCAL_MCP_PORT | No | The port for the local bridge. | 38455 |
| FIGMA_LOCAL_MCP_TOKEN | Yes | The shared authentication token between the MCP server and the Figma plugin. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| figma_statusA | Check whether the local Figma Desktop plugin is connected and report the active file/page. |
| figma_get_file_metadataA | Read metadata for the Figma file currently open in Figma Desktop. |
| figma_get_page_structureB | Read the top-level nodes on a Figma page. Defaults to the current page. |
| figma_get_selectionB | Read the current Figma selection, including layout, text, fills, and a bounded child tree. |
| figma_get_nodeB | Read one Figma node by ID, including its bounded child tree. |
| figma_get_design_contextA | Build an implementation-ready context pack for the current selection or a Figma node, including bounded structure, tokens, components, variables, styles, assets, and an optional screenshot. |
| figma_get_screenshotA | Export the current selection or a Figma node as a PNG image for visual comparison. |
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 7 tools
Each tool targets a distinct aspect: status, metadata, page structure, selection, node, context, screenshot. Some overlap exists between get_selection and get_node, but ID-based vs current selection keeps boundaries clear.
All tools share the figma_ prefix and most use the get_ verb, but figma_status breaks the verb_noun pattern. The naming remains predictable and readable overall.
Seven tools is well-scoped for a design-to-code bridge, covering status, metadata, page structure, selection, node access, context packing, and screenshots without unnecessary bloat.
The set covers all read-oriented needs for extracting design context: file info, page hierarchy, node access, selection, comprehensive context with tokens/styles/assets, and screenshots. No obvious gaps for a read-only bridge.