VengeanceUI MCP Server
Related Servers
Alternatives to VengeanceUI MCP Server
No user-submitted related servers found.
Related Servers
AlicenseCqualityDmaintenanceProvides 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.163 npm9MIT- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to retrieve NHS.UK frontend component templates, styles, macro options, and usage examples directly from the source repository.12 npm1MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to retrieve React, Svelte, Vue, and React Native component source code, demos, blocks, and metadata for building UIs in AI-powered development workflows.107,053 npmMIT
- AlicenseAqualityDmaintenanceProvides 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.2107,053 npmMIT
- FlicenseAqualityDmaintenanceProvides AI assistants with direct access to shadcn/ui components and blocks, enabling real-time fetching of component source code, documentation, and implementation examples.432 npm4-
- AlicenseAqualityCmaintenanceProvides AI coding assistants with on-demand access to component specs, test scenarios, accessibility requirements, and build guides from the Web UI Component Specification.10MIT
TDQS
Scored across 7 tools
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.
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.
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.
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.