What it does
It reads CSS, JSX, HTML and Tailwind classes and reports each located finding with its file, line and selector, the measured wrong value, and a before-to-after fix tied to a WCAG criterion or named UX law. Findings that have no single line, such as using too many font families, are reported at project level with a score and a description of the problem. Output is a ranked report in Markdown, JSON, HTML or SARIF, with a weighted score out of 10 in which accessibility carries the most weight.
It suits teams that want design issues caught like linter errors, either run from the command line or added to CI, where an absolute score bar or a baseline can fail a build on a new finding or a score drop. Developers using a supported agent or editor can also ask for a design audit in chat, through 14 skills and 16 tools.
The tool needs Node 18 or newer and has no configuration step. The default static audit runs without an API key and makes no network calls. Deep mode is optional and visits a URL you supply. The tool audits only and does not edit source files; it writes report and baseline files only when asked.
Limitations and requirements
Requires Node 18 or newer. Deep mode is opt-in and needs the playwright-core and @axe-core/playwright packages; without them it falls back to source findings only. Project-level findings do not point to a single line.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 17 Nov 2026 · its page on the source
UI/UX Suite
ESLint for design: UI bugs in your source, with the file, line, measured value and fix. WCAG 2.2.
v0.7.1As shown on registry.modelcontextprotocol.io when we last read it