Skip to main content
Glama
kunalgoesbyken

VengeanceUI MCP Server

by kunalgoesbyken
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to VengeanceUI MCP Server

No user-submitted related servers found.

    Related Servers

    • Grafana UI MCP Server by grafana

      Grafana UI MCP Serverofficial

      grafana
      A
      license
      C
      quality
      D
      maintenance
      Provides AI assistants with comprehensive access to Grafana's React component library, including TypeScript source code, MDX documentation, Storybook examples, test files, and design system tokens for building Grafana-compatible interfaces.
      1
      75 npm
      9
      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.
      10
      8,219 npm
      MIT

    • kodza

      kodza-dev
      F
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to search a catalogue of plain HTML, CSS and JavaScript UI components and fetch each one's exact files, settings and framework integration instructions. Lets users add production-ready interface components by asking in natural language.
      2
      2
      -
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A4/5.0

    Scored across 7 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, but get_component_info and get_component_code both target a specific component, which could cause confusion. However, the descriptions clarify that one returns metadata and the other returns source code, so the ambiguity is minor.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (list_components, search_components, get_component_code, get_components_by_category, etc.), making the naming predictable and easy to learn.

    Tool Count5/5

    With 7 tools, the server is well-scoped for a component library. Each tool serves a distinct function, and the count is within the ideal range for a focused MCP server.

    Completeness5/5

    The tool set covers the full lifecycle for a read-only component library: listing, searching, retrieving code and info, browsing by category, listing categories, and cache refresh. No obvious functional gaps exist.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources