Skip to main content
Glama
Davont

my-design MCP Server

by Davont
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to my-design MCP Server

No user-submitted related servers found.

    Related Servers

    • @sorb/tap

      metatoy
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for design tokens that gives AI agents read access to design systems, enabling token resolution, listing, and component usage lookups via natural language.
      MIT

    • @dsk/mcp

      rabindranath1311
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that gives AI assistants structured access to a design system's tokens, components, guidelines, and patterns, enabling them to read, lint, and author design system data.
      1
      MIT

    • ds-pilot

      lyse-labs
      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

    • BrixUI MCP Server

      multicomak
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that connects AI clients to Figma components, design tokens, and variables from the BrixUI Design System, enabling component browsing, searching, and token retrieval.
      4
      5 npm
      MIT
    • @lando-labs/lando-ds-mcp by lando-labs

      @lando-labs/lando-ds-mcpofficial

      lando-labs
      A
      license
      A
      quality
      A
      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
      6 npm
      1
      Apache 2.0

    • @deay/mcp

      njirolu
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server providing AI assistants with comprehensive documentation about @deay/ui components, including props, examples, best practices, and Figma design specifications.
      -
    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

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: changelog_query handles version history, component_details provides API documentation, component_examples offers code samples, component_list enumerates components, component_search finds components, and theme_tokens covers design tokens. The descriptions explicitly differentiate their roles, making misselection unlikely.

    Naming Consistency5/5

    All tool names follow a consistent snake_case pattern with a clear 'noun_noun' or 'noun_verb' structure (e.g., changelog_query, component_details). This predictability helps agents easily parse and understand the tool set without confusion from mixed conventions.

    Tool Count5/5

    With 6 tools, this server is well-scoped for its purpose of supporting a design system (my-design). Each tool earns its place by covering essential aspects like documentation, examples, listing, search, changelogs, and themes, avoiding bloat while providing comprehensive coverage.

    Completeness5/5

    The tool surface is complete for the domain of a design system, covering CRUD-like operations: component_list and component_search for discovery, component_details for detailed API info, component_examples for implementation, changelog_query for version management, and theme_tokens for styling. No obvious gaps exist for core workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources