vuetifyjs/mcp

Model Context Protocol (MCP) server providing Vuetify component information and documentation to any MCP-compatible client or IDE.

Overview

The Vuetify Model Context Protocol (MCP) server bridges the gap between Vuetify's powerful component library and AI-assisted development environments. This integration enables seamless access to Vuetify's extensive component ecosystem directly within your development workflow.

This MCP server enables IDEs and other Model Context clients to assist with:

• Generating Vuetify components with proper props and attributes
• Creating common UI layouts and patterns following best practices
• Providing comprehensive information about Vuetify features and APIs
• Accessing installation guides, FAQs, and release notes without leaving your IDE
• Working with @vuetify/v0 composables and headless components for building custom design systems

By connecting your development environment to the Vuetify MCP server, you gain AI-powered assistance that understands Vuetify's component structure, styling conventions, and implementation details.

Quick Start

Hosted HTTP Server (Easiest)

Two URLs. Use /mcp unless you subscribe to Vuetify One.

The claude CLI below is Claude Code, not Claude Desktop — see Claude Desktop for that GUI client.

# Claude Code — public docs
claude mcp add --transport http vuetify-mcp https://mcp.vuetifyjs.com/mcp

# Optional — authenticate with Vuetify One
claude mcp add --transport http vuetify-one https://mcp.vuetifyjs.com/one

Grok Bot / Cursor Agents: add /mcp for docs (no Authorize card). Add /one to authenticate with Vuetify One; subscribers can then use ecosystem sites from that connector. Do not paste an API key.

Local Installation

Run Vuetify MCP locally:

# Start the Vuetify MCP server
npx -y @vuetify/mcp

This command downloads and runs the latest version of the Vuetify MCP server, making it immediately available to your MCP-compatible clients.

Cursor / Agent Plugin

This repo is an Agent Plugins 1.0.0 package (plugin.json + mcp.json) that points compatible clients at the hosted server.

• Hosted MCP (docs): https://mcp.vuetifyjs.com/mcp
• Hosted MCP (One / OAuth): https://mcp.vuetifyjs.com/one
• Privacy: https://vuetifyjs.com/en/legal/mcp-privacy

Local test: copy or symlink this repo to ~/.cursor/plugins/local/vuetify-mcp.

Configuration

You can configure the Vuetify MCP server in your IDE or client by running the interactive CLI or by manually updating your settings file.

Using the Interactive CLI

The interactive CLI provides the simplest way to configure your environment:

# Configure for hosted remote server
npx -y @vuetify/mcp config --remote

# Or configure for local installation
npx -y @vuetify/mcp config

The CLI will:

1. Detect supported IDEs on your system (VS Code, Claude, Cursor, Trae, Windsurf)
2. Prompt you if multiple IDEs are found
3. Apply the necessary settings automatically to your selected environment
4. Use the hosted server (with --remote) or local installation

Manual Configuration

Below are the locations and JSON snippets for each supported environment. Copy the JSON into your client or IDE settings file at the specified path.

Local stdio (most IDEs):

{
  "mcpServers": {
    "vuetify-mcp": {
      "command": "npx",
      "args": ["-y", "@vuetify/mcp"]
    }
  }
}

Hosted remote server (most IDEs):

{
  "mcpServers": {
    "vuetify-mcp": {
      "url": "https://mcp.vuetifyjs.com/mcp"
    },
    "vuetify-one": {
      "url": "https://mcp.vuetifyjs.com/one"
    }
  }
}

Omit vuetify-one unless you have a Vuetify One subscription.

Claude Desktop

Claude Desktop (the GUI app, distinct from the Claude Code CLI) does not support direct HTTP transport in claude_desktop_config.json — it only accepts stdio servers. Pick one of the configs below.

Local stdio:

{
  "mcpServers": {
    "vuetify-mcp": {
      "command": "npx",
      "args": ["-y", "@vuetify/mcp"]
    }
  }
}

Hosted via mcp-remote bridge (consumes the hosted server over stdio):

{
  "mcpServers": {
    "vuetify-mcp": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.vuetifyjs.com/mcp"]
    }
  }
}

Hosted via mcp-remote on Windows + WSL2:

{
  "mcpServers": {
    "vuetify-mcp": {
      "command": "wsl",
      "args": ["npx", "-y", "mcp-remote", "https://mcp.vuetifyjs.com/mcp"]
    }
  }
}

