tailwind-context-resolver-mcp
Related Servers
Alternatives to tailwind-context-resolver-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables AI coding agents to inspect a project's design tokens and component catalog, audit React/Tailwind files against seven static UI quality rules, score overall UI health, and apply auto-fixes that are re-audited and reverted on regression. It works both locally over filesystem access and remotely on raw TSX/JSX or CSS snippets passed directly as strings.-
- AlicenseBqualityFmaintenanceProvides comprehensive tools for TailwindCSS development including utility class retrieval, CSS-to-Tailwind conversion, and color palette generation. It enables AI assistants to search documentation, generate component templates, and provide framework-specific installation guides.81,126 npm39MIT
- AlicenseNot 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.2 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to query a workspace's design system before writing UI and validate generated code against the same system afterward, using configurable token and component sources.9 npmMIT
- AlicenseBqualityCmaintenanceEnables LLMs to work with the Optics Design System, providing access to 83 design tokens (HSL-based colors, spacing, typography), 24 components with dependencies, and tools for theme generation, accessibility checking, and code scaffolding.156 npm1MIT
- FlicenseNot gradedqualityDmaintenanceConnects an AI agent to Figma and Panda CSS for two-way design system sync, component creation, and variable binding.-
TDQS
Scored across 7 tools
Each tool targets a distinct aspect of Tailwind CSS context: config overview, theme variable extraction, dead-token auditing, class compilation simulation, theme token querying, class string validation, and conflict detection. There is no meaningful overlap; even the two token-related tools are clearly differentiated by their source (CSS @theme vs resolved theme).
All tool names follow a consistent verb_noun pattern using lowercase with underscores (get_, resolve_, audit_, simulate_, validate_, detect_). Though the verbs differ, they accurately reflect the unique action each tool performs, and the pattern is uniform throughout.
Seven tools is well within the ideal range and each tool directly serves the server's purpose of resolving and validating Tailwind CSS context. No redundant tools and no missing essential operations for a read-only context resolver.
The toolset covers the full lifecycle of working with Tailwind design tokens and classes: config summary, theme token extraction and querying, dead-token auditing, class validation, conflict detection, and JIT simulation. There are no obvious gaps; it handles both Tailwind v3/v4 scenarios and provides actionable checks for developers.