Skip to main content
Glama
tailwind-context-resolver-mcp

tailwind-context-resolver-mcp

by vola-trebla

Related Servers

Alternatives to tailwind-context-resolver-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to validate, search and canonicalize Tailwind class names, resolve which conflicting utility wins, inspect theme tokens and variants, check color contrast, and migrate v3 classes to v4. It answers by querying the project's own installed Tailwind engine, so results reflect the real configuration, plugins and version instead of a stale snapshot.
      9
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables 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.
      -
    • A
      license
      B
      quality
      D
      maintenance
      Provides 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.
      8
      3,057 npm
      40
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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.
      13 npm
      1
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables LLM agents to search, resolve and audit DTCG design tokens — finding the token behind an intent or a hard-coded color/size, checking naming grammar, auditing CSS for hard-coded or unknown tokens, arbitrating semver, and previewing token additions as JSON Patch diffs. Writes are gated behind explicit confirmation plus an opt-in flag, so every change arrives as a reviewable proposal rather than an edit.
      7
      MIT

    TDQS

    A4.3/5.0

    Scored across 7 tools

    Disambiguation5/5

    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).

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues