ui-polish-mcp
Related Servers
Alternatives to ui-polish-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server that exposes a design system and UX rulebook as tools, enabling AI to generate UI consistent with your design tokens, components, layout rules, accessibility guidelines, and templates. It also provides a review tool to score UI proposals against the design system.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that bridges design and code by generating UI components, layouts, and themes from text prompts using v0.dev, with features like code refactoring and accessibility auditing.14 npm1MIT
- AlicenseAqualityDmaintenanceMCP server that gives AI coding agents the ability to design UIs through Google Stitch. It generates production-ready HTML and screenshots from natural language prompts.9MIT
- AlicenseCqualityAmaintenanceA production-grade MCP server that turns natural language intent into fully-architected, accessible, production-ready UI code through a 7-step agentic pipeline.201Apache 2.0
- AlicenseNot gradedqualityAmaintenanceThis MCP server enables AI agents to measure live web and responsive UIs — contrast ratios, touch targets, overflow, and theme drift — returning precise, selector-attached findings as text. It also lets a human and agent share the same live mobile and desktop session, with pinned notes and screenshots readable by the agent.268 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server for design decisions during a build, providing live UI/animation library docs (via llms.txt) and a curated knowledge base of UX laws and UI conventions. It enables agents to look up real component APIs and apply design best practices, running locally via stdio or hosted on Vercel.6 npmMIT
TDQS
Scored across 8 tools
Each tool targets a clearly distinct concern: component auditing, theme suggestion/retrieval/listing, single vs. batch color contrast checks, copy refinement, and placeholder suggestion. Overlapping areas like check_contrast and audit_color_pairs are explicitly separated as single-pair vs. multi-pair operations.
All tools follow a consistent verb_noun snake_case scheme: audit_component, suggest_theme, get_theme, list_presets, check_contrast, audit_color_pairs, refine_copy, suggest_placeholder. The naming makes each tool's resource and action predictable.
8 tools is well-scoped for a UI polish server. Each tool earns its place and collectively they cover component analysis, theme selection, contrast verification, and copy improvements without unnecessary bloat.
The toolset forms a complete pre-delivery polish workflow: audit React components, validate the color palette, refine UI copy, generate context-aware placeholders, and select or retrieve theme tokens. There are no obvious dead ends or missing core operations for the stated domain.