Skip to main content
Glama
danielbittencourt-bizsaver

Shadcn UI v4 MCP Server

by danielbittencourt-bizsaver
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Shadcn UI v4 MCP Server

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

    • UI HUB MCP Server

      jainil224
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI coding assistants to search, discover, and retrieve UI HUB components, source code, dependencies, templates, and animations via MCP.
      -
    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.7/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools target distinct resources (component, block, theme, repo structure) and actions (get, list, apply). However, get_component, get_component_demo, and get_component_metadata all relate to component details, which could cause slight confusion for an agent deciding which one to call.

    Naming Consistency5/5

    Every tool name follows a consistent snake_case verb_noun pattern: get_component, list_components, apply_theme, etc. The prefixes (get_, list_, apply_) are used uniformly, making the set highly predictable.

    Tool Count5/5

    With 10 tools, the surface is well-scoped for a UI component reference service. Each tool covers a distinct resource or operation without redundancy, fitting comfortably within the ideal 3–15 range.

    Completeness4/5

    The tools cover the core lifecycle: listing and fetching components, blocks, themes, demos, metadata, and applying themes. Minor gaps exist, such as no search/filter for components or blocks and no demo retrieval for blocks, but agents can work around these for the stated purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources