Skip to main content
Glama
dgesteves

design-system-mcp

by dgesteves
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to design-system-mcp

No user-submitted related servers found.

    Related Servers

    • weave-design-system-mcp

      avcs06
      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

    • Better Design

      marvkr
      A
      license
      A
      quality
      B
      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.
      48
      538
      MIT

    • tavero mcp

      baccaraaa
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to read a React app's design-system context, scan for UI drift in buttons, cards, colors, and spacing, retrieve findings with file:line evidence and expected tokens, and verify fixes by rescanning affected routes.
      0
      3
      MIT
    • @lando-labs/lando-ds-mcp by lando-labs

      @lando-labs/lando-ds-mcpofficial

      lando-labs
      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
      7 npm
      1
      Apache 2.0

    • melta-ds-mcp

      tsubotax
      A
      license
      A
      quality
      B
      maintenance
      It lets AI coding agents look up design tokens, component specifications, and prohibition rules on demand, then validate generated HTML or JSX with the same lint logic used by CI and editor hooks so violations are caught and corrected immediately. It also exposes the design constitution and rule sets as resources for reference during generation.
      6
      103 npm
      202
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A4.3/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool occupies a clearly distinct niche: list_components (exhaustive catalog), get_component (single contract), search_components (intent-based discovery), get_tokens (token values), and check_ui (lint/validation). The list vs. get vs. search trio mirrors a well-understood pattern, and the descriptions explicitly state when to use each, so misselection is unlikely.

    Naming Consistency5/5

    All names follow a predictable snake_case verb_noun convention (list_components, get_component, search_components, get_tokens, check_ui). Verbs are well-chosen and resource nouns are used consistently across the set.

    Tool Count5/5

    Five tightly scoped tools cleanly cover the design-system consumption lifecycle: discover, inspect, search, read tokens, and validate. Nothing is redundant and nothing feels missing from a count standpoint.

    Completeness4/5

    The surface covers component discovery, contracts, tokens, and linting very well, which are the core consumption workflows. There is a minor gap around overall setup/theming guidance (e.g. provider wiring, global conventions), but agents can work around it via get_tokens and doc examples.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources