Skip to main content
Glama
hangboss1761

idux-ui-mcp

by hangboss1761
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to idux-ui-mcp

No user-submitted related servers found.

    Related Servers

    • Ruixen MCP Server by ruixenui

      Ruixen MCP Serverofficial

      ruixenui
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to discover, search, and retrieve Ruixen UI components from the live registry, providing installation commands for MCP-compatible clients.
      3
      8 npm
      1
      MIT

    • Ant Design MCP Server

      leonwgc
      A
      license
      A
      quality
      D
      maintenance
      Provides access to Ant Design component library documentation and information for automated code generation. Enables searching components by category or keyword, retrieving component props, examples, API documentation, and available icons.
      6
      4 npm
      ISC
    • Taiga UI MCP Server by taiga-family

      Taiga UI MCP Serverofficial

      taiga-family
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides AI assistants with comprehensive access to Taiga UI components, enabling retrieval of component documentation, code examples, and migration guides via four MCP tools.
      3,150 npm
      15
      Apache 2.0

    • shadcn-ui MCP Server

      ymadd
      A
      license
      A
      quality
      D
      maintenance
      Helps AI assistants access shadcn/ui component documentation and examples through a TypeScript-based MCP server that provides reference information for component details, usage examples, and search capabilities.
      4
      876 npm
      60
      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

    B3.3/5.0

    Scored across 5 tools

    Disambiguation4/5

    Tools target distinct operations: listing all components, searching by keyword, retrieving details, retrieving examples, and cache maintenance. list_idux_components and search_components have some overlap since search can also return component lists, but descriptions clarify. An agent could occasionally confuse when to list versus search.

    Naming Consistency4/5

    Names mostly follow verb_noun snake_case (list_idux_components, get_component_details, get_component_examples, search_components, update_components_cache). Minor deviations: list_idux_components embeds 'idux' while others do not, and singular/plural varies (component vs components). Still readable and largely consistent.

    Tool Count5/5

    Five tools are well-scoped for a component documentation MCP: discovery, detail, examples, search, and cache refresh. Each has a clear role with no bloat or missing essentials. The count fits the narrow domain perfectly.

    Completeness4/5

    Core lifecycle for component lookup is covered: list/search, details, examples, and cache update. Minor gap: no explicit version listing or selection despite 'default Vue3' mentions, but agents can likely pass arguments or work around it.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources