@quasar/mcp
v1.1.0
Published
MCP server for AI agents: the Quasar documentation and component API, served from the packages installed in your project
Readme

@quasar/mcp
An MCP server that gives AI agents the Quasar documentation and component API of the exact versions installed in your project.
The documentation pages ship inside the quasar and @quasar/app-vite packages (in their dist/mcp folder), and the component API inside quasar (dist/api), so the server works offline and always describes what you run. There is no fallback to quasar.dev: a project on releases predating the bundled docs gets the API only, and the server says so.
Setup
Add the server to your MCP client, from the project folder. Nothing gets installed in the project: npx starts the latest release when online and the cached copy when offline (the retries flag keeps that fallback quick):
{
"mcpServers": {
"quasar": {
"command": "npx",
"args": ["-y", "--fetch-retries=0", "@quasar/mcp@latest"]
}
}
}The server serves the project it is started in. Clients that start servers elsewhere can point it at the project with --project <dir>. Started at the root of a workspace that holds several Quasar apps, it serves all of them: the tools take an app argument naming one, and default to the first app found.
See the AI Agents page for the per-client instructions.
Tools
| Tool | What it returns |
| --------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
| list_pages | every page available offline with its approximate size, grouped by the package shipping it |
| search_docs | the pages matching some keywords, with their description, approximate size and the sections the keywords occur in |
| get_page | one page, one section of it (by heading, or the #anchor of a pasted link), or its outline, as markdown |
| list_api | the names of the API descriptors: components, plugins, directives, utilities |
| get_api | the props, slots, events and methods of one of them, one part, or one member, as the site shows them; format: "json" for the raw descriptor |
| check_updates | whether newer releases of quasar, @quasar/app-vite or this server exist |
At session start the server also tells the agent which package versions it serves, the other apps of a workspace and their versions, what is missing, and which updates are available (checked in the background, cached for a day, never while offline, the same mechanism the Quasar CLI uses; NO_UPDATE_NOTIFIER disables it).
Chat Support
Ask questions at the official community Discord server: https://chat.quasar.dev
Community Forum
Ask questions at the official community forum: https://forum.quasar.dev
Contributing
I'm excited if you want to contribute to Quasar under any form (report bugs, write a plugin, fix an issue, write a new feature). Please read the Contributing Guide.
Semver
Quasar is following Semantic Versioning 2.0.
The documentation slices the packages ship (dist/mcp) carry a format number in their meta.json. It moves only when the shape the server parses changes, and this server's major version tracks it: @quasar/mcp@1 reads format 1. A project whose installed packages carry another format is told so at session start, with the server to run instead.
License
Copyright (c) 2026-present Razvan Stoenescu
