Resources · Claude connector

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

Overview

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.

Vocabulary

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.
Connect

Plug the Claude Vuetify connector in, in three steps

  1. 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.

  2. 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.

  3. 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.

Tools

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

What Claude reads (26)

26 tools

Twenty-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.

When it helps
you hit what looks like a component bug and want the right form without hunting for it.

Sourcemcp.vuetifyjs.com · October 1, 2026 ↗

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.

When it helps
you built a bin earlier and want to find it again without searching by hand.
Watch out
it requires the Vuetify One sign-in.

Source0.vuetifyjs.com · September 6, 2026 ↗

get_all_playgrounds

Enumerates the playgrounds, single-file Vue components, stored in your Vuetify One account, before Claude opens one.

When it helps
you want an overview of the experiments you kept while testing a layout.
Watch out
like the other playground tools, it depends on Vuetify One.

Source0.vuetifyjs.com · September 6, 2026 ↗

get_bin

Fetches one bin by its identifier, so Claude can read the exact code it contains rather than guess from a title.

When it helps
someone shares a bin with a broken dialog and you want Claude to look at the actual markup before suggesting a fix.

Source0.vuetifyjs.com · September 6, 2026 ↗

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.

When it helps
you are unsure whether a button prop you remember still exists.

Sourcemcp.vuetifyjs.com · October 1, 2026 ↗

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.

When it helps
you want to check which options a directive accepts before adding it to a list of cards.

Sourcemcp.vuetifyjs.com · October 1, 2026 ↗

get_exposed_exports

Provides the list of exports published by the Vuetify npm package, so Claude knows what can actually be imported.

When it helps
an import in your code fails and you want to confirm the name is exported at all before searching further.

Sourcemcp.vuetifyjs.com · October 1, 2026 ↗

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.

When it helps
you need the full text of one feature guide, not a summary.

Sourcemcp.vuetifyjs.com · October 1, 2026 ↗

get_feature_guides

Lists the feature guides available in the documentation, giving Claude a map of topics before it opens the right one.

When it helps
you are new to the framework and want to see which areas the official docs cover before diving into one.

Sourcemcp.vuetifyjs.com · October 1, 2026 ↗

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.

When it helps
you suspect your issue is a known one and want the maintainers' own explanation before reading forum threads.

Sourcemcp.vuetifyjs.com · October 1, 2026 ↗

get_installation_guide

Brings back detailed install instructions for several environments, including Vite, Nuxt, the Nuxt module, Laravel, CDN builds and VitePress.

When it helps
you start a fresh project and want the setup done the way the documentation describes, not from an old blog post.

Sourcemcp.vuetifyjs.com · October 1, 2026 ↗

get_playground

Opens one playground by its identifier and returns its single-file Vue component for Claude to read.

When it helps
you want Claude to explain why the layout in a saved playground collapses on small screens.
Watch out
Vuetify One sign-in required.

Source0.vuetifyjs.com · September 6, 2026 ↗

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.

When it helps
you are deciding whether a minor release is worth pulling in before a launch.

Sourcemcp.vuetifyjs.com · October 1, 2026 ↗

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.

When it helps
you inherit an older app and need the official migration steps laid out before estimating the work.

Sourcemcp.vuetifyjs.com · October 1, 2026 ↗

get_v4_breaking_changes

Lists what breaks in Vuetify 4, optionally by category, with migration guidance for each.

When it helps
you want to know what in a version 3 codebase will stop working after the jump.
Watch out
Vuetify's server marks it deprecated in favour of a tool that is not on the directory sheet.

Sourcemcp.vuetifyjs.com · October 1, 2026 ↗

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.

When it helps
you build your own design system and want to study how a reference component is implemented first.

Sourcemcp.vuetifyjs.com · October 1, 2026 ↗

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.

When it helps
before inventing a custom tab or popover primitive, you want to check whether one already exists in the package.

Sourcemcp.vuetifyjs.com · October 1, 2026 ↗

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.

When it helps
you picked a selection composable and want its exact behaviour before wiring it into a form.

Sourcemcp.vuetifyjs.com · October 1, 2026 ↗

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.

When it helps
you want to compare the selection composables side by side before choosing one for a multi-step form.

Sourcemcp.vuetifyjs.com · October 1, 2026 ↗

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.

When it helps
you want to import only the date helpers rather than the whole package and need the right path.

Sourcemcp.vuetifyjs.com · October 1, 2026 ↗

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.

When it helps
you are adding Vuetify0 to an existing Vue project and want the official first steps.

Sourcemcp.vuetifyjs.com · October 1, 2026 ↗

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.

When it helps
you need to understand how the package is organised before deciding which parts your team will adopt.

Sourcemcp.vuetifyjs.com · October 1, 2026 ↗

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.

