Figma Context MCP
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.
Description from the maker (original English)
Compares a mobile app screen (Android or iOS Simulator) with its Figma design and suggests fixes.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
FIGMA_TOKEN, DRIFTCHECK_OUTPUT, DRIFTCHECK_EXPORTSValues marked secret are keys to your account. Never share them or paste them into a chat.
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"driftcheck": {
"command": "dnx",
"args": [
"Driftcheck",
"--yes"
],
"env": {
"FIGMA_TOKEN": "your-value",
"DRIFTCHECK_OUTPUT": "your-value",
"DRIFTCHECK_EXPORTS": "your-value"
}
}
}
}Run this in your terminal
claude mcp add driftcheck --env FIGMA_TOKEN=your-value --env DRIFTCHECK_OUTPUT=your-value --env DRIFTCHECK_EXPORTS=your-value -- dnx Driftcheck --yesFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"driftcheck": {
"command": "dnx",
"args": [
"Driftcheck",
"--yes"
],
"env": {
"FIGMA_TOKEN": "your-value",
"DRIFTCHECK_OUTPUT": "your-value",
"DRIFTCHECK_EXPORTS": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"driftcheck": {
"type": "stdio",
"command": "dnx",
"args": [
"Driftcheck",
"--yes"
],
"env": {
"FIGMA_TOKEN": "your-value",
"DRIFTCHECK_OUTPUT": "your-value",
"DRIFTCHECK_EXPORTS": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
DRIFTCHECK_OUTPUT envDRIFTCHECK_EXPORTS envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account wilsonvargas, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: FIGMA_TOKEN
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.1) reached the registry 10 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need .NET on your computer.
In the same category: Figma Context MCP, Claude Real Video, Figma MCP Server
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.
Let any LLM watch a video locally — and search everything it has ever watched.
Figma’s official server gives AI your design data so it can turn designs into code or describe them accurately. Connects to Figma’s cloud.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Driftcheck
Catch UI drift before your users do.
Your AI agent compares the app on the emulator with its Figma design, then fixes the differences.
Open the interactive report → · Design: Paylo kit by Marvilo (CC BY 4.0)
Driftcheck is a local MCP server. It captures the screen of an Android device or the iOS Simulator, compares it 1:1 with the Figma frame and gives your agent what it needs to close the gap:
Margin, android:layout_marginTop, Modifier.padding, .frame, EdgeInsets…It works with real-world design kits, where layers are called Frame or Text, and without a Figma token through the Driftcheck Figma plugin.
You need the .NET 10 SDK, plus adb for Android or Xcode for the iOS Simulator. Install Driftcheck in one click:
VS Code asks for your Figma token; leave it empty to use the Figma plugin instead. In Cursor, add the token to FIGMA_TOKEN in the server's configuration afterwards.
Or add it to any MCP client by hand; dotnet dnx downloads it from NuGet the first time:
{
"mcpServers": { "driftcheck": { "command": "dotnet", "args": ["dnx", "Driftcheck", "--yes"], "env": { "FIGMA_TOKEN": " " } } } }
With Claude Code:
claude mcp add driftcheck -e FIGMA_TOKEN=<your Figma token> -- dotnet dnx Driftcheck --yes
Then run your app and ask your agent:
Compare the app on the emulator with https://www.figma.com/design/…?node-id=… and fix the differences.
compare_screen answers with a report the agent can act on (excerpt from the demo):
**Fidelity: 75 %** — 15 of 20 elements as in Figma
| Element | Property | Figma | App |
|---|---|---|---|
| Nice to meet you | height | 31.5 | 25.5 |
| Text "Sign up with Google" | x | 131.9 | 125 |
| Shape "Sign up" | background | #DBC6F8 | #BAD1BB |
FontFamily="Inter", FontSize="32", CharacterSpacingBackgroundColor="#9E56FF" (it renders as #DBC6F8 in the design: the layer or a container has opacity)
Along with it come report.html (the interactive report above: slider, opacity, diff and side by side), side_by_side.png and diff.png.
| Device | How it reads the screen |
|---|---|
| Android emulator or device | adb: screencap + uiautomator dump (the AutomationId is the resource-id) |
| iOS Simulator (macOS) | simctl + an XCUITest helper that reads the accessibility tree (the AutomationId is the accessibilityIdentifier) |
Fix suggestions are written for .NET MAUI, Android views, Jetpack Compose, UIKit, SwiftUI and Flutter, or in plain terms if you don't pass a framework. The comparison itself doesn't depend on the framework: it works from what's on the screen.
| Tool | Use |
|---|---|
list_devices | Connected Android devices and booted iOS simulators |
get_design_specs | Sizes, colors, texts and fonts of the frame (before writing the UI code) |
capture_screen | Capture + app elements with their AutomationId |
compare_screen | Full design vs. app comparison: fidelity, differences, how to fix them and report.html |
import_design | Imports a .driftcheck.json from the Figma plugin that ended up outside Downloads |
Driftcheck downloads the frame once and keeps it in a local cache, recomputes Figma's auto layout, and matches layers to app elements by AutomationId, by visible text or by position. Texts are compared by their visible glyphs rather than their boxes, non-text layers are found in the screenshot by how they look, and a device slightly wider or narrower than the frame is handled by anchoring each element where it fits best. The full walkthrough is in How Driftcheck compares.
Figma limits how many calls a token can make, and on some seat types the quota is very low: once it runs out, it responds 429 with waits of days. That's why:
refresh=true to get_design_specs or compare_screen to download a frame that changed in Figma.429, the error says how long to wait.tools/figma-export-plugin exports the frame (JSON + 2x render) to a .driftcheck.json file without using the REST API. If it lands in Downloads, Driftcheck picks it up on its own from the frame link; if it lands in another folder, import it with import_design. See the plugin README.adb (detected from ANDROID_HOME, ANDROID_SDK_ROOT or the default paths on Windows and macOS)FIGMA_TOKEN environment variable with a Figma Personal Access Token (scope *File content: Read-only*), or the Figma plugin to work without the APIDRIFTCHECK_OUTPUT to change the output folder (default: driftcheck in the temp folder)DRIFTCHECK_EXPORTS to change where plugin exports are looked up (default: Downloads)get_design_specs provides it as a reference.git clone https://github.com/wilsonvargas/Driftcheck.git
cd Driftcheck dotnet build src/Driftcheck.Mcp
The .mcp.json at the root registers the server for MCP clients that read it when opening this folder. To use it from another project, add the server to your client's MCP configuration:
{
"mcpServers": { "driftcheck": { "command": "dotnet", "args": [" /src/Driftcheck.Mcp/bin/Debug/net10.0/Driftcheck.Mcp.dll"] } } }
src/Driftcheck.Mcp — MCP servertools/ios-accessibility-helper — UI test that dumps the iOS Simulator accessibility tree (copied next to the server on build)tools/figma-export-plugin — Figma plugin that exports a frame without the REST APIsamples/PayloMaui — MAUI test app with screens from the Paylo kit by Marvilo (CC BY 4.0) For the iOS Simulator: dotnet build -f net10.0-ios -p:TargetFrameworks=net10.0-ios (limiting TargetFrameworks avoids requiring the Mac Catalyst workload), then xcrun simctl install booted bin/Debug/net10.0-ios/iossimulator-arm64/PayloMaui.app and xcrun simctl launch booted com.companyname.paylomaui. The Xcode version must be the one the iOS workload asks for; if several are installed, pick it with DEVELOPER_DIR.samples/PayloNative — the same sign-up screen with native Android views (Java, no MAUI or AndroidX), to check that the comparison doesn't depend on MAUI. ./build.ps1 builds it with the SDK tools (no Gradle) and installs it on the emulatorsamples/PayloIos — the same screen with native iOS views (UIKit in Swift, no MAUI or storyboard). ./build.sh builds it with swiftc (no Xcode project) and installs it on the booted simulatortests/Driftcheck.Tests — comparer tests with synthetic screensdocs — the detailed comparison walkthrough and the demo report published on GitHub PagesTo compare the sample apps, open the Paylo kit in the Figma
Only the beginning is shown; read the rest in the repo