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)
Check web pages for responsive design problems and screenshot them on phone, tablet and desktop.
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.
You need
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": {
"facet": {
"command": "npx",
"args": [
"-y",
"@chandra14/facet-check",
"mcp"
]
}
}
}Run this in your terminal
claude mcp add facet -- npx -y @chandra14/facet-check mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"facet": {
"command": "npx",
"args": [
"-y",
"@chandra14/facet-check",
"mcp"
]
}
}
}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": {
"facet": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@chandra14/facet-check",
"mcp"
]
}
}
}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.
These 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 chndr-prksh, 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.
The registry does not list a required key, though some servers ask you to sign in on first use.
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.0) reached the registry 24 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js 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.
Check a web page for responsive design problems on real phone, tablet and desktop viewports. It runs from the command line, in CI, or as an MCP server that AI coding agents (Claude Code, Cursor, Codex, VS Code) can call.
npx @chandra14/facet-check localhost:3000
Or install it once with npm install -g @chandra14/facet-check, then run facet-check localhost:3000.
Output for a test page with a price table that is too wide for phones (shortened):
Facet check http://localhost:3000
6 devices · 14 errors · 14 warnings
✗ iPhone 16 393×852 @3x error Page scrolls sideways by 267px — The document is 660px wide in a 393px viewport. error Extends 267px past the viewport — “SizeWhole beanGroundSubscriptionWholesal” html > body > main > table fix: Constrain it with max-width: 100%, min-width: 0 on a flex child, overflow-wrap: anywhere, or let it scroll inside its own container. error Tap target is 13 × 13px — #weekly fix: Targets must be at least 24 × 24px (WCAG 2.5.8); 44 × 44px is comfortable. warn Field text is 14px, so iOS zooms in on focus — #email fix: Give form controls font-size: 16px or larger. console Carousel failed to initialise at 393px
! Full HD laptop at 125% (most common) 1536×864 @1.25x warn Text is only 10px — “Prices include tax. Orders placed after ”
Each device is a real emulation in headless Chromium, not a resized window. It uses the device's viewport, pixel ratio, touch support, mobile viewport behaviour and user agent. A page with no viewport meta tag lays out at 980px on a phone, as it would on the real device.
It is the command-line and agent side of Facet, an open-source browser for responsive web development. Facet's device catalogue has 290+ profiles, from the iPhone SE to 2026 flagships, foldables, tablets, laptops and 4K monitors.
On every device:
device-width, or zoom disablednpx @chandra14/facet-check <url> [options]
| Option | |
|---|---|
-d, --devices | Device ids, names, sizes like 1024x768, or a preset (default: popular) |
-s, --screenshots | Save a PNG of each device |
--full-page | Capture the whole page, not only the first screen |
--json | Print the full report as JSON |
--all | Also list info-level notes |
--fail-on | Exit 1 when a finding is at least error (default), warn or info; never always exits 0 |
--timeout | Page load timeout (default 30000) |
--list-devices [query] | Show presets and the device catalogue |
The URL can be a full URL, a bare host (example.com), a local dev server (localhost:3000, :5173) or a path to an HTML file.
Presets: popular (the six most common real-world sizes), default (phone, tablet, laptop), phones, latest, tablets, desktops, apple, foldables, extremes.
npx @chandra14/facet-check localhost:3000 -d phones --screenshots shots
npx @chandra14/facet-check https://example.com -d iphone-17,"Galaxy S26",ipad,1440x900 --json
The exit code is 1 when errors are found, so it can gate a pull request:
- run: npx @chandra14/facet-check http://localhost:4173 --fail-on error
facet-check mcp runs a Model Context Protocol server over stdio. An agent can then check its own CSS changes on many screen sizes and look at the result.
Claude Code
claude mcp add facet -- npx -y @chandra14/facet-check mcp
Cursor, VS Code, Claude Desktop and other clients
{
"mcpServers": { "facet": { "command": "npx", "args": ["-y", "@chandra14/facet-check", "mcp"] } } }
| Tool | What it does |
|---|---|
check_responsive | Loads a URL on several devices and returns the problems on each, with selectors and fixes |
screenshot | Returns one labelled image per device (viewport or full page) |
compare_element | Measures one element on every device: size, visibility, font size, display, flex and grid |
audit_accessibility | Runs axe-core on one device and returns WCAG violations with fixes |
list_devices | Lists the device catalogue and presets |
Then ask, for example: *"Check localhost:3000 on phones and fix anything that scrolls sideways."*
Node 20 or later and a Chromium-based browser. facet-check uses, in order: the browser at FACET_CHROME, Playwright's Chromium (npx playwright install chromium), Google Chrome, then Microsoft Edge. Most machines already have one of these.
MIT