Skip to main content
Glama

Related Servers

Alternatives to css-is-awesome-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to query a design system's components, tokens, icons, patterns, and usage or accessibility guidelines through standardized MCP tools, with pluggable adapters for different data sources.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Read-only MCP server that exposes a design system's tokens, components, conventions, and deprecations as queryable tools, enabling agents to look up canonical values, assess change impact, and detect hardcoded value drift.
      8
      3 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI IDEs to query Figma design tokens, component specs, and audit issues via MCP tools, without cloud subscriptions.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables MCP-capable IDEs to search 8,214 design-system components, retrieve exact source bundles and semantic tokens, and follow a copy-first handoff workflow with composition validation.
      6
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      MCP server for the Lando Labs Design System, enabling AI agents to introspect and generate code for React components, hooks, icons, design tokens, and theme presets via 15 tools.
      15
      12 npm
      1
      Apache 2.0

    TDQS

    A3.5/5.0

    Scored across 34 tools

    Disambiguation4/5

    The set follows a clear list/get/search pattern per resource type (functions, mixins, tokens, themes, recipes, animations, components), making most tools trivially distinguishable. Minor fuzziness exists among the eight read_* doc tools (read_readme/read_agents/read_llm_txt are all 'entry points') and between get_token/get_token_map, but descriptions resolve these.

    Naming Consistency4/5

    Strong verb_noun convention throughout: list_/get_/search_/read_ prefixes with plural nouns for list/search and singular for get, applied consistently across seven resource families. Minor deviations like the bare 'status', 'assemble_prompt', and the noun_from_noun 'theme_from_tokens' keep it from perfect.

    Tool Count3/5

    34 tools is heavy; the breadth of the library (functions, mixins, tokens, themes, components, animations, recipes, docs) justifies many, but the eight separate read_* doc tools and several near-parallel get/list/search triads could be consolidated. Borderline-above the comfortable range for the surface.

    Completeness5/5

    Coverage is thorough: list/get/search for every resource type, plus validation, theme generation from design tokens, token mapping, size resolution, and full documentation access. Hidden gaps are hard to find for a read/inspection-focused library server.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data