Skip to main content
Glama
Zoot01

coss-ui-mcp

by Zoot01
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to coss-ui-mcp

No user-submitted related servers found.

    Related Servers

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

    • @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
    • @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

    • Insider Design System MCP

      denizzeybek-fe
      F
      license
      B
      quality
      D
      maintenance
      Automated MCP server for the Insider Design System. Enables AI assistants to discover, understand, and generate code for over 60 Design System components with automated extraction from source code.
      14
      -

    • ds-mcp

      aestheticfunction
      A
      license
      Not graded
      quality
      A
      maintenance
      A read-only MCP server that provides AI coding agents with a queryable contract for design system tokens, components, patterns, and anti-patterns.
      12 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

    A4.3/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: listing all components, searching for specific ones, getting detailed docs for a component, getting overview docs, planning a UI with recommendations, and fetching theme info. No overlap in functionality, and descriptions guide appropriate use.

    Naming Consistency4/5

    Tools follow a 'coss_<verb>_<noun>' pattern for most (get_component, get_doc, list_components), but three tools use a single verb without a noun (plan, search, theme). While readable and prefixed consistently, the lack of uniform verb-noun structure slightly reduces predictability.

    Tool Count5/5

    With 6 tools covering exploration, search, detailed documentation, planning, and theming, the count is well-scoped for a UI component library reference server. Each tool provides essential functionality without unnecessary redundancy.

    Completeness5/5

    The tool set covers the full lifecycle of using the component library: discovering (list, search), understanding (get_component, get_doc), planning (plan), and styling (theme). No obvious gaps for a read-only reference MCP server.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources