Official MCP Server for Quasar Framework — AI-Powered Docs Access

[ICTLAYER]

Please read

I'd like to propose the creation of an official Model Context Protocol (MCP) server for Quasar Framework — similar to what MUI has recently shipped with @mui/mcp.

---

My Observation

When developers ask AI assistants questions about Quasar components, directives, plugins, or CLI modes, the answers often:

• Reference outdated APIs (e.g., Quasar v1 patterns in a v2 project)
• Hallucinate non-existent props or events
• Link to 404 documentation pages
• Miss Quasar-specific patterns (e.g., quasar.config.js, Boot Files, Notify, QTable slots)

This erodes developer trust and slows down productivity — especially for newcomers who don't yet know what's right vs. wrong.

---

The Proposal

Create and publish an official @quasar/mcp package to npm that:

1. Exposes Quasar's documentation (components, directives, plugins, CLI modes, configuration) as MCP tools
2. Supports major AI coding environments out of the box:
   • VS Code (GitHub Copilot / Agent mode)
   • Cursor
   • Windsurf
   • JetBrains IDEs
   • Claude Code
   • Zed
3. Covers the full Quasar ecosystem, including:
   • All UI components (QBtn, QTable, QDialog, etc.)
   • Quasar CLI (quasar.config.js, Boot Files, SSR, PWA, Electron, Capacitor modes)
   • Composables & plugins (useQuasar, Notify, Dialog, Loading, etc.)
   • SASS variables, theming, and dark mode
   • App Extensions

---

Example Setup (Proposed)

VS Code / Antigravity / Trae IDE / Cursor / Windsurf etc

"mcpServers": {
  "quasar-mcp": {
    "type": "stdio",
    "command": "npx",
    "args": ["-y", "@quasar/mcp@latest"]
  }
}

Claude Code

claude mcp add quasar-mcp -- npx -y @quasar/mcp@latest

---

Why This Matters

• 🚀 Improved developer experience — Accurate AI answers with citations to real Quasar docs
• 🧠 Better onboarding — New Quasar users get trustworthy guidance from day one
• 🔗 No broken links — Tools only reference docs that actually exist
• 🌍 Positions Quasar as AI-ready — Alongside frameworks like MUI, Quasar would be among the first Vue-based frameworks with an official MCP integration
• 🤝 Community contribution opportunity — The MCP server could be maintained as a separate community-driven package under the quasarframework org

---

Prior Art

• MUI MCP — @mui/mcp (React)
• Model Context Protocol Spec

---

Questions for the Team

• Is there interest from the core team in maintaining this officially?
• Could this be a community-driven package under the quasarframework GitHub org?
• Would the existing quasar.dev docs structure lend itself to being scraped/indexed for MCP tooling?

I'm happy to contribute to an initial prototype if there's interest. 🙌

[yusufkandemir]

Hi there. Thanks for the proposal.

About 11 months ago, I started the initial efforts towards AI. My first aim was to create a readable/processed markdown version of the docs, since the source markdown files lack JSON API, examples, etc., which are added after some processing and turned into HTML and served via the docs site. Which means there is no easy/proper way of feeding relevant info into the AI context.
After all this time, a lot has changed. So, now on top of this idea, I want to also explore creating MCP, agent skill(s), etc., to provide an even better experience. However, I need some time to get back into it, research, think, make tests, etc. I'll first start with reviving my attempts at creating the markdown processing pipeline. So, I'll let this discussion serve as some sort of placeholder and hope to get back to it in the following weeks.

[tavaresgerson]

Hi! I hope you're all doing well.

I created a script that generates readable documentation for LLMs in markdown - you can view it here https://github.com/tavaresgerson/quasar-llm/releases/tag/v2.19.3

It's been working for me using Junie/Jetbrains.

There's an index.md file where you can access all the files.

[jeka-kiselyov]

Hi there.

I built a library that combines a component showcase (Quasar components + optional custom ones, kind of like Storybook for apps) with an MCP server. It shares logic between both and pulls Quasar component definitions directly from the Quasar package on the fly.

https://github.com/jeka-kiselyov/varmory

It fits my use cases really well ( speeding up Quasar + Claude for fresh projects, or reusing custom set of components/theme in other projects ), maybe someone else will find it useful too, have some ideas to improve there, or want to fork and adjust it.