Skip to main content
Glama
tsubotax

melta-ds-mcp

by tsubotax
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to melta-ds-mcp

No user-submitted related servers found.

    Related Servers

    • WunderUI MCP by Kl-webmedia

      WunderUI MCPofficial

      Kl-webmedia
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to build UI with a design system's tokens, component inventory and prop signatures, page templates, and starter snippets, while tracking free/pro availability and live-updating design data.
      1,151 npm
      1
      MIT

    • 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.
      4 npm
      MIT

    • Better Design

      marvkr
      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.
      507
      MIT

    • design-md-mcp

      tingowiggle
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI coding agents to query any DESIGN.md design system and receive short, targeted answers with exact design tokens, existing component classes, markup examples, and rules. It also catches drift by flagging made-up colors and pixel values and suggesting the nearest token.
      1
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.8/5.0

    Scored across 6 tools

    Disambiguation4/5

    Most tools target distinct objects (get_component, get_token, search) with clear boundaries, but check_rule, check_html, and get_rules form a cluster around prohibition rules. The descriptions do distinguish them (apply to class strings vs. full HTML vs. retrieve raw rules), so an agent can reasonably select correctly.

    Naming Consistency4/5

    Names mostly follow a verb_noun pattern (get_component, get_token, get_rules, check_rule, check_html), with only 'search' as a bare verb deviation. Still highly predictable and consistent in style.

    Tool Count5/5

    Six tools is well-scoped for a design-system lookup and validation server. Each tool serves a distinct purpose (component metadata, tokens, search, three rule-checking variants) with no obvious filler.

    Completeness4/5

    The surface covers the core read-only lifecycle: discover (search), inspect (get_component/get_token), and validate (check_rule/check_html/get_rules). Only minor gaps exist, e.g. no explicit list-components or list-tokens endpoint, though search largely covers discovery.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources