quasar-docs-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| quasar_get_componentA | Get documentation for a specific Quasar UI component. Returns the full markdown documentation including API reference, props, events, slots, methods, and usage examples. Args:
Returns: For markdown: Full component documentation with API details For JSON: { "component": string, // Original input "normalized_name": string, // Resolved component name "path": string, // File path in docs "url": string, // Quasar.dev URL "content": string, // Documentation content "truncated": boolean // Whether content was truncated } Examples:
Errors:
|
| quasar_get_pageA | Get any Quasar documentation page by its path. Use this for non-component documentation like style guides, plugins, CLI docs, getting started guides, etc. Args:
Returns: For markdown: Full page content with documentation For JSON: { "requested_path": string, // Original path input "resolved_path": string, // Actual file path found "url": string, // Quasar.dev URL "content": string, // Page content "truncated": boolean // Whether content was truncated } Examples:
Errors:
|
| quasar_search_docsA | Search the Quasar documentation for topics, components, or features. Returns a list of matching pages with titles, paths, sections, URLs, and relevance scores. Supports section filtering, pagination, and optional deep content search. Args:
Returns: For markdown: Formatted list with titles, sections, paths, URLs For JSON: { "query": string, "section": string | undefined, "total": number, // Total matches found "count": number, // Results in this response "offset": number, // Current offset "limit": number, // Requested limit "has_more": boolean, // More results available "next_offset": number, // Offset for next page "results": [ { "title": string, "path": string, "section": string, "url": string, "snippet": string, // Context around match "score": number // Relevance score } ] } Examples:
Errors:
|
| quasar_list_sectionsA | List all available Quasar documentation sections, or list pages within a specific section. Use this to discover what documentation is available and navigate the docs structure. Args:
Returns: When listing all sections (no section parameter): For markdown: Formatted list of sections with titles, descriptions, and page counts For JSON: { "total_sections": number, "sections": [ { "name": string, // Section identifier (e.g., 'vue-components') "path": string, // URL path "title": string, // Human-readable title "description": string, // Section description "page_count": number // Number of pages in section } ] } When listing pages in a section: For markdown: List of pages with titles and paths For JSON: { "section": string, "total_pages": number, "pages": [ { "title": string, "path": string, "url": string } ] } Examples:
Errors:
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/mamit514/quasar-docs-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server