Skip to main content
Glama

Related Servers

Alternatives to ds-canon

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      A read-only MCP server that provides AI coding agents with a queryable contract for design system tokens, components, patterns, and anti-patterns.
      12 npm
      1
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for design tokens that gives AI agents read access to design systems, enabling token resolution, listing, and component usage lookups via natural language.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that exposes your design system components and tokens to AI agents, preventing duplicate component creation and hardcoded token values.
      9 npm
      9
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      MCP server that gives LLMs deep knowledge of design systems and tokens, enabling intelligent design evolution, token analysis, and designer-to-developer handoffs.
      37
      5 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides resources, tools, and prompts for a Design System via MCP protocol, enabling component search, reading, and related component discovery.
      205 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that gives AI assistants structured access to a design system's tokens, components, guidelines, and patterns, enabling them to read, lint, and author design system data.
      1
      MIT

    TDQS

    A4/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: listing vs. retrieving specific entities, finding usages, checking deprecations, conventions, and code drift. The overlap between whats_deprecated and filtered token/component lists is minimal because the former is specifically about deprecated items and their migration targets.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern (list_tokens, get_component, find_usages, check_token_drift), but whats_deprecated breaks the pattern with a question-style name. Overall the naming is predictable and readable, with one minor deviation.

    Tool Count5/5

    8 tools is well-scoped for a design system canonical server. Each tool addresses a distinct need (querying, detail lookup, dependency analysis, conventions, drift checking) and none feel redundant or unnecessary.

    Completeness5/5

    The tool surface comprehensively covers the design system domain: token and component listing/detail, deprecation info, reverse dependencies, conventions, and code drift detection. For a read-only reference server, the coverage is complete and leaves no obvious dead ends.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues