Figma Live Design QA MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FIGMA_TOKEN | Yes | Figma personal access token with File content: read permission. | |
| DESIGN_QA_HOME | No | Custom base directory for run data (default: ~/.figma-live-design-qa-mcp/). | |
| DESIGN_QA_REPORT_DIR | No | Custom directory for reports (default: ~/Documents/Design QA/). |
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 |
|---|---|
| run_design_qaA | End-to-end design QA: measures a Figma frame and a live page, then writes an HTML report. Give it a Figma frame link and the URL of the built page. Runs capture_design, capture_build, check_tokens and build_report in sequence. On failure it returns the runId so the remaining steps can be run individually. |
| capture_designA | Fetch a Figma frame and derive its design token set. Accepts a pasted Figma frame link or a bare file key plus nodeId. Writes the flattened node list to disk and returns a runId. Never returns the node tree. |
| capture_buildA | Measure the live page in the user's own browser session, piercing shadow DOM and same-origin iframes. Reuses a running Chrome over CDP, else a copy of the Chrome profile. Never asks for or stores credentials. Viewport width defaults to the Figma frame width from the same run. |
| check_tokensA | Compare every colour, font size, font weight and border radius in the build against the design token set. Returns findings grouped by value, capped at 50, with severities. Dimensions where no token set could be inferred are reported as "not verified" rather than guessed at. |
| build_reportA | Write a self-contained HTML report with all images inlined, plus report.json. Opens offline and can be shared directly. Returns the absolute path. |
| dismiss_findingC | Add a finding to the baseline for its Figma file so it is suppressed on all future runs. |
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 6 tools
Each tool has a distinct role: orchestration, capturing design, capturing build, comparing, reporting, and managing baselines. No overlap in purpose.
All tool names follow a consistent verb_noun pattern in lowercase with underscores, making them predictable and easy to understand.
6 tools is well-scoped for an end-to-end design QA workflow, covering all necessary steps without unnecessary redundancy.
The tool set covers the full lifecycle: capture design, capture build, compare tokens, generate report, and dismiss findings. No obvious gaps for the stated purpose.