Ui MCP Server

UI/UX design-audit MCP server: scores a project on 12 dimensions vs WCAG 2.2 + APCA. The ui mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 11 defined tools rather than through you.

What it actually does

Most "design review" tools tell you "improve your contrast." This tool tells you:

• Real color science. — Contrast is computed with the tool's own WCAG 2.2 and APCA math, not estimated. The fixture's measured ratios (e.g. 1.03:1) are reproducible from lib/color-engine.js
• Cited WCAG success criteria. — Accessibility findings cite the exact SC: 1.4.3 Contrast (Minimum), 1.4.11 Non-text Contrast, 2.5.8 Target Size, 2.4.7 Focus Visible, 1.1.1 Non-text Content, 3.3.2 Labels or Instructions
• A regression gate, not a vibe. — 311 tests (run npm test) assert real behavior, including a 12-problem fixture where every finding must carry evidence.file, evidence.line, and a fix. If specificity regresses, the test suite fails

Its toolset

Everything the assistant can do here goes through one of these:

• Platform — Skills directory
• Trae — ~/.trae/skills
• Vibe — ~/.vibe/skills
• OpenClaw — ~/.openclaw/skills
• Antigravity — ~/.gemini/antigravity/skills
• Dimension — Weight
• Accessibility — 12%
• Responsiveness — 8%
• uiux_audit_run — One-call full audit. Scan → extract → score 12 dimensions → located findings. Supports depth: quick\
• uiux_scan_project — Detect framework, styling (Tailwind v3 vs v4), component/theme/icon libs
• uiux_check_contrast — WCAG 2.2 + APCA contrast for any pair

Adding it to your client

ui-ux-suite on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

When to reach for it

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Ui's toolset — Platform, Trae, Vibe and 8 more — is a fair guide to whether it matches your workflow. It is maintained by Aboudjem; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 11 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Ui.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the ui mcp server does with a few real requests.