Context Figma MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FIGMA_TOKEN | No | Figma personal access token with `file_content:read` permission. Required for normal mode to access the live Figma API. | |
| FIGMA_FIXTURE_PATH | No | Path to a synthetic Figma REST-shaped JSON fixture for offline mode. When set, the server serves the local fixture instead of live data and does not require FIGMA_TOKEN. Never set in production. |
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_prototype_flowsB | List explicit Figma prototype flow starting points and their pages. Read-only. |
| get_prototype_graphA | Get explicit Figma prototype interactions and navigation as a provenance-aware graph; optionally limit to nodes reachable from a flow/screen. Does not infer missing links. |
| get_screen_interactionsB | Get triggers, actions, conditions and resolved destinations for one Figma screen. No AI inference. |
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 3 tools
The three tools target distinct granularities: single screen, flow starting points, and global graph. However, get_screen_interactions and get_prototype_graph (when limited to a screen) can both return screen-level interactions, creating minor overlap that descriptions mostly resolve.
All tools use the get_ prefix followed by a snake_case noun phrase (get_screen_interactions, get_prototype_flows, get_prototype_graph), a consistent verb_noun pattern throughout.
Three tools is well-scoped for a focused, read-only prototype-context server. Each tool covers a distinct retrieval need (per-screen details, flow list, navigation graph) without redundancy.
The set covers screen interactions, flow origins, and the full navigation graph, which is complete for read-only prototype context. A minor gap exists for retrieving interactions of arbitrary nodes not tied to a screen or flow, but core workflows are covered.