When it helps
you want Claude to follow the maintainers' recommended patterns while it helps you build headless components.

Sourcemcp.vuetifyjs.com · October 1, 2026 ↗

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.

When it helps
your project is pinned to an older version and you want answers that match it rather than the latest.

Sourcemcp.vuetifyjs.com · October 1, 2026 ↗

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.

When it helps
you subscribe to Vuetify One and want to add its package to a project the way the maintainers describe.

Sourcemcp.vuetifyjs.com · October 1, 2026 ↗

What Claude creates or updates (5)

5 tools

Five Vuetify One tools that save or revise bins, playgrounds and short links in your account.

create_vuetify_bin

Approval: see the rule

Saves 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.

What Claude asks for
no source documents a Vuetify-specific confirmation; Claude's default rule of asking first applies.
When it helps
an example discussed in the conversation should be kept as a bin.

Source0.vuetifyjs.com · September 6, 2026 ↗

create_vuetify_playground

Approval: see the rule

Creates 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.

What Claude asks for
the sources describe no dedicated confirmation; the default rule below applies.
When it helps
you want to try a component layout outside your app.

Source0.vuetifyjs.com · September 6, 2026 ↗

update_vuetify_bin

Approval: see the rule

Changes the content of an existing bin, so the shared snippet reflects the fix rather than a new copy.

What Claude asks for
Vuetify documents no confirmation for this edit; Claude's default of asking before changing an account applies.
When it helps
a reviewer pointed out an error in the bin you circulated.

Source0.vuetifyjs.com · September 6, 2026 ↗

update_vuetify_playground

Approval: see the rule

Updates 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 for
no source describes a playground-specific confirmation; the general rule is the reference.
When it helps
you iterate on a form prototype and want the same playground to carry each improvement.

Source0.vuetifyjs.com · September 6, 2026 ↗

Approvals

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.

Plans

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.

Limits

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

Need help connecting Vuetify MCP to Claude?

A person reads every message.

FAQ

Questions about the Claude Vuetify connector

01What can Claude do with the Vuetify connector?
Claude can read current Vuetify documentation and APIs and, with a Vuetify One sign-in, save shareable demos. The directory lists 31 tools: 26 read, covering component and directive APIs by version, install and upgrade guides, release notes, the FAQ, Vuetify0 docs and your saved bins, playgrounds and links; 5 create or update bins, playgrounds and short links. That means answers matched to the release you use rather than to training data.
02Can Claude create or change things with the Vuetify connector?
Yes, five tools write, all tied to a Vuetify One account: creating a bin, a playground or a vtfy.link short URL, and updating a bin or a playground. None of the tools on the sheet deletes anything. The bug report tool does not file an issue; it only prepares a pre-filled link. Without a Vuetify One sign-in, Claude stays limited to the documentation tools, which change nothing. Your account content stays as it is unless one of those five tools runs.
03Does Claude ask before saving a bin or playground?
Claude's default rule is to ask before any action it takes on an account for you, and that covers the five Vuetify One tools. No source describes a Vuetify-specific confirmation on top of that. The 26 reading tools fetch documentation or your saved demos and change nothing. On Team and Enterprise, owners decide which actions members may let through without being asked again. Nothing in the docs tools can alter your account.
04Which Claude plans include the Vuetify connector?
No official source publishes plan availability connector by connector. Anthropic's general rule is that remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, and that on Team and Enterprise an Owner or Primary Owner switches a connector on for the organization first. The Vuetify MCP sheet in the directory shows the current state for your account. Vuetify One is a separate account on Vuetify's side.
05Does Claude need my Vuetify account?
Not for documentation. Vuetify states that its public documentation and API tools work with no account and no login. A Vuetify One sign-in is only needed for bins, playgrounds and short links, and it goes through Vuetify's own sign-in screen, not a pasted API key. Claude then works with the access of that account and nothing more, and only the ten account tools use it. Documentation questions never touch it.
06Why can Claude not save a Vuetify bin?
The likely cause is the missing Vuetify One sign-in. Vuetify documents the bin, playground and link tools as available only on a separate address, mcp.vuetifyjs.com/one, which you connect to authenticate with Vuetify One, and says subscribers can then reach the ecosystem sites. The sign-in uses OAuth, not a pasted API key. Without it, Claude still answers from the public documentation and API tools, which need no login, but cannot save a demo.
07Claude or an automation tool for Vuetify?
They do different jobs. Claude fits when you are working on code and want the current API, an install guide or a quick demo while you talk. An automation tool runs by itself when an event fires, with nobody in a chat. Claude's Vuetify connector has no trigger, so it is a reference and prototyping aid for the developer at the keyboard. Nothing runs in the background between conversations. It answers when you ask.