Skip to main content
Glama
jeremysykes

component-contracts

by jeremysykes

Related Servers

Alternatives to component-contracts

No user-submitted related servers found.

    Related Servers

    • 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.
      3 npm
      9
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Design system MCP server. 20 tools: extract design tokens from any URL, pull from Figma or Penpot, generate React + shadcn/ui components from specs, run WCAG audits, sync tokens bidirectionally.
      50
      123 npm
      46
      MIT
    • 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
      2 npm
      MIT
    • 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.
      10 npm
      1
      Apache 2.0
    • A
      license
      A
      quality
      F
      maintenance
      Comprehensive MCP server for end-to-end UI development, offering tools to generate components, manage design tokens, audit accessibility, autofix issues, inspect live pages, compare screenshots, and more across multiple frameworks.
      13
      11 npm
      MIT
    • 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.7/5.0

    Scored across 4 tools

    Disambiguation3/5

    get_primitive overlaps with get_composition_pattern and get_caveats since it already returns composition patterns and caveats. However, get_composition_pattern is scoped to component types rather than primitives, and get_caveats is more targeted, so descriptions help somewhat, but the boundaries remain fuzzy.

    Naming Consistency5/5

    All tools follow a consistent verb_noun snake_case pattern: list_primitives uses 'list' and the others use 'get', which is a predictable and uniform convention. There are no mixed styles or ambiguous verbs.

    Tool Count4/5

    Four tools is a reasonable size for a focused server, but two of them (get_composition_pattern, get_caveats) largely duplicate what get_primitive already provides, so the count feels slightly padded rather than perfectly lean.

    Completeness4/5

    The set covers listing primitives and retrieving detailed contract information, which serves the stated purpose. A minor gap is the lack of a dedicated tool for just the API or accessibility contract, but get_primitive essentially covers this in aggregate, so no critical dead ends exist.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues