Figma Context MCP
by GLips
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.
Runs on your computer★ 16,165MITUpdated 5 months ago
Install
onsystem
Overview
Description from the maker (original English)
Catches palette colors, native elements and APIs your design system lacks in agent-written React.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Design, images & audio
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- The registry lists no key to fill in.
You need
- npmNode.js installed (for the npx command)
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": {
"onsystem": {
"command": "npx",
"args": [
"-y",
"onsystem"
]
}
}
}Run this in your terminal
claude mcp add onsystem -- npx -y onsystemOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"onsystem": {
"command": "npx",
"args": [
"-y",
"onsystem"
]
}
}
}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.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"onsystem": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"onsystem"
]
}
}
}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.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
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 6, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account dgesteves, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Design, images & audioi
- More stars than 0% of the other 2163 servers in this category
- Published to the registry more recently than 83% of the other 2163 servers in this category
- Basic checks equal to or better than 100% of the other 2163 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is onsystem safe?
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.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
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).
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.12.1) reached the registry 6 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
What can I use instead?
In the same category: Figma Context MCP, Claude Real Video, Figma MCP Server
Alternatives
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
Claude Real Video
by HUANGCHIHHUNGLeo
Let any LLM watch a video locally — and search everything it has ever watched.
Runs on your computer★ 2,284MITUpdated 2 months ago
Install
Figma MCP Server
by figma
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.
Runs in the cloud★ 2,152Updated 13 months ago
Install
README from the maker
Open the README
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.
onsystem
Keeps coding agents on your design system: catches palette colors, native elements and APIs your system lacks, at every edit and pull request, with the fix. Set it up once in your design-system package; every app in your monorepo gets it. Runs locally and works alongside @shadcn/lint.
Built for design-system and platform teams with a React design-system package; a shadcn/ui app is the zero-config demo. Formerly @dgesteves/design-system-mcp (what changed).
Using the GitHub Action? uses: dgesteves/onsystem@v0 checks the lines a pull request changed: see CI and baselines.
Also works with
Website and docs: onsystem.vercel.app, with a playground that checks your own code.
Feedback wanted: say where it breaks in the launch feedback thread, see what's next in the roadmap, or pick up a good first issue. If onsystem is useful to you, a star helps other people find it.
https://github.com/user-attachments/assets/900cc1fa-387c-4e76-a524-a818521dd1a0
On the website , an agent drafts a settings card, check_ui finds 11 problems with a fix each, and the agent applies them. Then a real Claude Code session with the plugin: Claude looks the components up before writing, and check_ui passes. Last, the benchmark.
The problem
Coding agents write UI from their training data, not from your design system. Ask for a settings card and you get bg-[#ef4444], p-[13px], a native , variant="danger" on a Button that only has destructive, and where the system exports CardHeader. On the demo draft above, tsc reports 3 of the 11 problems, and review catches the rest when someone has the time. Describing the design system to the agent helps; what holds is checking what it actually wrote, at the edit and at the pull request.
What it checks
onsystem reads your components, cva and tv variants, parts and tokens from source with the TypeScript compiler, and checks .tsx and .jsx against them. Every finding has a rule id, a location and the fix. Tokens come from your stylesheets, DTCG 2025.10 files or a DESIGN.md, and onsystem export writes them out as either.
| Rule | Default | Catches |
|---|---|---|
no-unknown-component | error | Components and parts that don't exist ( , typos) |
no-unknown-prop | error | Props a component doesn't take (tone, isDisabled) |
no-unknown-variant | error | Values outside a variant (variant="danger") |
prefer-design-system-component | error | Native elements the design system has a component for ( → ) |
no-hardcoded-color | error | Hex, rgb, hsl, oklch and Tailwind palette colors (bg-gray-100 → bg-muted) |
icon-button-accessible-name | error | Icon-only buttons without an accessible name |
no-hardcoded-spacing | warn | Arbitrary padding, margin and gap (p-[13px] → p-3) |
no-hardcoded-radius | warn | Arbitrary radius (rounded-[7px] → rounded-sm) |
How often it is wrong. The corpus job runs check on 12 public repositories pinned by commit (Documenso, Dub, Cal.com, midday, Flowise and others: 24 runs, 14,539 distinct findings), without their dependencies installed (the two MUI apps get MUI). A seeded random sample of 80 of those findings, stratified by rule, was labelled from the code alone: blind labels by an AI reviewer (Claude Opus 5.5), not by a person. 57 are right, 14 debatable and 9 false positives: 11.2% (95% Wilson interval 6.0-20.0%), about the same when weighted by each rule's share of all findings (11.0%). Most come from no-hardcoded-color (7 of 65 sampled). Counting values a project's own design system already uses as debatable, 6 of 80 are false positives (7.5%, 3.5-15.4%). The sample has each label with its reason, the labeller's notes and the script behind these numbers. Shipped code rarely invents components, props or variants, and without dependencies no-unknown-prop skips components whose props do not resolve: those three rules have 56 findings in the corpus, 55 of them in Flowise, an MUI app, and 3 in the sample, all right but too few for a rate of their own. The corpus's older labels, made by an AI reviewer who could see the finding and so not blind, fail the job when one of their true positives stops being reported or a fixed false positive comes back. Code installed from a shadcn registry, such as the chatbot's components/ai-elements, has no labels yet (Code from shadcn registries). The rules reference shows each rule on an example and how to suppress a finding.
Quickstart
Run it from the app's folder or from the monorepo root, with Node.js 20.19 or later:
npx -y onsystem inspect # what it found; --explain says whynpx -y onsystem check . # the same check the agent and CI run npx -y onsystem init # write the config, and offer a baseline
At a monorepo root, inspect lists every app and design-system package, and check checks each file by its own project's design system. In a design-system package, init sets it up for every app that depends on it, with no config in the apps: as a workspace package, or installed from npm. Installed apps read the components from the sources the package publishes, or from its type declarations (.d.ts) when it publishes only compiled dist/, and get every rule either way (init checks its files list). From a package that publishes compiled code and no type declarations, they get the token rules but no component, prop, variant or native-element checks.
In a new create-next-app, the template page's hardcoded colors already make the first check . fail; init offers to record them as a baseline, so only new findings fail. Folders installed from a shadcn registry, such as components/ai-elements, are someone else's code: Code from shadcn registries says how to check them or leave them out.
Claude Code. The plugin brings the hook, the MCP server and a skill:
/plugin marketplace add dgesteves/onsystem/plugin install onsystem@dgesteves
After each Write or Edit of a .tsx or .jsx file, the hook runs onsystem check on it. Errors go back to Claude as a blocking error with the fix, so Claude corrects the file before it moves on; warnings go as a note. It stays
Only the beginning is shown; read the rest in the repo