Skip to main content
Glama
vamsiy78

ballmac-ui-mcp

by vamsiy78
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to ballmac-ui-mcp

No user-submitted related servers found.

    Related Servers

    • free-design-registry

      erichon0410-png
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to search a fully local catalog of 21st-style shadcn components via full-text search, inspect individual records, generate reusable build prompts, retrieve install steps, and fetch design tokens for aesthetic keywords. Runs entirely offline over stdio with no API keys, paywalls, or rate limits.
      Apache 2.0

    • 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

      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
      5,613 npm
      MIT

    • ui-registry-mcp

      mrityunjay-tiwari
      A
      license
      A
      quality
      D
      maintenance
      Provides coding agents live access to shadcn-style component registries, enabling them to search, compare, and fetch real component source code for UI composition.
      5
      119 npm
      5
      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

    A3.7/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (list_items vs get_item vs compose_page). The only mild overlap is between list_items, list_categories, and search_items, plus get_item vs get_examples, but the descriptions clarify the boundaries (browse vs filter-by-category vs need-based search, full detail vs examples only).

    Naming Consistency5/5

    All eight tools follow a consistent snake_case verb_noun pattern (get_examples, list_items, list_categories, search_items, get_item, get_install_command, compose_page, get_setup). No mixed conventions or vague verbs.

    Tool Count5/5

    Eight tools is well-scoped for a UI component registry, covering discovery, detail, install and composition without bloat. Each tool earns its place.

    Completeness4/5

    The surface covers discovery (list/search/categories), inspection (get_item/get_examples), setup, install and page composition—a coherent read-only lifecycle for a component catalog. Minor gaps like versioning or license-status checks exist but are workable.

    Resources