QuasarUI MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| QUASARUI_ACCESS_KEY | No | Your QuasarUI Access Key. Optional: without it, only Free Components are available. With a valid key (All Access or Blocks Pro account) Paid Components are available too. For HTTP clients the key is instead passed as an "Authorization: Bearer YOUR_ACCESS_KEY" header. A wrong, revoked or malformed key returns 401 and never falls back to Free Components. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_componentA | Get a Component's full Vue SFC source by slug. Free Components return their source to anyone; a Paid Component without access returns an upgrade message with the pricing URL instead. |
| get_setup_guideA | How to set up Quasar (Quasar CLI, Nuxt or Vite) and paste a QuasarUI Component into a project, including the icon sets the Components need. |
| list_blocksA | List every QuasarUI Block (a group of related Components, e.g. pricing-sections) with its tags, how many Components it has, how many are Free, and its page URL. |
| list_componentsA | List the Components of one Block, each with "access": "free" (source available to anyone) or "paid" (needs All Access or Blocks Pro). |
| search_componentsA | Search Components by a plain-language query, e.g. "pricing table with a monthly/yearly toggle" or a slug. Returns up to 20 matches, best first, each with its Free or Paid access. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.