mcp-uimax
Related Servers
Alternatives to mcp-uimax
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceProvides professional UI/UX design expertise and frontend development tools for analyzing interfaces, generating design systems, and creating modern components with accessibility and best practices built-in. Supports React, Vue, Angular and other frameworks with seamless Claude Code CLI integration.423MIT
- AlicenseAqualityDmaintenanceEnables Claude Code to capture and analyze web page screenshots, responsive layouts, and page metadata using Puppeteer. It allows developers to perform visual UI inspections and compare designs across various viewports directly within the terminal.3MIT
- AlicenseAqualityDmaintenanceCore Web Vitals analysis powered by Lighthouse. Four tools: analyze a URL, compare two URLs, check against thresholds, or crawl an entire site. Works with Claude Code, Cursor, Windsurf, and any MCP-compatible AI tool.410 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants such as Claude, ChatGPT, Cursor, and Claude Code to run 25+ specialized SEO checks on any URL, generate XML sitemaps and robots.txt files, extract brand design elements, and audit technical SEO, content quality, mobile responsiveness, and security.MIT
- AlicenseNot gradedqualityAmaintenanceGives Claude Code a real browser so it can navigate, click, type, screenshot, and assert against web pages directly from the terminal. Enables multi-step test scenarios, visual regression checks, session recording, and console/network error monitoring with security controls.106 npmMIT
- AlicenseAqualityCmaintenanceAI design fidelity — compare Figma designs or screenshots against the rendered implementation and get structured discrepancies. Uses your Claude Code or Codex subscription, no API keys.31MIT
TDQS
Scored across 37 tools
Many tools have overlapping purposes (e.g., multiple performance audits, multiple comparison tools, and a 'primary' review tool that subsumes many others). Agents will struggle to choose the correct tool due to redundant functionality and unclear boundaries.
Most tools follow a verb_noun pattern (e.g., capture_console, check_budgets), but some deviate (lcp_optimization, responsive_screenshots). Overall, the naming is readable and predictable, with only minor inconsistencies.
With 37 tools, the server is overly bloated for its domain. Many tools are highly specific (e.g., check_dark_mode) and could be merged. This volume increases cognitive load and reduces efficiency.
The tool set covers nearly all aspects of UI auditing: accessibility, performance, SEO, visual comparison, interaction testing, and reporting. Minor gaps exist (e.g., no dedicated mobile viewport testing beyond responsive screenshots), but overall it is comprehensive.