- Home
- Resources
- Integrations
- Vuetify MCP
Claude Vuetify connectorWhat Claude can look up and build with Vuetify.
The Claude Vuetify connector exposes 31 tools. 26 read documentation, APIs and your saved demos, 5 create or update bins, playgrounds and short links, and 0 are undocumented. Below: what needs no account, what needs Vuetify One, and what Claude asks first.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when Claude reads the Vuetify docs live
Instead of answering from whatever it learned during training, Claude can query the current Vuetify documentation: the props, slots and events of a component in a given version, the documented way to install, the breaking changes of a major release. With a Vuetify One sign-in, it can also save a working demo you can share.
Get the API right for the version your project runs. get_component_api_by_version returns a component's props, slots and events, and get_vuetify_api_by_version loads the API types of a release.
Install and migrate the documented way. get_installation_guide covers Vite, Nuxt, Laravel, CDN and more, while get_upgrade_guide and get_v4_breaking_changes list what changes between majors.
Turn an answer into a demo. Once you sign in with Vuetify One, create_vuetify_bin and create_vuetify_playground save an example, and create_vuetify_link shortens its address.
What Claude cannot do: it does not file a bug for you, since create_bug_report only prepares a link to the issues site with the fields pre-selected. The ten bin, playground and link tools stay out of reach without a Vuetify One account. For how assistants and automation tools share the work, the Integrations hub gathers the other families.
Five words before you plug it in
The vocabulary of this page, in one minute.
- Connector
- The link you set up once between Claude and an outside service, so Claude can use that service while it answers you.
- Tool
- One named job a connector hands to Claude. Claude picks the ones it needs mid-answer, and the directory sheet lists them by name.
- Authorization
- The Vuetify One sign-in, needed only for bins, playgrounds and links. Granted once per person, and it can be taken back.
- Approval
- The confirmation Claude waits for before it goes ahead with something that creates or changes content in an account.
- MCP
- The open standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as Vuetify.
Plug the Claude Vuetify connector in, in three steps
- 01
Find Vuetify MCP in your connectors
Open Claude's settings, go to Customize, then Connectors, and search for Vuetify MCP. On a Team or Enterprise workspace, an Owner or Primary Owner switches it on for the organization before members can use it.
- 02
Add it from its row
Click Connect on the Vuetify MCP line. Vuetify says its documentation and API tools work with no account, so you can ask about components right away. If the link breaks later, Disconnect and add it again.
- 03
Sign in only for demos
Creating or updating bins, playgrounds and short links uses a Vuetify One sign-in, not a pasted key. If Vuetify's screen opens, read what it grants before accepting: that screen, not Claude, sets what the access covers.
The 31 tools of the Claude Vuetify connector
Vuetify MCP gives Claude 31 tools: 26 that read your account, 5 that change something in it.
Two groups: what Claude reads, and what it creates or updates. The documentation and API tools are marked read-only by Vuetify's own server. Names stay exactly as Claude shows them.
- 26 read
- 5 write
Tools index
- create_bug_report
- get_all_bins
- get_all_links
- get_all_playgrounds
- get_bin
- get_component_api_by_version
- get_directive_api_by_version
- get_exposed_exports
- get_feature_guide
- get_feature_guides
- get_frequently_asked_questions
- get_installation_guide
- get_playground
- get_release_notes_by_version
- get_upgrade_guide
- get_v4_breaking_changes
- get_vuetify0_component_guide
- get_vuetify0_component_list
- get_vuetify0_composable_guide
- get_vuetify0_composable_list
- get_vuetify0_exports_list
- get_vuetify0_installation_guide
- get_vuetify0_package_guide
- get_vuetify0_skill
- get_vuetify_api_by_version
- get_vuetify_one_installation_guide
What Claude reads (26)
26 toolsTwenty-six tools that look up docs, APIs, guides and your saved bins, playgrounds and links, without changing them.
create_bug_report
Prepares a link to the Vuetify issues site with the repository and the bug report type already selected. It does not submit anything: you open the link and file the issue yourself.
get_all_bins
Lists the Play bins saved under your Vuetify One account, so the existing demos are visible before a new one is made.
get_all_links
Returns the vtfy.link short URLs you created, so the links already made from your account can be listed in the conversation.
get_all_playgrounds
Enumerates the playgrounds, single-file Vue components, stored in your Vuetify One account, before Claude opens one.
get_bin
Fetches one bin by its identifier, so Claude can read the exact code it contains rather than guess from a title.
get_component_api_by_version
Returns the API list of one Vuetify component, its props, slots and events, from the current documentation instead of an answer frozen at training time. No account is needed.
get_directive_api_by_version
Gives the API information for one Vuetify directive, read from the current documentation rather than recalled from training. Vuetify's server marks it read-only, and it works with no account.
get_exposed_exports
Provides the list of exports published by the Vuetify npm package, so Claude knows what can actually be imported.
get_feature_guide
Pulls the documentation page of one specific feature, once the right guide has been picked from the list of available ones. It is one of the public documentation tools that need no login.
get_feature_guides
Lists the feature guides available in the documentation, giving Claude a map of topics before it opens the right one.
get_frequently_asked_questions
Loads the official list of frequently asked questions about Vuetify, so common problems get the documented answer. No account is needed for it.
get_installation_guide
Brings back detailed install instructions for several environments, including Vite, Nuxt, the Nuxt module, Laravel, CDN builds and VitePress.
get_playground
Opens one playground by its identifier and returns its single-file Vue component for Claude to read.
get_release_notes_by_version
Retrieves the release notes of one or more Vuetify versions, so Claude can tell you what a given release fixed or added. Several versions can be asked at once.
get_upgrade_guide
Returns the raw upgrade guide for each major version jump, from 1.5 to 2, 2.7 to 3, or 3 to 4.
get_v4_breaking_changes
Lists what breaks in Vuetify 4, optionally by category, with migration guidance for each.
get_vuetify0_component_guide
Delivers detailed documentation and source code for one headless component of Vuetify0, the framework's unstyled layer. No sign-in is required.
get_vuetify0_component_list
Lists the headless components available in Vuetify0; Vuetify's server counts 40 of them. It is a starting point before opening one component's guide.
get_vuetify0_composable_guide
Supplies the detailed documentation and source code of a single Vuetify0 composable, the reusable logic pieces of that package. It works with no account.
get_vuetify0_composable_list
Lists every composable in Vuetify0 by category, among them foundation, registration, selection, forms, plugins, data and reactivity; the server counts 71. Each entry can then be opened in detail.
get_vuetify0_exports_list
Shows the subpath exports of the Vuetify0 package, such as utilities, types, date, palettes, theme and locale. No Vuetify One sign-in is needed.
get_vuetify0_installation_guide
Reads the Vuetify0 README from GitHub, with installation and usage instructions for this headless meta-framework. The text comes straight from the package's GitHub page.
get_vuetify0_package_guide
Fetches the package-specific documentation of Vuetify0 from GitHub, beyond the install steps. Like the other Vuetify0 tools, it needs no account.
get_vuetify0_skill
Hands Claude the latest reference file for Vuetify0, a compact guide of patterns, anti-patterns and common mistakes aimed at AI coding assistants.
get_vuetify_api_by_version
Downloads and caches the Vuetify API types of a given version, according to Vuetify's server, which marks the tool read-only. It is part of the public documentation and API tools that need no login.
get_vuetify_one_installation_guide
Reads the README of the Vuetify One package from GitHub, including install and usage instructions. Reading this guide itself does not require a sign-in.
What Claude creates or updates (5)
5 toolsFive Vuetify One tools that save or revise bins, playgrounds and short links in your account.
create_vuetify_bin
Approval: see the ruleSaves a new Play bin in your Vuetify One account. Vuetify lists it among the tools that only work after a Vuetify One sign-in, done through OAuth rather than a pasted API key.
create_vuetify_link
Approval: see the ruleGenerates a vtfy.link short URL from your Vuetify One account. Like the bin and playground tools, it depends on the Vuetify One sign-in that Vuetify documents for its account tools.
create_vuetify_playground
Approval: see the ruleCreates a playground in your Vuetify One account; Vuetify describes its content as a Vue single-file component. It sits with the other account tools behind the Vuetify One sign-in.
update_vuetify_bin
Approval: see the ruleChanges the content of an existing bin, so the shared snippet reflects the fix rather than a new copy.
update_vuetify_playground
Approval: see the ruleUpdates a playground you already saved in your Vuetify One account, instead of creating a new one. Like the four other writing tools, it requires the Vuetify One sign-in.
What Claude asks before saving to Vuetify One
No source describes a Vuetify-specific confirmation; the rules below are Claude's general ones.
By default, Claude stops and asks before any action it carries out on an account for someone, which covers the five tools that create or update bins, playgrounds and short links. The 26 reading tools change nothing. Claude works with the access of the person who connected: without a Vuetify One sign-in, the account tools stay out of reach. On Team and Enterprise, owners decide which actions members may let through and can restrict a connector for the whole organization.
Which plans include the Claude Vuetify connector
None of the 819 directory sheets states its availability by plan, so there is no official answer for Vuetify alone.
Anthropic's general rule: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner switches the connector on for the organization before members can connect. The Vuetify MCP sheet in the official directory is the only place showing its current state. Vuetify One is a separate account on Vuetify's side.
What the connector does not do
This connector is documented only by its publisher: no Claude help center article and no Anthropic developer page covers it, so the limits below come from Vuetify.
A connector is not an automation: Claude calls its tools while it answers, and nothing runs on its own when a new release ships. By default the sheet's documentation tools only read, and the five that write touch your Vuetify One account, an observed floor rather than a promise. The directory's verification badge is not a security audit, and Anthropic says on every sheet that it does not choose a publisher's tools or vouch for how they behave.
Need help connecting Vuetify MCP to Claude?
A person reads every message.
