UIMax MCP MCP Server

If you already use UIMax MCP, the uimax mcp mcp server is the piece that lets your assistant work with it directly. UIMax MCP — Turns Claude Code into a frontend expert that reviews and fixes your UI automatically. Free for Pro plan users.

What the server does

1. Sees your app — captures a real screenshot via Puppeteer 2. Audits accessibility — runs axe-core for WCAG 2.1 violations 3. Runs Lighthouse — real Google Lighthouse scores (Performance, Accessibility, Best Practices, SEO) 4. Measures performance — captures Core Web Vitals (FCP, LCP, CLS, TBT) 5. Audits SEO — 18 checks: meta tags, Open Graph, Twitter cards, structured data, heading hierarchy, canonical URLs 6. Scans your code — AST-based analysis for 25+ anti-patterns across accessibility, design, and code quality 7. Grades everything — per-section Report Card with letter grades (A+

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• Debugging — The Debugging tool exposed by this server

Credentials and setup notes

• Node.js >= 18.0.0 - Chrome/Chromium (uses your system Chrome — no extra download) - Claude Code (for MCP integration)

Installation

The server ships on npm as uimax-mcp, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Where it fits

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. UIMax MCP's toolset — Debugging — is a fair guide to whether it matches your workflow. It is maintained by prembobby39-gif; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against UIMax MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Worth knowing first

• 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.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.