Listed from the MCP registry; nobody on Odel publishes it.
Design bugs by line number in CSS, JSX, HTML and Tailwind, each with the measured value and the fix.
Runs on your machine from its package; the steps are below.
At most: only reads or looks up information.
Odel charges nothing per call. The publisher may charge for its own service.
Runs locally over stdio
This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).
Run
npx -y ui-ux-suite
MCP client config
{
"mcpServers": {
"ui-ux-suite": {
"command": "npx",
"args": [
"-y",
"ui-ux-suite"
]
}
}
}English · 简体中文 · 日本語 · Español · Français
Design bugs by line number, each with the exact fix.
It reads your source code and prints what to change, line by line.
| Exact line to fix | WCAG rule cited | Fix value given |
|---|---|---|
| 46 located findings on the test app, each with a file and a line. | Contrast is measured against WCAG 2.2; each finding cites a WCAG rule or UX law. | Each one shows the measured value and the change, such as #fbfbfb to #767676. |
Works with: any MCP client and any agent that reads skills. Tested: Claude Code, Cursor, Codex, Gemini CLI, OpenCode.
Use it on any web project, before you ship or on each push. It is plain code, so it needs no AI model.
You get a score out of 10 and the three fixes to do first. Below them, every finding with its fix, and its file and line when it has one.
npx ui-ux-suite .
The report opens with the score, then the three fixes to start with, then the detail.
# Design audit: 3.7/10 (Needs Work)
**Verdict:** score 3.7/10, Needs Work. 46 located findings, 8 critical.
## Fix these first
1. 9 `.swatch*` color variants fail WCAG AA contrast (worst 1.75:1) at `src/styles.css:118`. Fix: Rebuild this color set against the surface it sits on so each meets ≥ 4.5:1 (e.g. the worst, `#b5c6d7`, should be `#6d7882` or darker), or reserve ...
2. No visible keyboard focus indicator anywhere at `src/styles.css:22`. Fix: Add a focus ring to all interactive elements: `:focus-visible { outline: 2px solid var(--ring, #2563eb); outline-offset: 2px; }`.
3. Fixed 1200px width on `.layout` with 0 media queries at `src/styles.css:57`. Fix: Use `max-width: 1200px; width: 100%` and add responsive breakpoints (sm/md/lg).
**Weakest areas:** Typography System 1.5/10, Accessibility 1.6/10, Component Quality 2/10.
_Scanned 3 CSS, 1 JSX/TSX/Vue/Svelte and 1 HTML files in 0.03s on 2026-11-17T18:22:05.018Z. The detail follows._
This is a real run on our test app, version 0.7.1. The command is in Proof. The test app is broken on purpose, so it scores low.
It reads source, not pixels, and a high score does not prove WCAG conformance.
Recommended: one command for all your agents and projects.
npx skills add Aboudjem/ui-ux-suite -g
Works in more than 70 agents: pick yours in the menu (the list).
npx skills is Vercel's open installer for agent skills. Its page: skills.sh/aboudjem/ui-ux-suite.
In a terminal it shows the agent menu. In a script it installs into every agent folder, so add -a <agent> there.
It installs the 14 skills only. The MCP server, which the skills call, is one more line, below. Only this project: drop -g.
Or install straight into one agent. Click it to jump to its command. Nothing to configure, and no API key.
Claude Code (skills install tested)
npx skills add Aboudjem/ui-ux-suite -g -a claude-code
Codex (MCP tested, skills install tested)
npx skills add Aboudjem/ui-ux-suite -g -a codex
Cursor (MCP tested, skills install tested)
npx skills add Aboudjem/ui-ux-suite -g -a cursor
Gemini CLI (MCP tested, skills install tested)
npx skills add Aboudjem/ui-ux-suite -g -a gemini-cli
GitHub Copilot (install tested)
npx skills add Aboudjem/ui-ux-suite -g -a github-copilot
OpenCode (MCP tested, skills install tested)
npx skills add Aboudjem/ui-ux-suite -g -a opencode
Claude Code plugin. It adds 5 slash commands, 12 agents and the MCP server to the 14 skills. Tested.
claude plugin marketplace add Aboudjem/10x
claude plugin install ui-ux-suite@10x
Then add the MCP server. The plugin brings it. Elsewhere, the skills call it, so add it once. MCP is an open standard that lets an agent call tools. This line adds it for all your projects in Claude Code. The snippet for each other agent is in docs/editors.md.
claude mcp add -s user ui-ux-suite -- npx -y ui-ux-suite --mcp
{
"mcpServers": {
"ui-ux-suite": { "command": "npx", "args": ["-y", "ui-ux-suite", "--mcp"] }
}
}
No agent at all. The command line needs no install step: npx ui-ux-suite . runs it.
Each row is a real install and check, run on the date shown on macOS with Node 22.
| Agent | How it was installed | Tested | What the test showed |
|---|---|---|---|
| Claude Code | Plugin loaded with claude --plugin-dir . | 2026-11-17 | claude plugin validate . --strict passes, and the MCP server connects |
| Cursor | .cursor/mcp.json, then cursor-agent mcp enable ui-ux-suite | 2026-11-17 | cursor-agent mcp list-tools ui-ux-suite lists the 16 tools |
| Codex | codex mcp add ui-ux-suite | 2026-11-17 | codex mcp list shows the server enabled |
| Gemini CLI | gemini mcp add ui-ux-suite, then trust the folder | 2026-11-17 | gemini mcp list shows the server connected |
| OpenCode | opencode.json | 2026-11-17 | opencode mcp list shows the server connected |
| Skills CLI 1.9.0 | npx skills add Aboudjem/ui-ux-suite -g -a <agent>, for each of the 6 agents above, in a fresh home folder | 2026-11-17 | The 14 skills land in ~/.agents/skills, or ~/.claude/skills for Claude Code |
| Claude Code MCP | claude mcp add -s user ui-ux-suite -- npx -y ui-ux-suite --mcp, in a fresh home folder | 2026-11-17 | claude mcp list in another folder shows the server connected |
| Any MCP client | npx -y ui-ux-suite --mcp | 2026-11-17 | A raw MCP session lists 16 tools and audits the test app at 3.7 |
Documented, not run on that date: the MCP setup for VS Code and GitHub Copilot, Windsurf, Continue, Zed, Pi and install.sh.
Their snippets are in docs/editors.md.
Two agents need one more step before the server starts:
cursor-agent mcp enable ui-ux-suite.gemini there once and pick "Trust folder".1. Point it at a project.
npx ui-ux-suite .
2. Fix the three lines at the top. Each one names a file, a line and the change to make.
3. Put it in CI. CI means the checks that run on each push. Pick the output format and the rule that fails the build.
npx ui-ux-suite . --fail-under 7 # exit 1 when the score drops below 7
npx ui-ux-suite . --json | jq # machine-readable, banner goes to stderr
npx ui-ux-suite . --html report.html # standalone HTML report
npx ui-ux-suite . --sarif ui-ux.sarif # SARIF 2.1.0 for GitHub code scanning
npx ui-ux-suite . --write-baseline .uiux-baseline.json # save today's findings
npx ui-ux-suite . --baseline .uiux-baseline.json --fail-on-regression
npx ui-ux-suite . --tags dimension:accessibility --exclude-tags severity:nice-to-have
In an agent, ask for it in plain words: "audit this project's design". In Claude Code, type /ui-ux-suite:audit.
4. Optional: use deep mode. It checks the running app in a real browser. The CLI has no deep flag. Deep mode runs through the MCP tool uiux_audit_run.
First, install the two extra packages and a browser in your project:
npm i -D playwright-core @axe-core/playwright
npx playwright install chromium
Then start your app and ask your agent: "Run uiux_audit_run with depth: "deep" and baseUrl: "http://localhost:3000"."
Deep mode adds live contrast, axe-core checks and touch targets under 44 by 44 pixels. The parameters are in docs/tools.md.
Every flag and exit code is in docs/cli.md. Every MCP tool is in docs/tools.md.
It reads your source, measures each value and prints the fix. It does not run your app or need a browser.
| Step | What happens |
|---|---|
| 1. Read | It walks the folder and reads CSS, SCSS, JSX, TSX, Vue, Svelte, HTML and Tailwind classes. |
| 2. Measure | It computes real values: contrast in WCAG 2.2 and APCA, font sizes, spacing, target sizes. |
| 3. Locate | It ties each problem to a file, a line and a selector. |
| 4. Score | It scores 12 weighted dimensions out of 10. Accessibility weighs the most, at 12%. |
| 5. Report | It prints the score, three fixes, then every finding with its before, its after and the WCAG rule or UX law behind it. |
Think of it as ESLint for design. ESLint is a tool that checks code style. It finds low contrast, a missing focus ring, and a fixed width that breaks on phones.
Some findings are about the whole project, such as "5 font families, use 1 or 2". They count in the score and have no single line.
Here is one finding in full, from the same test app run:
### [!] Low text contrast on `.hero-subtitle`: 1.03:1
- **Where:** `src/styles.css:14` · selector `.hero-subtitle`
- **Measured:** 1.03:1 (APCA Lc 0) (needs 4.5:1)
- **Why:** Text `#fbfbfb` on `#ffffff` measures 1.03:1 (APCA Lc 0). WCAG 2.2 §1.4.3 requires ≥ 4.5:1 for normal text.
- **Impact:** Users with low vision (and most users in bright light) cannot read this text.
- **Fix:** Change `color` on `.hero-subtitle` from `#fbfbfb` to `#767676` (meets 4.5:1 on `#ffffff`), or darken further.
- **Cites:** WCAG 1.4.3 Contrast (Minimum) (AA)
What is APCA Lc? It is a second contrast score, built to match how people see text. It runs from 0, no visible contrast, to about 106. The tool calls Lc 90 fine for body text, and 60 the floor for large text. The WCAG ratio still decides pass or fail. See docs/science.md.
The weights and the scoring rules are in docs/scoring.md. The standards behind the findings are in docs/science.md.
Every number on this page comes from a command. Run it and compare.
| Claim | Command that prints it |
|---|---|
| 397 tests pass, 0 fail | npm test |
| The broken test app scores 3.7 out of 10, with 46 located findings | npx ui-ux-suite test/fixtures/planted-ux-problems |
| The MCP server exposes 16 tools | node scripts/gen-tool-reference.js --check |
| The repo holds 14 skills | npx skills add Aboudjem/ui-ux-suite --list |
| The package has no runtime dependency | npm view ui-ux-suite dependencies prints nothing |
| The plugin manifest is valid | claude plugin validate . --strict |
The test app is the regression check. It has known problems on purpose, listed in PLANTED.md. The tests fail if one of them stops being found with a file, a line and a fix.
CI runs the same npm test on every push and pull request, on Node 18 and Node 22.
Is it safe to run on my project? Yes. It never creates, edits or deletes a source file. It only writes the report or baseline file you name.
Does my code leave my machine? No. The audit makes no network call, needs no API key and sends no telemetry. Deep mode opens only the URL you give it.
Do I need a running app? No. The default audit reads source files. Deep mode is optional and adds live checks through Playwright and axe-core.
Does it fix my code for me?
No. It prints each fix as a before and an after. You, or your agent, apply it.
My project already scores badly. Can I still use it in CI? Yes. Save a baseline once: a file with today's findings. Then the build fails only on a new finding or a lower score. The two commands are in step 3 above.
Which stacks does it read? React, Next.js, Vue, Svelte, Angular and plain HTML. Tailwind v3 and v4, CSS Modules, SCSS, styled-components, Emotion and plain CSS.
How is it different from Lighthouse or axe? Those two need a running page. This reads source, so it can name the file and the line. See docs/comparison.md.
More questions are answered in docs/faq.md.
playwright-core and @axe-core/playwright. Without them you get the source findings only.MIT · Built by Adam Boudjemaa