After editing claude_desktop_config.json, fully quit and relaunch Claude Desktop. Logs (useful for debugging) are at <Claude folder>/logs/main.log — search for vuetify-mcp.

Authentication

Hosted /mcp needs no login. /one authenticates with Vuetify One so subscribers can access ecosystem sites — do not paste an API key there.

Local stdio or self-hosted HTTP can still use a Vuetify API key. How you pass it depends on transport:

Local stdio servers use environment variables:

{
  "mcpServers": {
    "vuetify-mcp": {
      "command": "npx",
      "args": ["-y", "@vuetify/mcp"],
      "env": {
        "VUETIFY_API_KEY": "<YOUR_API_KEY>"
      }
    }
  }
}

HTTP/remote servers require headers (env vars don't work for HTTP transport):

{
  "mcpServers": {
    "vuetify-mcp": {
      "type": "http",
      "url": "https://mcp.vuetifyjs.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}

The server accepts either Authorization: Bearer <token> or X-Vuetify-Api-Key: <token> headers.

VSCode local:

{
  "servers": {
    "vuetify-mcp": {
      "command": "npx",
      "args": ["-y", "@vuetify/mcp"],
      "env": {
        "VUETIFY_API_KEY": "<YOUR_API_KEY>",
        "GITHUB_TOKEN": "<YOUR_GITHUB_TOKEN>"
      }
    }
  }
}

VSCode remote:

{
  "servers": {
    "vuetify-mcp": {
      "url": "https://mcp.vuetifyjs.com/mcp"
    }
  }
}

WSL (Windows Subsystem for Linux)

If you prefer to run the MCP server from Windows using WSL:

{
  "mcpServers": {
    "vuetify-mcp": {
      "command": "wsl.exe",
      "args": [
        "bash",
        "-c",
        "/home/<user>/.nvm/versions/node/<version>/bin/node /home/<user>/sites/mcp/dist/index.js"
      ]
    }
  }
}

Replace <user> and <version> with your actual WSL username and Node.js version.

Self-Hosted HTTP Server

Run your own HTTP server for remote access:

# Start with HTTP transport
npx -y @vuetify/mcp --transport=http --port=3000 --host=0.0.0.0 --stateless

Configuration:

{
  "mcpServers": {
    "vuetify-mcp": {
      "url": "http://your-server:3000/mcp"
    }
  }
}

CLI Arguments:

• --transport=http - Enable HTTP transport
• --port=3000 - Port number (default: 3000)
• --host=0.0.0.0 - Host address (default: localhost)
• --path=/mcp - Endpoint path (default: /mcp)
• --stateless - Stateless mode (recommended for public servers)

Features

The Vuetify MCP server provides a comprehensive set of tools to enhance your development experience. These tools are automatically available to any MCP-compatible client once the server is configured.

API Tools

• get_vuetify_api_by_version: Download and cache Vuetify API types by version. Supports all major Vuetify versions (2.x and 3.x).
• get_component_api_by_version: Return the API list for a specific Vuetify component, including props, events, slots, and exposed methods.
• get_directive_api_by_version: Return the API information for a specific Vuetify directive (e.g., v-ripple, v-scroll). Includes directive description, arguments, default values, and source reference.

Documentation Tools

• get_installation_guide: Get detailed installation guides for various environments, including Vue CLI, Nuxt, Vite, and manual installation methods.
• get_available_features: Get a list of available Vuetify features, including components, directives, and composables.
• get_exposed_exports: Get a list of exports from the Vuetify npm package, useful for understanding what can be imported directly.
• get_frequently_asked_questions: Get the FAQ section from the Vuetify docs, providing answers to common questions and issues.
• get_release_notes_by_version: Get release notes for one or more Vuetify versions, helping you understand changes between versions.
• get_vuetify_one_installation_guide: Get the README contents for @vuetify/one package from GitHub.

Upgrade (v2 → v3)

Start with get_v3_upgrade_playbook. Target Vuetify 3.13 LTS — do not jump to v4.

• get_v3_upgrade_playbook: Ordered phases (baseline e2e, Vue 3 prerequisite, bundler/Nuxt, eslint --fix, component map, breaking-change scan).
• get_v3_upgrade_baseline_recipe: Playwright recipe for upgrade-baseline/ before the bump and upgrade-after/ after. Functional tests are the source of truth; screenshots are classified, not a CI gate.
• get_v2_to_v3_component_map: v2 component → v3.13 status (core, renamed, removed, replaced).
• get_v3_breaking_changes: Filterable v2 → 3 catalog, including a gotchas category.
• get_upgrade_guide: Full markdown. Use version: "v2.7" for v2 → 3 (fetched from v3-stable).

Prompt: upgrade-v2-to-v3.

Upgrade (v3 → v4)

• get_upgrade_guide: Use version: "v3".
• get_v4_breaking_changes: Filterable Vuetify 4 breaking changes.

Vuetify0 (@vuetify/v0) Tools

Support for @vuetify/v0, a headless meta-framework providing unstyled components and composables for building design systems:

• get_vuetify0_installation_guide: Get installation and usage instructions for @vuetify/v0 from GitHub.
• get_vuetify0_package_guide: Get package-specific documentation for @vuetify/v0.
• get_vuetify0_composable_list: List all 71 composables organized by category (foundation, registration, selection, forms, system, plugins, data, reactivity, transformers).
• get_vuetify0_component_list: List all 40 headless components available in @vuetify/v0.
• get_vuetify0_composable_guide: Get detailed documentation and source code for specific composables.
• get_vuetify0_component_guide: Get detailed documentation and source code for specific components.

Project Structure

The Vuetify MCP server follows a modular architecture that separates concerns and makes the codebase easier to navigate and extend:

vuetify-mcp/
├── bin/
│   └── cli.js          # CLI entry point with argument handling
├── src/
│   ├── index.ts        # Main server entry point
│   ├── services/       # Core business logic
│   │   ├── api.ts         # API-related services
│   │   ├── documentation.ts # Documentation services
│   │   └── vuetify0.ts    # @vuetify/v0 services
│   ├── tools/          # MCP tool definitions
│   │   ├── api.ts         # API tools
│   │   ├── documentation.ts # Documentation tools (includes @vuetify/v0)
│   ├── transports/     # Transport implementations
│   │   └── http.ts        # HTTP transport with stateless/stateful modes
│   └── cli/            # Interactive CLI configuration
├── package.json
├── tsconfig.json
└── README.md

This structure makes it easy to locate specific functionality and extend the server with new features.

Development

If you want to contribute to the Vuetify MCP server or customize it for your own needs, follow these steps to set up your development environment:

# Install dependencies
pnpm install

# Run development server
pnpm dev

The development server will start with hot-reloading enabled, allowing you to see your changes immediately.

Adding New Features

To add new features or extend existing ones:

1. Add or update service methods in the appropriate service file (e.g., src/services/component.ts)
2. Register the tool in the corresponding tools file (e.g., src/tools/component.ts)
3. Build and test your changes

MCP SDK Integration

This project uses the @modelcontextprotocol/sdk package to create a Model Context Protocol server that Claude and other AI assistants can interact with. The MCP architecture enables AI assistants to:

• Call specific tools defined in the server
• Receive structured responses in a standardized format
• Provide a better experience for Vuetify-related inquiries

The implementation follows the standard MCP patterns with:

• Server initialization using McpServer class
• Parameter validation with Zod schemas for type safety
• Multiple transport options: stdio (default) and HTTP with session management

Example Tool Implementation

Here's a simplified example of how a tool is implemented in the Vuetify MCP server:

// In src/tools/component.ts
import { z } from 'zod';
import { componentService } from '../services/component';

export const getComponentApiByVersion = {
  name: 'get_component_api_by_version',
  description: 'Return the API list for a Vuetify component',
  parameters: z.object({
    component: z.string().describe('The component name (e.g., "VBtn")'),
    version: z.string().optional().describe('Vuetify version (defaults to latest)')
  }),
  handler: async ({ component, version }) => {
    return componentService.getComponentApi(component, version);
  }
};

Troubleshooting

Common Issues

• Server Not Starting: Ensure you have Node.js 16 or higher installed
• Configuration Not Working: Verify the paths and JSON structure in your settings file
• Missing API Information: Check that you're using a supported Vuetify version

Getting Help

If you encounter issues not covered here, please:

1. Check the GitHub issues for similar problems
2. Join the Vuetify Discord for community support
3. Open a new issue with detailed reproduction steps

Version Compatibility

The Vuetify MCP server is compatible with:

• Vuetify 3.x
• Node.js 22 and higher
• All major MCP-compatible clients (Claude, VSCode, etc.)

License

Vuetify MCP is available under the MIT software license.

Copyright (c) 2025-present Vuetify, LLC