Base44
Build and edit Base44 apps from an AI assistant, and query data your app's users submit.
Give a coding agent version-accurate Vuetify component APIs, install guides and v3-to-v4 migration notes.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Vuetify MCP server connects the official Vuetify documentation to Claude, ChatGPT and any MCP-compatible agent. Its 31 tools return component and directive APIs at a version you name, installation guides for eight platforms, feature guides, release notes and v3-to-v4 migration detail. Twenty-one need no sign-in; ten reach Vuetify One and require a subscription.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Download and cache Vuetify API types by version
Return the API list for a Vuetify component
Return the API information for a Vuetify directive
Get detailed information about how to install Vuetify in a variety of environments.
Get a list of available features in the documentation.
Get the information about a specific feature in the documentation.
Get a list of exports from the Vuetify npm package
Get a list of frequently asked questions about Vuetify.
Get release notes for one or more versions of Vuetify.
Get the README contents for @vuetify/one package from GitHub, including installation and usage instructions.
Get the upgrade guide for migrating between Vuetify major versions (v1.5→v2, v2.7→v3, v3→v4).
Get Vuetify 4 breaking changes, optionally filtered by category. Returns migration guidance for each change.
Get the README contents for @vuetify/v0 (Vuetify0) package from GitHub, including installation and usage instructions for this headless meta-framework.
Get the package-specific documentation for @vuetify/v0 from GitHub.
Get a comprehensive list of all 71 composables available in @vuetify/v0, organized by category (foundation, registration, selection, forms, system, plugins, data, reactivity, transformers).
Get a list of all 40 headless components available in @vuetify/v0.
Get detailed documentation and source code for a specific @vuetify/v0 composable.
Get detailed documentation and source code for a specific @vuetify/v0 component.
Get a list of all subpath exports available in @vuetify/v0 (utilities, types, constants, date, data-table, palettes, theme, locale, logger, and more).
Get the latest SKILL.md reference for @vuetify/v0 — a compact guide with patterns, anti-patterns, and common mistakes optimized for AI coding assistants.
Generate a link to the Vuetify issues site with the repository and bug report type pre-selected.
Create a Vuetify bin. Use of this tool requires a vuetify one subscription
Get all user bins. Use of this tool requires a vuetify one subscription
Update an existing Vuetify bin. Use of this tool requires a vuetify one subscription
Get a bin by ID. Use of this tool requires a vuetify one subscription
Create a Vuetify short link (vtfy.link). Use of this tool requires a vuetify one subscription
Get all user links. Use of this tool requires a vuetify one subscription
Create a Vuetify playground. Content should be a Vue SFC. Use of this tool requires a vuetify one subscription
Get all user playgrounds. Use of this tool requires a vuetify one subscription
Update an existing Vuetify playground. Use of this tool requires a vuetify one subscription
Get a playground by ID. Use of this tool requires a vuetify one subscription
Read from the server on 2026-08-17, including each tool's own safety annotations.
readOnlyHint. They affirm destructiveHint: true and say nothing on the read-only axis. Absent is not false — see the annotations section above.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.mcp-remote bridge or the local package.get_upgrade_guide accepts v1.5, v2.7 and v3 as source versions. Migrations from other starting points are not covered by that tool.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.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.resources/list returned 78 URIs, names and MIME types on 2026-08-19; no resource body was fetched, and the install-vuetify prompt template was not retrieved either. The count is also a moving target — an internal table recorded 61 on 2026-08-18 — and some version tokens in the URIs (0, 1SSl) are malformed in ways we did not investigate.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.Not for documentation. We opened an anonymous handshake against the endpoint on 2026-08-17 and the server returned all 31 tool definitions without a credential. Vuetify's own docs state that documentation and API tools need no login. The ten Vuetify One tools are different: their descriptions say each requires a Vuetify One subscription, and the server publishes an OAuth descriptor for that path.
Because Claude Desktop only accepts stdio servers. Vuetify's documentation states plainly that direct HTTP transport is not supported in the Claude Desktop configuration file. Use the mcp-remote bridge to consume the hosted server over stdio, or run the package locally with npx. Claude Code, Cursor, Codex and Kimi all take the hosted URL directly.
Any published version, defaulting to the latest. The live schemas for the three API tools all take an optional version string that defaults to latest and accepts a specific release such as 3.0.0. The upgrade guide tool is narrower: its enum offers exactly three source versions, v1.5, v2.7 and v3, so those are the documented migration paths.
No. Nothing in the 31 live schemas touches your filesystem, your repository or your running application. The connector returns documentation, API definitions and migration guidance as text, and your agent decides what to do with it. The only writes it performs are to Vuetify's own hosted services, and those require a Vuetify One subscription.
It builds a URL, nothing more. The tool's own description says it generates a link to the Vuetify issues site with the repository and bug report type pre-selected, and the server annotates it readOnlyHint true. No issue is filed, no GitHub credential is used, and nothing is posted. You still open the link and submit the report yourself.
Bins are. The live create_vuetify_bin schema defaults its visibility parameter to public, so a bin created without an explicit setting is world-readable. Pass private if the snippet contains anything you would not publish. The create_vuetify_link schema has a related default: scoped is false, which reserves your chosen slug globally rather than only within your account.
It is queryable rather than bulk. Vuetify's documentation makes the distinction directly, saying that unlike llms.txt the MCP server is real-time and queryable. An llms.txt bundle is a static snapshot the agent loads wholesale, while a tool call fetches one component API, one guide or one release note at the version you name.
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-17llms.txt, llms-full.txt and SKILL.md bundles. · retrieved 2026-08-17vuetifyjs/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-17latest 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-17https://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-17robots.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-17initialize 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-17prompts/list and resources/list calls against https://mcp.vuetifyjs.com/mcp — 1 prompt and 78 resources, returned to an anonymous request (2026-08-19). Source for the install-vuetify prompt name, the vuetify://api@<VERSION>.json resource URI shape, the application/json MIME type, the per-version naming and the odd version tokens. Names and metadata only — no prompt or resource content was fetched. · retrieved 2026-08-19tool_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-14Connect Vuetify MCP once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.