Skip to main content
Glama
denizzeybek-fe

Insider Design System MCP

by denizzeybek-fe
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Insider Design System MCP

No user-submitted related servers found.

    Related Servers

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

    • coss-ui-mcp

      Zoot01
      A
      license
      A
      quality
      C
      maintenance
      MCP server for the coss ui design system, enabling AI agents to fetch components, props, and design tokens on demand for accurate, low-cost code generation.
      6
      1
      MIT

    • Angular Storybook MCP Server

      yeholer-dot
      F
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that brings an Angular design system built on Storybook into AI tools like Claude and Cursor, providing real-time access to component metadata, APIs, and documentation.
      -
    • @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
    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

    B3.4/5.0

    Scored across 14 tools

    Disambiguation3/5

    Most tools have clear verb+object distinctions, but several overlap: get-component versus get-props/get-events/get-examples, get-ds-for-figma versus map-figma-component, and generate-code versus generate-figma-component. Descriptions clarify intent somewhat, but an agent could easily select the wrong tool for a similar task.

    Naming Consistency4/5

    Tool names uniformly follow lowercase snake_case with a verb-object structure (list/get/search/generate/map/validate/convert). Minor inconsistencies like get-ds-for-figma and the pair generate-figma-component versus convert-figma-to-vue slightly break the pattern but remain predictable.

    Tool Count4/5

    14 tools is a reasonable count for a design-system documentation and Figma conversion server. However, some tools feel redundant or consolidatable, such as get-ds-for-figma and map-figma-component, making the set slightly heavier than necessary.

    Completeness4/5

    The server covers component discovery, detailed documentation, props/events/examples, code generation, and Figma mapping/validation/conversion well. Minor gaps like design tokens, theme variables, or component dependency relationships are missing but not critical for the core workflow.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources