krusch-frontend-mcp
Related Servers
Alternatives to krusch-frontend-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables AI coding agents to absorb UI references into perceptual design tokens, semantic responsive layout skeletons, motion physics parameters, and zero-dependency multi-framework components, while auditing WCAG contrast, touch targets, reduced-motion guardrails, and layout stability.6MIT
- FlicenseNot gradedqualityDmaintenanceProvides AI assistants with access to a production-ready design system including Tailwind CSS component patterns, style guides (colors, typography, spacing), and Web Components specifications for consistent UI development.-
- AlicenseAqualityCmaintenanceGives AI coding agents a ten-phase frontend design pipeline (audit, style direction, build, review, verify, perf, brand) with an exclusive style menu. Its verify_page tool loads a URL in a real Playwright browser at mobile and desktop viewports and returns screenshots, ARIA snapshots, console errors, failed requests, horizontal-overflow offenders, axe-core violations, and pointer type.3MIT
- AlicenseAqualityBmaintenanceEnables coding agents to audit frontend source for generic AI UI patterns and WCAG 2.1 contrast failures, extract Design DNA from local stylesheets or live URLs, and export Tailwind v4 tokens. It also applies complete design presets to synchronize agent rule files and MCP configuration.25683 npm36MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI coding assistants to inspect frontend projects, search a curated design and motion recipe catalog, prepare and preview structured design plans, apply changes with backups and rollback, capture previews, audit UI accessibility and performance, and monitor activity via a web dashboard.-
- AlicenseNot gradedqualityBmaintenanceEnables AI coding assistants to generate bespoke design systems by synthesizing OKLCH color palettes, chamfer highlights and spring physics, teaching layout composition grammar, and returning micro-interaction primitives and component blueprints. Also audits JSX/TSX/HTML through a senior design director's lens to score and critique UI quality.1MIT
TDQS
Scored across 12 tools
Most tools have clearly distinct purposes (palette generation, layout analysis, breakpoints, RAG query, provenance). The one genuinely confusable pair is ingest_figma_tokens vs generate_css_variables_from_figma, which both parse Figma JSON, but the descriptions explicitly differentiate RAG ingestion from CSS output. Minor residual overlap between generate_component_styles and generate_css_variables_from_figma is manageable via descriptions.
All names use consistent snake_case with a verb_noun shape (generate_*, query_*, analyze_*, list_*, get_*). The only deviation is the 'frontend_' prefix applied to just two of twelve tools, which slightly breaks the pattern but remains readable and descriptive.
Twelve tools is well within the sweet spot for a design-system/frontend server, with each tool covering a distinct stage (tokens, CSS, layout, components, knowledge retrieval, templates). No obviously redundant or filler tools.
The surface covers the full frontend design pipeline: palette, CSS-to-Tailwind, Figma token ingestion and CSS variable emission, layout analysis, component styling, breakpoints, RAG queries, provenance/graph traversal, and canonical template listing/retrieval. Minor gaps exist around theme/dark-mode generation and writing back or updating design rules/tokens, but core workflows are covered end to end.