Vuetify MCP

Limits

• No filesystem or repository access. Nothing in the 31 schemas reads, writes or scans a local project. When Vuetify's docs suggest prompting an agent to "scan this repo for Vuetify 3 patterns that break in v4", the scanning is done by your coding agent's own file tools; this connector supplies only the breaking-change list.
• Ten tools need a paid subscription. Every Vuetify One tool description states that use requires a Vuetify One subscription. Without one, the usable surface is the 21 documentation tools.
• Five write tools carry no readOnlyHint. They affirm destructiveHint: true and say nothing on the read-only axis. Absent is not false — see the annotations section above.
• Bins default to public and link slugs to global. The create_vuetify_bin schema's visibility defaults to public; create_vuetify_link's scoped defaults to false, reserving the slug globally. Both are avoidable only by supplying the parameter explicitly.
• Nothing deletes, and nothing rolls back. There is no delete tool for bins, playgrounds or links, and no version history.
• Claude Desktop cannot use the hosted URL. Per Vuetify's docs, that client is stdio-only. Use the mcp-remote bridge or the local package.
• The upgrade path enum is three values. get_upgrade_guide accepts v1.5, v2.7 and v3 as source versions. Migrations from other starting points are not covered by that tool.
• Two schema statements about v0 composable categories disagree. The get_vuetify0_composable_list description names nine categories; the get_vuetify0_composable_guide category enum lists ten, adding semantic. Trust the enum, since it is what the server validates against.
• The MCP privacy policy could not be read. The URL in Anthropic's directory entry is served by a single-page app that returns its shell for every path, so no policy text was retrievable by our client. We make no claim about what the hosted server logs or retains. See Sources.
• The GitHub README lags the deployed server. It documents a tool named get_available_features that the live server does not expose, states Vuetify 3.x compatibility without mentioning the v4 tools that are live, and omits the Vuetify One tools entirely. The docs site is current; the README is not.
• We did not exercise any tool. Our check was a read-only initialize and tools/list handshake. Every capability described above comes from the server's own tool descriptions and schemas plus Vuetify's published documentation — not from calling anything.
• Self-hosted deployments are out of scope. This page describes the hosted endpoint only.

Frequently asked questions

Sources

• Vuetify MCP documentation (retrieved 2026-08-17; HTTP 200, zero redirects). This is the documentation URL in Anthropic's directory entry, and it is live and current — the 0. host is Vuetify's Vuetify0 documentation site, not a preview or a redirect. Source for the 31-tool count, the public-versus-Vuetify-One split, the Claude Desktop stdio constraint and its mcp-remote workaround, the per-client setup blocks, the interactive configurator, the do-not-paste-an-API-key instruction, the example prompts and the llms.txt comparison. Clean Markdown is served by appending .md to the page URL, advertised in the host's own robots.txt. · retrieved 2026-08-17
• Vuetify0 AI tools page (retrieved 2026-08-17; HTTP 200, zero redirects). Source for the relationship between the MCP server and Vuetify's llms.txt, llms-full.txt and SKILL.md bundles. · retrieved 2026-08-17
• vuetifyjs/mcp repository README (retrieved 2026-08-17; HTTP 200). MIT licensed. Source for the local and self-hosted transports, the CLI arguments and the VUETIFY_API_KEY option for non-hosted setups. It also disagrees with the live server — it documents get_available_features, which tools/list does not return, and predates the v4 and Vuetify One tool groups. Where they differ, the live handshake wins. · retrieved 2026-08-17
• npm registry — and (retrieved 2026-08-17). Source for the statement that Vuetify 4 is current: latest resolved to 4.1.9, with v3-stable at 3.13.1 and v2-stable at 2.7.2. The @vuetify/mcp package is the same server, published by Vuetify. · retrieved 2026-08-17
• Server OAuth descriptors — and (retrieved 2026-08-17; HTTP 200 each). The server's own RFC 9728 declaration: resource https://mcp.vuetifyjs.com/mcp, authorisation server https://api.vuetifyjs.com, scope mcp, bearer token in a header, authorisation code grant with PKCE S256 and dynamic client registration. · retrieved 2026-08-17
• Vuetify MCP privacy policy — — content not retrieved. The directory's value 308-redirects to this trailing-slash URL, which returns HTTP 200; the destination is cited here. The host is a single-page app that returns an identical 1,532-byte HTML shell for *every* path, including paths that do not exist, so a 200 proves nothing about the page. A browser-based fetch returned the document title and no policy body. No claim is made on this page about the server's data handling.
• robots.txt — and (retrieved 2026-08-17; HTTP 200 each). Both are User-agent: * with Allow: /. Neither carries a Content-Signal line, so no AI-use preference is expressed either way. The Vuetify0 file goes further and advertises its machine affordances — llms.txt, llms-full.txt, SKILL.md and the per-page .md suffix — describing them as curated documentation for AI assistants. · retrieved 2026-08-17
• Live initialize and tools/list handshake against https://mcp.vuetifyjs.com/mcp — 31 tools with descriptions, input schemas and annotations, returned to an anonymous request (2026-08-17). Source for every tool name, the three annotation shapes, the parameter enums, the schema defaults and the subscription sentences in the Vuetify One tool descriptions. · retrieved 2026-08-17
• Anthropic Connectors Directory entry (listed 2026-08-14; snapshot taken 2026-08-16; the directory app returns HTTP 403 to an unauthenticated fetcher, so these values come from the committed snapshot rather than the rendered page). Source for the partner tier, the endpoint, the streamable-HTTP transport, the developer-tools and productivity categories and the Vuetify authorship. Its 31 tool_names match the live handshake exactly — no drift in either direction, which is unusual enough in this catalogue to be worth stating. · retrieved 2026-08-14