QuasarUI MCP Server
OfficialRelated Servers
Alternatives to QuasarUI MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseAqualityBmaintenanceEnables 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.22-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to access documentation of Vue UI components, including props, events, and slots, for generating correct usage code.7MIT
- 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.105,254 npmMIT
- FlicenseNot gradedqualityDmaintenanceExposes SigmaUI Design System components to AI assistants, providing tools for component documentation, search, usage examples, and design tokens to accelerate Vue 3 and Nuxt 3 UI development.-
- AlicenseBqualityCmaintenanceEnables AI assistants to search, understand, and retrieve UI components from ui-layouts.com through tools like search, documentation, metadata, and source code access.461 npm34MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI coding assistants to search, discover, and retrieve UI HUB components, source code, dependencies, templates, and animations via MCP.-
TDQS
Scored across 5 tools
Each tool has a clearly distinct role: browsing blocks, browsing components within a block, searching components, retrieving source, and setup guidance. There is no meaningful overlap between list_components and search_components because one is hierarchy-based and the other is query-based.
All tool names use snake_case and follow a predictable verb_noun pattern: get_*, list_*, and search_*. The convention is consistent across the entire small set.
Five tools is well scoped for a component catalog server. Each tool provides a distinct browsing or retrieval capability without redundant operations.
The surface covers the core workflow: discover blocks, list components, search, fetch source, and get setup instructions. Minor gaps could include a direct list-all-components operation or richer block detail retrieval, but agents can work around these via search and list_components.