Skip to main content
Glama

Related Servers

Alternatives to Sekura Design MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      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
      1 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A design harness for AI coding agents. Better Design gives an agent design systems, UI and UX principles, icons and UI review: it finds or creates a design system that fits the product and installs its components, explains how sign-up, forms and onboarding should work, and reviews finished screens for readability, accessibility and unclear copy.
      252
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables coding agents to access a governed, versioned design style specification through MCP, including deterministic checks, proposal review workflows, and generated CSS, JSON, and TypeScript artifacts.
      Apache 2.0
    • 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.
      17 npm
      1
      Apache 2.0
    • F
      license
      Not graded
      quality
      C
      maintenance
      MCP server that exposes a design system and UX rulebook as tools, enabling AI to generate UI consistent with your design tokens, components, layout rules, accessibility guidelines, and templates. It also provides a review tool to score UI proposals against the design system.
      -

    TDQS

    A3.8/5.0

    Scored across 21 tools

    Disambiguation4/5

    Most tools target clearly distinct resources: specs vs. code (get_component vs. get_component_code), single-pair vs. whole-theme contrast (check_contrast vs. audit_theme), and markup vs. integration validation. A few token tools (get_tokens, export_tokens, suggest_token, get_primitives) sit close together, but the descriptions differentiate them well.

    Naming Consistency4/5

    Strong and predictable get_<noun> pattern across the majority of tools, with coherent list_/validate_/suggest_/export_ prefixes for the non-retrieval operations. Minor deviations: 'search' is a bare verb without a noun, and validation-type tools use three different verbs (validate_, check_, audit_).

    Tool Count4/5

    21 tools is on the heavy side but the design-system domain genuinely spans discovery, components, foundations, tokens, primitives, layouts, patterns, migration, validation, and setup. Nearly every tool earns its place with a distinct artefact or operation.

    Completeness5/5

    Comprehensive lifecycle coverage: discovery (get_overview, search), specifications, code, tokens and primitives, foundations, patterns, layouts, migration guidance, validation, contrast auditing, setup, and exports. No obvious dead ends for an agent building or maintaining a Sekura interface.

    Maintenance

    ActivityActive
    ResponsivenessNo issues