Skip to main content
Glama
sam-rubinstein

frontend-design-mcp

by sam-rubinstein
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to frontend-design-mcp

No user-submitted related servers found.

    Related Servers

    • ds-directory-mcp

      NoWorries
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables intent-based semantic search over external design system documentation, allowing MCP-compatible AI assistants to retrieve relevant design tokens, component architectures, and code patterns via a single tool.
      -

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

    • UI System Selector MCP

      MossaJehad
      A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents to discover, compare, select, and enforce design systems and component libraries, with installation guidance, component APIs, and strict adherence directives to prevent default substitutions.
      10
      MIT

    • Design-Code Registry MCP

      mrasadi
      A
      license
      A
      quality
      C
      maintenance
      Maps design components, tokens, and patterns to their code implementations, providing AI coding agents with exact-match resolution across any design tool and framework. Enables agents to reliably discover and reuse existing components across React, Vue, Flutter, SwiftUI, and more.
      20
      MIT
    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

    A4.2/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools have clearly distinct roles: search, install, project-state, and update-checking are well separated. The only soft spot is get_project_design vs get_design, since both involve DESIGN.md content, though one summarizes the local project file and the other fetches design documents/sections.

    Naming Consistency5/5

    Every tool uses a consistent lowercase snake_case verb_noun pattern (get_*, list_*, search_*, install_*, check_*). The get_design_* family is predictable and makes related read operations easy to group.

    Tool Count5/5

    Eight tools is a well-scoped size for a design-system MCP: enough to cover discovery, inspection, installation, and upkeep without redundancy or bloat.

    Completeness4/5

    The core lifecycle—search, inspect, install, check local state, and monitor updates—is covered. There is no explicit uninstall or apply-update operation, and local design access is summarized rather than returned in full, so agents may need workarounds for those edge cases.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources