Skip to main content
Glama
mrityunjay-tiwari

ui-registry-mcp

by mrityunjay-tiwari
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to ui-registry-mcp

No user-submitted related servers found.

    Related Servers

    • shadcn-ui-mcp-server

      EzequielPereirae
      A
      license
      A
      quality
      D
      maintenance
      Provides AI assistants with comprehensive access to shadcn/ui v4 components, blocks, demos, and metadata across React, Svelte, Vue, and React Native, enabling efficient component integration and code generation.
      2
      10
      2,896 npm
      MIT

    • UIShelf MCP Server

      SH20RAJ
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to search across 340+ React UI registries, inspect component code and quality scores, compare options, detect a project's stack, and generate or execute safe transactional install plans. It provides read and write safeguards with dry-run planning and rollback.
      1
      MIT

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

    A4.4/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: listing registries, searching components, fetching full component source, comparing alternatives across libraries, and checking design consistency. No two tools overlap in functionality.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with underscores (e.g., list_registries, search_components, get_component, compare_components, check_consistency). There is no mixing of naming conventions.

    Tool Count5/5

    With 5 tools, the surface is well-scoped for the server's purpose: discover libraries, search and retrieve components, compare options, and validate consistency. Each tool earns its place without being excessive or insufficient.

    Completeness5/5

    The tool set covers the full workflow from listing registries to searching, retrieving, comparing, and checking consistency. There are no obvious gaps for the intended use case of exploring and integrating UI components from multiple registries.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources