DriftCheck
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-only scope. Optional: leave empty or omit to use the Driftcheck Figma plugin without the Figma REST API. | |
| DRIFTCHECK_OUTPUT | No | Optional output folder for generated reports and images. Defaults to 'driftcheck' in the temp folder. | |
| DRIFTCHECK_EXPORTS | No | Optional folder where Driftcheck looks for Figma plugin exports. Defaults to Downloads. |
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
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| compare_screenA | Compares the app's current screen on the device (Android or iOS Simulator) with a Figma frame. Matches Figma layers to app elements by visible text, name = AutomationId or position, and reports differences in position, size, text and background color. Non-text layers (buttons, fields, lines, icons, images) are found in the screenshot by how they look, comparing box, fill, corner radius, border and content. Reports fidelity (% of elements as in Figma, and how much it changed since the previous comparison) and how to fix each difference with the framework's properties. Generates report.html (interactive report to show the user), side_by_side.png and diff.png (in diff.png: green = matches, orange = differs, dotted blue = where Figma says it should be). Open the images for a visual review. If the screenshot doesn't look like the design (a loading screen), it waits and captures again up to 3 times. |
| capture_screenA | Takes a screenshot of the device (Android or iOS Simulator) and lists the visible elements with their AutomationId (resource-id on Android, accessibilityIdentifier on iOS), text and bounds in dp or pt. On iOS it takes a few more seconds: it reads the accessibility tree with a UI test, which is built the first time. |
| list_devicesA | Lists the Android devices and emulators connected through adb and, on macOS, the booted iOS simulators. |
| get_design_specsA | Returns the measurements of the Figma frame: position, size, colors, texts and typography of every named layer. Use it BEFORE writing a screen's UI code. If deviceWidth is passed, values are scaled to that width in dp or pt. |
| import_designA | Imports a .driftcheck.json file exported with the Driftcheck plugin in Figma, to compare without the Figma API (no token or no quota). Exports in the Downloads folder are picked up on their own; this is for the ones that ended up in another folder. Then compare with the frame link, as usual. |
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 5 tools
Each tool has a clear primary purpose, but capture_screen and compare_screen could be mistaken at a glance since compare_screen internally captures and analyzes the screen. get_design_specs and import_design also both deal with Figma source data, though their descriptions clearly distinguish API vs offline export use.
All tools follow a consistent snake_case verb_noun pattern: list_devices, compare_screen, capture_screen, get_design_specs, import_design. No mixed conventions or vague standalone verbs.
Five tools is well-scoped for a visual design comparison server. Each tool covers a distinct step in the workflow: device discovery, screenshot capture, Figma spec retrieval, offline design import, and comparison.
The core workflow is covered: discover devices, get design specs or import design data, capture the current UI, and compare it against Figma with reports. Minor gaps exist around explicit device selection or app navigation/state control, but agents can likely work around these.