MCP server

UI UX Suite MCP: A Design Linter That Cites the Exact Line to Fix

UI UX Suite works like ESLint for design: it scores a project across 12 weighted dimensions and reports the file, line, measured value and fix for each finding.

Run
claude mcp add ui-ux-suite -- npx -y ui-ux-suite --mcp
View on GitHub

Stars, license and last push from GitHub. Install count as reported by the open skills directory.

What is UI UX Suite?

UI UX Suite is a design audit tool that also runs as an MCP server. It reads CSS, JSX, HTML and Tailwind classes, then reports located findings with the measured wrong value and an exact before and after fix. It scores 12 weighted dimensions and never edits your source.

The README's headline example is a single contrast failure: .hero-subtitle on line 14 of src/styles.css sets #fbfbfb on #ffffff, which measures 1.03 to 1. The suggested fix is #767676. Every finding follows that shape.

It is a command-line auditor first and an MCP server second. Run it on a folder and you get a ranked list plus a score out of 10, with no config file and no setup step.

What a finding contains

  • Located. The file, the line and the selector, like a linter error.
  • Measured. The real wrong value, such as a contrast ratio, rather than an adjective like low.
  • Fixed. An exact before and after change, plus the WCAG criterion or named UX law behind it.
  • Project-level findings, such as five font families where one or two would do, still score but have no single line to cite.

Safe by default

The static audit executes nothing and makes no network call. It needs no API key and sends nothing off your machine. It audits only: a fix is printed for you to apply, and the tool never edits a project file.

Deep mode is opt-in. It visits only the URL you give it, needs playwright-core plus @axe-core/playwright, and falls back to source findings when those are absent.

Where it fits

Best for

  • Teams that want a design score as a CI gate, using --fail-under or a baseline that fails on a new finding.
  • Agents that should check contrast, spacing and typography against measured numbers. Pair it with the accessibility audit skill for wider checks.
  • Reviews that need SARIF output for GitHub code scanning.

Not for

  • Anyone who expects automatic edits. It reports and never rewrites.
  • Palette generation. It scores contrast, and a color skill suits choosing new colors.
  • Visual taste feedback on a screenshot. The related critique skill is closer to that job.

Use it with UiChemy

UI UX Suite audits the CSS and markup you already have. UiChemy builds the WordPress page itself, writing into Elementor or Gutenberg, so the two do different jobs. To build a page first, click Get Started on uichemy.com.