SkillFoxx

Vuetify MCP

Vuetify MCP server: the agent pulls component APIs, guides, release notes and the v2 to v3 upgrade playbook from it

  • 115 ★ on the repository
  • Last commit
  • MIT
MCP serverOfficial

Extended access

Why this level

  • The agent calls a remote Vuetify server and downloads API data and documentation
  • The /one address works through Vuetify One subscriber OAuth and opens extra ecosystem sites
All reasons and checks

vuetifyjs/mcpAuthor:Vuetify

Install

Manual install

claude mcp add --transport http vuetify-mcp https://mcp.vuetifyjs.com/mcp

The public address from the README; no key is needed.

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • The agent calls a remote Vuetify server and downloads API data and documentation
  • The /one address works through Vuetify One subscriber OAuth and opens extra ecosystem sites

This is third-party code. Review the repository files before installing.

What it does

The server gives an agent the Vuetify documentation and API reference, so generated components use real props, events and slots. Tools fall into groups: component and directive APIs by version (2.x and 3.x included), installation guides for Vue CLI, Nuxt and Vite, a feature list with detailed guides, the FAQ, the package's exported names and release notes. A separate block covers upgrades. For v2 to v3 the server returns an ordered playbook, a Playwright baseline recipe, a map of old components, a catalog of breaking changes and the full guide. The target is Vuetify 3.13 LTS, and the server advises against jumping straight to v4. A separate list of breaking changes covers v3 to v4. Another set of tools covers @vuetify/v0, a headless set of components and composables for custom design systems: the server lists 71 composables and 40 components and returns guides with source code. There are two ways to run it. The public address https://mcp.vuetifyjs.com/mcp accepts connections without login. The /one address needs OAuth for Vuetify One subscribers and adds the ecosystem sites. Locally the server starts with npx -y @vuetify/mcp, optionally over HTTP transport.

Who it is for. Vue and Nuxt developers who build Vuetify interfaces with an agent and migrate projects from version 2 to 3.

Good fit when

  • The agent must create a Vuetify component and check props, events and slots against the project's version
  • A Vuetify 2 project moves to 3.13 LTS and needs an ordered plan and the list of breaking changes
  • You need Vuetify installation steps for Nuxt, Vite or Vue CLI without browsing the site
  • You build a design system on @vuetify/v0 and want the agent to know its composable and component lists

Not a fit when

  • The project does not use Vuetify: the server answers only about this library
  • You need Vuetify One ecosystem sites without a subscription: only the /one address returns them after OAuth
  • The agent is offline and you have not self-hosted the server: it fetches documentation online

Example request

Update the table component for Vuetify 3.13: check the v-data-table props against the API and show what changed compared with version 2.

MCP

Transport
stdio, http
Authentication
not required

Environment variables

VUETIFY_API_KEY secret
Key for authorized calls, needed only when working with a Vuetify One subscription.
GITHUB_TOKEN secret
GitHub token for tools that read issues and repository data.

Limitations

The public /mcp works without keys, and the /one address opens for Vuetify One subscribers. For local work with GitHub issues the config names a GITHUB_TOKEN variable, and VUETIFY_API_KEY is used for authorized calls. Claude Desktop does not support direct HTTP transport in claude_desktop_config.json, so the remote server needs the mcp-remote bridge or a local run. The server downloads and caches API data by version.

How to disable. Remove the vuetify-mcp block from your client's MCP settings. In Claude Code the command is claude mcp remove vuetify-mcp. The local data cache sits on your machine, and the public server issues no keys.

FAQ

How do I connect Vuetify MCP to Claude Code?

Run claude mcp add --transport http vuetify-mcp https://mcp.vuetifyjs.com/mcp. The public address works without a key. The local option starts with npx -y @vuetify/mcp.

Do I need a Vuetify One subscription?

No, the /mcp address covers documentation and APIs.

Does the server work with Claude Desktop?

Yes, through a local run of npx -y @vuetify/mcp or the mcp-remote bridge. Claude Desktop does not accept direct HTTP transport in claude_desktop_config.json.

Can the server guide a move from Vuetify 2 to 3?

Yes. The get_v3_upgrade_playbook tool returns the order of steps, with a component map and a catalog of breaking changes beside it. The stated target is Vuetify 3.13 LTS.

Can I host the server myself?

Yes. The command npx -y @vuetify/mcp --transport=http --port=3000 --stateless starts an HTTP server, and --host and --path set the address and path. For public servers the README recommends --stateless mode.

Discussion

No questions or reviews yet.

MCP servers

Nuxt MCP Dev

nuxt-mcp-dev / vite-plugin-mcp

A Nuxt module and a Vite plugin start an MCP server on the dev server port so the agent sees config, pages, components, auto-imports and the module graph

MCP serverExtended access914

A Vite plugin with an MCP server that shows the agent the components, routes and Pinia stores of a running Vue app

MCP serverExtended access578
Official

Vibe MCP gives an agent components, icons and tokens of the monday.com Vibe design system

MCP serverExtended access695
Official

From the onyx authors: gives agents exact props of Vue components, icons and CSS tokens for the installed version.

MCP serverMinimal access126

A Vite, Nuxt and Next.js plugin that exposes the state of a running Vue, React, Svelte or Solid app to an agent over MCP.

MCP serverExtended access127
Official

Chakra UI MCP server: a reference for components, props and theme tokens, plus code review for moving from version 2 to 3

MCP serverExtended access40.7K

README in short

The documentation starts with a quick start through the public HTTP server and a local run, then setup for VS Code, Claude, Cursor, Trae and Windsurf. An interactive config command with a --remote flag does the setup. Separate sections explain keys, a self-hosted HTTP server with --transport, --port, --host and --stateless options, and list the tools by group.

README badge

Report a problem