Manufact

Vuetify MCP

mcp.vuetifyjs.com/mcp

Vuetify MCP is the official hosted Model Context Protocol server for the Vuetify ecosystem. It gives Claude, Cursor, Grok, and other MCP clients live, queryable access to Vuetify 3/4 component and directive APIs, installation and feature guides, FAQs, release notes, v3→v4 upgrade guidance, and the Vuetify0 (headless) composable/component surface. Public documentation tools work with no account. Creating or updating Vuetify Bins, Playground demos, and vtfy.link short URLs uses Vuetify One OAuth (not a pasted API key). Use it when an agent needs current Vuetify APIs instead of training-cutoff guesses: install a Vite/Nuxt app the documented way, look up VBtn props, migrate a v3 project, or pull a v0 selection/form primitive before inventing one. Hosted endpoint: https://mcp.vuetifyjs.com/mcp (streamable HTTP).

Protocol: MCP 2025-11-25
Server version: 0.12.1
Website: mcp.vuetifyjs.com
Supports: Tools
Resources
Prompts

Overall score

Last reviewed at Oct 5, 2026, 14:36:32 UTC

Server metadata

5 of 8 fields50/1005 / 10 pts

Identity, discovery, and usage metadata advertised during the MCP handshake.

Stable server name

Vuetify

10/10Source

Human-readable title

Vuetify MCP

10/10Source

Useful description

Describe what the server helps an agent do.

0/20Source

Server version

Version 0.12.1

10/10Source

Public website

Website: mcp.vuetifyjs.com

10/10Source

Scalable or high-resolution icon

Advertise a vector or at least 128px server icon.

0/10Source

Server instructions

Add concise instructions that explain how an agent should use the server.

0/20Source

Declared capabilities

Supports Tools, Resources, Prompts.

10/10Source

Protocol

Pass100/10020 / 20 pts

Connection, authentication, and protocol compatibility.

MCP negotiation succeeds (v1/v2)

MCP legacy negotiation succeeded in 492ms

Source

Tools list returns results

28 tool(s) returned

Source

Resources list responds

161 resource(s) returned

Source

Server declares tools capability

Server declares tools capability in initialize response

Source

Tools

Issues93/10027.9 / 30 pts

Tool definitions, annotations, and client compatibility.

Skills over MCP resources are readable

Server does not advertise the Skills over MCP extension

All tools have descriptions

All tools have non-empty descriptions

All tools have OpenAI behavior hints

56 behavior annotation issue(s) found

How to fix: On each tool, declare annotations.readOnlyHint, annotations.destructiveHint, and annotations.openWorldHint as booleans. The policy review separately assesses whether their values match the tool's actual behavior.

errorChatGPT

Source

Claude Code metadata fits its 2 KB fields

Tool descriptions and server instructions fit Claude Code's 2 KB fields

Source

Claude tools declare applicable behavior hints

All tools include an applicable readOnlyHint or destructiveHint

Source

All tools have a display title

Source

Claude tool names are within 64 characters

All tool names are within Claude's 64-character limit

Source

Cursor tool-name budget advisory

No tool name independently exhausts Cursor's observed 60-character combined budget

Observed behavior

Tool names use valid characters

All tool names use valid characters

Source

Tool names follow the MCP 1–128 character range

All tool names follow the MCP recommended length

Source

ChatGPT tool names are unique

All tool names are unique

Source

Tool input schemas have a valid object structure

All tool input schemas have a valid object structure

Source

Tool names follow MCP uniqueness guidance

All tool names are unique

Source

Tool input header annotations are valid

All x-mcp-header annotations satisfy Streamable HTTP requirements

Source

Declared output schemas have a valid basic structure

0 declared output schema(s) pass basic structural validation; schemas may describe any JSON value, including arrays

Source

Tool text has no hidden control characters

No invisible or control characters found in tool-facing text

Source

OpenAI file parameters use valid schemas

All declared OpenAI file parameters use reviewer-valid schemas

Source

MCP Apps

Not applicable-Optional

App resources, metadata, and rendering requirements.

Tool-linked resource URI is readable

No view resources found — view checks skipped

Source

View resource envelope is valid

No view resources found — view checks skipped

Tool invocation metadata present

No view resources found — view checks skipped

Source

All discovered view resources were inspected

No view resources found — view checks skipped

Source

View resources declare a domain

No view resources found — view checks skipped

Source

CSP metadata covers literal external origins

No view resources found — view checks skipped

Source

View resource metadata complete

No view resources found — view checks skipped

Source

Declared domains respond

No view resources found — view checks skipped

Tool visibility metadata is valid

No view resources found — view checks skipped

Source

Tool documentation quality

28 tools reviewed73/10029.2 / 40 pts

How clearly each tool’s title, description, input and output schemas, and behavior annotations guide an agent.

get_vuetify_api_by_versionTitles 99Descriptions 70Inputs 93Annotations 25Outputs 072/100

Title99/100

Get Vuetify API by version

The title clearly communicates the tool’s action and subject. Keep it concise.

Description70/100

Download and cache Vuetify API types by version

Describe the returned information so the agent knows whether it will answer the request.

Inputs93/100

Input documentation gives an agent enough context to populate the arguments.

version

The version of Vuetify to retrieve API types for, e.g., "latest" or "3.0.0"

Clear enough to supply this argument.

Annotations25/100

Declare destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

{
  "title": "Get Vuetify API by version",
  "readOnlyHint": true
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_vuetify_api_by_version",
  "description": "Download and cache Vuetify API types by version",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {
      "version": {
        "type": "string",
        "default": "latest",
        "description": "The version of Vuetify to retrieve API types for, e.g., \"latest\" or \"3.0.0\""
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "title": "Get Vuetify API by version",
    "readOnlyHint": true
  }
}

get_component_api_by_versionTitles 99Descriptions 71Inputs 88Annotations 25Outputs 071/100

Title99/100

Get component API by version

The title clearly communicates the tool’s action and subject. Keep it concise.

Description71/100

Return the API list for a Vuetify component

Describe the returned information so the agent knows whether it will answer the request.

Inputs88/100

Explain what happens when this optional value is omitted.

componentName

The name of a Vuetify component, available options here: https://vuetifyjs.com/components/all/

Clear enough to supply this argument.

version

The version of Vuetify to retrieve API types for, e.g., "latest" or "3.0.0"

Explain what happens when this optional value is omitted.

Annotations25/100

Declare destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

{
  "title": "Get component API by version",
  "readOnlyHint": true
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_component_api_by_version",
  "description": "Return the API list for a Vuetify component",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "componentName"
    ],
    "properties": {
      "version": {
        "type": "string",
        "default": "latest",
        "description": "The version of Vuetify to retrieve API types for, e.g., \"latest\" or \"3.0.0\""
      },
      "componentName": {
        "type": "string",
        "description": "The name of a Vuetify component, available options here: https://vuetifyjs.com/components/all/"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "title": "Get component API by version",
    "readOnlyHint": true
  }
}

get_directive_api_by_versionTitles 99Descriptions 68Inputs 88Annotations 25Outputs 071/100

Title99/100

Get directive API by version

The title clearly communicates the tool’s action and subject. Keep it concise.

Description68/100

Return the API information for a Vuetify directive

Describe the returned information so the agent knows whether it will answer the request.

Inputs88/100

Explain what happens when this optional value is omitted.

directiveName

The name of a Vuetify directive, e.g., "v-ripple" or "ripple"

Clear enough to supply this argument.

version

The version of Vuetify to retrieve API types for, e.g., "latest" or "3.0.0"

Explain what happens when this optional value is omitted.

Annotations25/100

Declare destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

{
  "title": "Get directive API by version",
  "readOnlyHint": true
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_directive_api_by_version",
  "description": "Return the API information for a Vuetify directive",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "directiveName"
    ],
    "properties": {
      "version": {
        "type": "string",
        "default": "latest",
        "description": "The version of Vuetify to retrieve API types for, e.g., \"latest\" or \"3.0.0\""
      },
      "directiveName": {
        "type": "string",
        "description": "The name of a Vuetify directive, e.g., \"v-ripple\" or \"ripple\""
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "title": "Get directive API by version",
    "readOnlyHint": true
  }
}

get_installation_guideTitles 98Descriptions 70Inputs 75Annotations 25Outputs 067/100

Title98/100

Get installation guide

The title clearly communicates the tool’s action and subject. Keep it concise.

Description70/100

Get detailed information about how to install Vuetify in a variety of environments.

The description explains the capability, when to use it, and what to expect.

Inputs75/100

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

platform

The platform for which to get the installation guide. Available platforms: vite, nuxt, nuxt-module, laravel, cdn, cdn-esm, vitepress, vuetify0

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

ssr

Whether to return the SSR version of the installation guide.

Clear enough to supply this argument.

fresh

Whether the user has an existing project or is starting fresh.

Explain the meaning of this value, not just its name.

Annotations25/100

Declare destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

{
  "title": "Get installation guide",
  "readOnlyHint": true
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_installation_guide",
  "description": "Get detailed information about how to install Vuetify in a variety of environments.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {
      "ssr": {
        "type": "boolean",
        "default": false,
        "description": "Whether to return the SSR version of the installation guide."
      },
      "fresh": {
        "type": "boolean",
        "default": false,
        "description": "Whether the user has an existing project or is starting fresh."
      },
      "platform": {
        "enum": [
          "vite",
          "nuxt",
          "nuxt-module",
          "laravel",
          "cdn",
          "cdn-esm",
          "vitepress",
          "vuetify0"
        ],
        "type": "string",
        "default": "vite",
        "description": "The platform for which to get the installation guide. Available platforms: vite, nuxt, nuxt-module, laravel, cdn, cdn-esm, vitepress, vuetify0"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "title": "Get installation guide",
    "readOnlyHint": true
  }
}

get_feature_guidesTitles 100Descriptions 69Inputs 100Annotations 25Outputs 074/100

Title100/100

Get feature guides

The title clearly communicates the tool’s action and subject. Keep it concise.

Description69/100

Get a list of available features in the documentation.

Describe the returned information so the agent knows whether it will answer the request.

Inputs100/100

This tool declares no inputs, so argument descriptions are not needed.

No input fields.

Annotations25/100

Declare destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

{
  "title": "Get feature guides",
  "readOnlyHint": true
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_feature_guides",
  "description": "Get a list of available features in the documentation.",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "annotations": {
    "title": "Get feature guides",
    "readOnlyHint": true
  }
}

get_feature_guideTitles 99Descriptions 63Inputs 75Annotations 25Outputs 066/100

Title99/100

Get feature guide

The title clearly communicates the tool’s action and subject. Keep it concise.

Description63/100

Get the information about a specific feature in the documentation.

Describe the concrete operation and its scope instead of restating the tool name.

Inputs75/100

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

feature

The feature for which to get the documentation. Available features: accessibility, aliasing, application-layout, blueprints, dates, display-and-platform, global-configuration, icon-fonts, internationalization, programmatic-scrolling, sass-variables, theme

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

Annotations25/100

Declare destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

{
  "title": "Get feature guide",
  "readOnlyHint": true
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_feature_guide",
  "description": "Get the information about a specific feature in the documentation.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "feature"
    ],
    "properties": {
      "feature": {
        "enum": [
          "accessibility",
          "aliasing",
          "application-layout",
          "blueprints",
          "dates",
          "display-and-platform",
          "global-configuration",
          "icon-fonts",
          "internationalization",
          "programmatic-scrolling",
          "sass-variables",
          "theme"
        ],
        "type": "string",
        "description": "The feature for which to get the documentation. Available features: accessibility, aliasing, application-layout, blueprints, dates, display-and-platform, global-configuration, icon-fonts, internationalization, programmatic-scrolling, sass-variables, theme"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "title": "Get feature guide",
    "readOnlyHint": true
  }
}

get_exposed_exportsTitles 89Descriptions 66Inputs 100Annotations 25Outputs 071/100

Title89/100

Get exposed exports

The title clearly communicates the tool’s action and subject. Keep it concise.

Description66/100

Get a list of exports from the Vuetify npm package

Describe the returned information so the agent knows whether it will answer the request.

Inputs100/100

This tool declares no inputs, so argument descriptions are not needed.

No input fields.

Annotations25/100

Declare destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

{
  "title": "Get exposed exports",
  "readOnlyHint": true
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_exposed_exports",
  "description": "Get a list of exports from the Vuetify npm package",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "annotations": {
    "title": "Get exposed exports",
    "readOnlyHint": true
  }
}

get_frequently_asked_questionsTitles 99Descriptions 70Inputs 100Annotations 25Outputs 074/100

Title99/100

Get frequently asked questions

The title clearly communicates the tool’s action and subject. Keep it concise.

Description70/100

Get a list of frequently asked questions about Vuetify.

Describe the returned information so the agent knows whether it will answer the request.

Inputs100/100

This tool declares no inputs, so argument descriptions are not needed.

No input fields.

Annotations25/100

Declare destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

{
  "title": "Get frequently asked questions",
  "readOnlyHint": true
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_frequently_asked_questions",
  "description": "Get a list of frequently asked questions about Vuetify.",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "annotations": {
    "title": "Get frequently asked questions",
    "readOnlyHint": true
  }
}

get_release_notes_by_versionTitles 100Descriptions 68Inputs 50Annotations 25Outputs 061/100

Title100/100

Get release notes by version

The title clearly communicates the tool’s action and subject. Keep it concise.

Description68/100

Get release notes for one or more versions of Vuetify.

Describe the returned information so the agent knows whether it will answer the request.

Inputs50/100

Clarify units, where to obtain this value, or conventions not already expressed in the schema.

version

One or more Vuetify versions for which to get the release notes.

Clarify units, where to obtain this value, or conventions not already expressed in the schema.

Annotations25/100

Declare destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

{
  "title": "Get release notes by version",
  "readOnlyHint": true
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_release_notes_by_version",
  "description": "Get release notes for one or more versions of Vuetify.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {
      "version": {
        "type": "string",
        "default": "latest",
        "description": "One or more Vuetify versions for which to get the release notes."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "title": "Get release notes by version",
    "readOnlyHint": true
  }
}

get_vuetify_one_installation_guideTitles 100Descriptions 85Inputs 100Annotations 25Outputs 079/100

Title100/100

Get Vuetify One installation guide

The title clearly communicates the tool’s action and subject. Keep it concise.

Description85/100

Get the README contents for @vuetify/one package from GitHub, including installation and usage instructions.

The description explains the capability, when to use it, and what to expect.

Inputs100/100

This tool declares no inputs, so argument descriptions are not needed.

No input fields.

Annotations25/100

Declare destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

{
  "title": "Get Vuetify One installation guide",
  "readOnlyHint": true
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_vuetify_one_installation_guide",
  "description": "Get the README contents for @vuetify/one package from GitHub, including installation and usage instructions.",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "annotations": {
    "title": "Get Vuetify One installation guide",
    "readOnlyHint": true
  }
}

get_upgrade_guideTitles 98Descriptions 95Inputs 75Annotations 25Outputs 074/100

Title98/100

Get upgrade guide

The title clearly communicates the tool’s action and subject. Keep it concise.

Description95/100

Get the raw upgrade guide markdown for migrating between Vuetify major versions (v1.5→v2, v2.7→v3, v3→v4). For machine-actionable rules, use get_upgrade_plan and get_upgrade_rules instead.

The description explains the capability, when to use it, and what to expect.

Inputs75/100

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

version

The source Vuetify version to upgrade from. Available versions: v1.5, v2.7, v3

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

Annotations25/100

Declare destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

{
  "title": "Get upgrade guide",
  "readOnlyHint": true
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_upgrade_guide",
  "description": "Get the raw upgrade guide markdown for migrating between Vuetify major versions (v1.5→v2, v2.7→v3, v3→v4). For machine-actionable rules, use get_upgrade_plan and get_upgrade_rules instead.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "version"
    ],
    "properties": {
      "version": {
        "enum": [
          "v1.5",
          "v2.7",
          "v3"
        ],
        "type": "string",
        "description": "The source Vuetify version to upgrade from. Available versions: v1.5, v2.7, v3"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "title": "Get upgrade guide",
    "readOnlyHint": true
  }
}

get_upgrade_planTitles 99Descriptions 95Inputs 95Annotations 25Outputs 080/100

Title99/100

Get upgrade plan

The title clearly communicates the tool’s action and subject. Keep it concise.

Description95/100

Get a structured upgrade plan for migrating between Vuetify versions. Resolves multi-hop migrations (e.g., v2→v4 becomes v2→v3→v4). Returns tooling recommendations, effort estimates, and a rule index per hop. This is the first call agents should make when planning a migration. After scanning, agents MUST emit findings using the MigrationReceipt schema (see get_migration_receipt_schema).

The description explains the capability, when to use it, and what to expect.

Inputs95/100

Input documentation gives an agent enough context to populate the arguments.

from

Source Vuetify version to upgrade from. Examples: v1, v2, v3, 2.7, 3. Known versions: v1, v2, v3, v4

Clear enough to supply this argument.

Target Vuetify version to upgrade to. Examples: v2, v3, v4, latest. Known versions: v1, v2, v3, v4

Clear enough to supply this argument.

Annotations25/100

Declare destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

{
  "title": "Get upgrade plan",
  "readOnlyHint": true
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_upgrade_plan",
  "description": "Get a structured upgrade plan for migrating between Vuetify versions. Resolves multi-hop migrations (e.g., v2→v4 becomes v2→v3→v4). Returns tooling recommendations, effort estimates, and a rule index per hop. This is the first call agents should make when planning a migration. After scanning, agents MUST emit findings using the MigrationReceipt schema (see get_migration_receipt_schema).",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "from",
      "to"
    ],
    "properties": {
      "to": {
        "type": "string",
        "description": "Target Vuetify version to upgrade to. Examples: v2, v3, v4, latest. Known versions: v1, v2, v3, v4"
      },
      "from": {
        "type": "string",
        "description": "Source Vuetify version to upgrade from. Examples: v1, v2, v3, 2.7, 3. Known versions: v1, v2, v3, v4"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "title": "Get upgrade plan",
    "readOnlyHint": true
  }
}

get_upgrade_rulesTitles 99Descriptions 89Inputs 80Annotations 25Outputs 074/100

Title99/100

Get upgrade rules

The title clearly communicates the tool’s action and subject. Keep it concise.

Description89/100

Get full machine-actionable migration rules for Vuetify upgrades. Each rule includes: detect.grep patterns for scanning code, replace mappings, codemod hints, and revert snippets for incremental migration. Filter by rule IDs, category, or component. After scanning with detect.grep, agents MUST emit findings using the MigrationReceipt schema (see get_migration_receipt_schema).

The description explains the capability, when to use it, and what to expect.

Inputs80/100

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

from

Source Vuetify version to upgrade from. Examples: v1, v2, v3, 2.7, 3

Clear enough to supply this argument.

Target Vuetify version to upgrade to. Examples: v2, v3, v4, latest

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

ids

Optional array of specific rule IDs to fetch (e.g., ["v4/typography-classes", "v4/css-layers"])

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

category

Optional category to filter by. Available: styles, theme, display, grid, typography, elevation, components, composables, directives, utilities

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

component

Optional component name to filter by (e.g., "VSnackbar", "VBtn", "VSelect")

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

Annotations25/100

Declare destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

{
  "title": "Get upgrade rules",
  "readOnlyHint": true
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_upgrade_rules",
  "description": "Get full machine-actionable migration rules for Vuetify upgrades. Each rule includes: detect.grep patterns for scanning code, replace mappings, codemod hints, and revert snippets for incremental migration. Filter by rule IDs, category, or component. After scanning with detect.grep, agents MUST emit findings using the MigrationReceipt schema (see get_migration_receipt_schema).",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "from",
      "to"
    ],
    "properties": {
      "to": {
        "type": "string",
        "description": "Target Vuetify version to upgrade to. Examples: v2, v3, v4, latest"
      },
      "ids": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "Optional array of specific rule IDs to fetch (e.g., [\"v4/typography-classes\", \"v4/css-layers\"])"
      },
      "from": {
        "type": "string",
        "description": "Source Vuetify version to upgrade from. Examples: v1, v2, v3, 2.7, 3"
      },
      "category": {
        "enum": [
          "styles",
          "theme",
          "display",
          "grid",
          "typography",
          "elevation",
          "components",
          "composables",
          "directives",
          "utilities"
        ],
        "type": "string",
        "description": "Optional category to filter by. Available: styles, theme, display, grid, typography, elevation, components, composables, directives, utilities"
      },
      "component": {
        "type": "string",
        "description": "Optional component name to filter by (e.g., \"VSnackbar\", \"VBtn\", \"VSelect\")"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "title": "Get upgrade rules",
    "readOnlyHint": true
  }
}

get_migration_receipt_schemaTitles 100Descriptions 96Inputs 100Annotations 25Outputs 081/100

Title100/100

Get migration receipt schema

The title clearly communicates the tool’s action and subject. Keep it concise.

Description96/100

Get the MigrationReceipt schema that agents MUST use when reporting migration findings. The MCP server returns rules; client agents scan user code and emit receipts in this format. Includes confidence guidance: high (→ auto) for exact match + codemod, medium/low (→ review) for partial matches. Returns both the receipt schema and the batch envelope (MigrationReceiptReport).

The description explains the capability, when to use it, and what to expect.

Inputs100/100

This tool declares no inputs, so argument descriptions are not needed.

No input fields.

Annotations25/100

Declare destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

{
  "title": "Get migration receipt schema",
  "readOnlyHint": true
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_migration_receipt_schema",
  "description": "Get the MigrationReceipt schema that agents MUST use when reporting migration findings. The MCP server returns rules; client agents scan user code and emit receipts in this format. Includes confidence guidance: high (→ auto) for exact match + codemod, medium/low (→ review) for partial matches. Returns both the receipt schema and the batch envelope (MigrationReceiptReport).",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "annotations": {
    "title": "Get migration receipt schema",
    "readOnlyHint": true
  }
}

get_v4_breaking_changesTitles 99Descriptions 90Inputs 75Annotations 25Outputs 073/100

Title99/100

Get Vuetify 4 breaking changes

The title clearly communicates the tool’s action and subject. Keep it concise.

Description90/100

[DEPRECATED: Use get_upgrade_rules({ from: "v3", to: "v4" }) instead] Get Vuetify 4 breaking changes, optionally filtered by category. Returns migration guidance for each change.

The description explains the capability, when to use it, and what to expect.

Inputs75/100

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

category

Optional category to filter by. Available categories: styles, theme, display, grid, typography, elevation, v-btn, v-snackbar, v-select, v-date-picker, v-form, v-img, nested. Omit to get all breaking changes.

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

Annotations25/100

Declare destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

{
  "title": "Get Vuetify 4 breaking changes",
  "readOnlyHint": true
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_v4_breaking_changes",
  "description": "[DEPRECATED: Use get_upgrade_rules({ from: \"v3\", to: \"v4\" }) instead] Get Vuetify 4 breaking changes, optionally filtered by category. Returns migration guidance for each change.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {
      "category": {
        "enum": [
          "styles",
          "theme",
          "display",
          "grid",
          "typography",
          "elevation",
          "v-btn",
          "v-snackbar",
          "v-select",
          "v-date-picker",
          "v-form",
          "v-img",
          "nested"
        ],
        "type": "string",
        "description": "Optional category to filter by. Available categories: styles, theme, display, grid, typography, elevation, v-btn, v-snackbar, v-select, v-date-picker, v-form, v-img, nested. Omit to get all breaking changes."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "title": "Get Vuetify 4 breaking changes",
    "readOnlyHint": true
  }
}

get_v3_breaking_changesTitles 99Descriptions 81Inputs 75Annotations 25Outputs 071/100

Title99/100

Get Vuetify 3 breaking changes

The title clearly communicates the tool’s action and subject. Keep it concise.

Description81/100

Vuetify 2 → 3 breaking changes, optionally filtered by category (setup, layout, theme, components, gotchas, …). High-pain categories include before/after snippets. Omit category to get all.

Describe the returned information so the agent knows whether it will answer the request.

Inputs75/100

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

category

Optional category to filter by. Available categories: setup, layout, theme, sass, styles, general, inputs, v-alert, v-badge, v-banner, v-btn, v-calendar, v-checkbox, v-date-picker, v-form, v-list, v-menu, v-navigation-drawer, v-rating, v-select, v-table, v-stepper, v-data-table, v-slider, v-tabs, v-img, v-snackbar, v-expansion-panel, v-card, v-sparkline, v-intersect, renames, missing, gotchas. Omit to get all breaking changes.

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

Annotations25/100

Declare destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

{
  "title": "Get Vuetify 3 breaking changes",
  "readOnlyHint": true
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_v3_breaking_changes",
  "description": "Vuetify 2 → 3 breaking changes, optionally filtered by category (setup, layout, theme, components, gotchas, …). High-pain categories include before/after snippets. Omit category to get all.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {
      "category": {
        "enum": [
          "setup",
          "layout",
          "theme",
          "sass",
          "styles",
          "general",
          "inputs",
          "v-alert",
          "v-badge",
          "v-banner",
          "v-btn",
          "v-calendar",
          "v-checkbox",
          "v-date-picker",
          "v-form",
          "v-list",
          "v-menu",
          "v-navigation-drawer",
          "v-rating",
          "v-select",
          "v-table",
          "v-stepper",
          "v-data-table",
          "v-slider",
          "v-tabs",
          "v-img",
          "v-snackbar",
          "v-expansion-panel",
          "v-card",
          "v-sparkline",
          "v-intersect",
          "renames",
          "missing",
          "gotchas"
        ],
        "type": "string",
        "description": "Optional category to filter by. Available categories: setup, layout, theme, sass, styles, general, inputs, v-alert, v-badge, v-banner, v-btn, v-calendar, v-checkbox, v-date-picker, v-form, v-list, v-menu, v-navigation-drawer, v-rating, v-select, v-table, v-stepper, v-data-table, v-slider, v-tabs, v-img, v-snackbar, v-expansion-panel, v-card, v-sparkline, v-intersect, renames, missing, gotchas. Omit to get all breaking changes."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "title": "Get Vuetify 3 breaking changes",
    "readOnlyHint": true
  }
}

get_v2_to_v3_component_mapTitles 99Descriptions 73Inputs 100Annotations 25Outputs 075/100

Title99/100

Get Vuetify 2 to 3 component map

The title clearly communicates the tool’s action and subject. Keep it concise.

Description73/100

v2 component → v3.13 status (core, renamed, removed, replaced) with notes and issue links.

Describe the returned information so the agent knows whether it will answer the request.

Inputs100/100

This tool declares no inputs, so argument descriptions are not needed.

No input fields.

Annotations25/100

Declare destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

{
  "title": "Get Vuetify 2 to 3 component map",
  "readOnlyHint": true
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_v2_to_v3_component_map",
  "description": "v2 component → v3.13 status (core, renamed, removed, replaced) with notes and issue links.",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "annotations": {
    "title": "Get Vuetify 2 to 3 component map",
    "readOnlyHint": true
  }
}

get_v3_upgrade_playbookTitles 100Descriptions 81Inputs 100Annotations 25Outputs 077/100

Title100/100

Get Vuetify 2 to 3 upgrade playbook

The title clearly communicates the tool’s action and subject. Keep it concise.

Description81/100

Start here for Vuetify 2 → 3. Ordered phases: baseline e2e, Vue 3 prerequisite, bundler/Nuxt, eslint --fix, component map, breaking-change scan. Target vuetify@^3.13. Do not upgrade to v4.

Describe the returned information so the agent knows whether it will answer the request.

Inputs100/100

This tool declares no inputs, so argument descriptions are not needed.

No input fields.

Annotations25/100

Declare destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

{
  "title": "Get Vuetify 2 to 3 upgrade playbook",
  "readOnlyHint": true
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_v3_upgrade_playbook",
  "description": "Start here for Vuetify 2 → 3. Ordered phases: baseline e2e, Vue 3 prerequisite, bundler/Nuxt, eslint --fix, component map, breaking-change scan. Target vuetify@^3.13. Do not upgrade to v4.",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "annotations": {
    "title": "Get Vuetify 2 to 3 upgrade playbook",
    "readOnlyHint": true
  }
}

get_v3_upgrade_baseline_recipeTitles 98Descriptions 79Inputs 100Annotations 25Outputs 076/100

Title98/100

Get Vuetify 2 to 3 upgrade baseline recipe

The title clearly communicates the tool’s action and subject. Keep it concise.

Description79/100

Playwright recipe to snapshot the current Vuetify 2 app before upgrading (upgrade-baseline/) and re-run after (upgrade-after/). Functional e2e is the source of truth; screenshots are classified, not a CI gate.

Describe the returned information so the agent knows whether it will answer the request.

Inputs100/100

This tool declares no inputs, so argument descriptions are not needed.

No input fields.

Annotations25/100

Declare destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

{
  "title": "Get Vuetify 2 to 3 upgrade baseline recipe",
  "readOnlyHint": true
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_v3_upgrade_baseline_recipe",
  "description": "Playwright recipe to snapshot the current Vuetify 2 app before upgrading (upgrade-baseline/) and re-run after (upgrade-after/). Functional e2e is the source of truth; screenshots are classified, not a CI gate.",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "annotations": {
    "title": "Get Vuetify 2 to 3 upgrade baseline recipe",
    "readOnlyHint": true
  }
}

get_vuetify0_installation_guideTitles 97Descriptions 77Inputs 100Annotations 25Outputs 076/100

Title97/100

Get Vuetify0 installation guide

The title clearly communicates the tool’s action and subject. Keep it concise.

Description77/100

Get the README contents for @vuetify/v0 (Vuetify0) package from GitHub, including installation and usage instructions for this headless meta-framework.

The description explains the capability, when to use it, and what to expect.

Inputs100/100

This tool declares no inputs, so argument descriptions are not needed.

No input fields.

Annotations25/100

Declare destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

{
  "title": "Get Vuetify0 installation guide",
  "readOnlyHint": true
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_vuetify0_installation_guide",
  "description": "Get the README contents for @vuetify/v0 (Vuetify0) package from GitHub, including installation and usage instructions for this headless meta-framework.",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "annotations": {
    "title": "Get Vuetify0 installation guide",
    "readOnlyHint": true
  }
}

get_vuetify0_package_guideTitles 96Descriptions 70Inputs 100Annotations 25Outputs 073/100

Title96/100

Get Vuetify0 package guide

The title clearly communicates the tool’s action and subject. Keep it concise.

Description70/100

Get the package-specific documentation for @vuetify/v0 from GitHub.

Describe the returned information so the agent knows whether it will answer the request.

Inputs100/100

This tool declares no inputs, so argument descriptions are not needed.

No input fields.

Annotations25/100

Declare destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

{
  "title": "Get Vuetify0 package guide",
  "readOnlyHint": true
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_vuetify0_package_guide",
  "description": "Get the package-specific documentation for @vuetify/v0 from GitHub.",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "annotations": {
    "title": "Get Vuetify0 package guide",
    "readOnlyHint": true
  }
}

get_vuetify0_composable_listTitles 98Descriptions 82Inputs 100Annotations 25Outputs 077/100

Title98/100

Get Vuetify0 composable list

The title clearly communicates the tool’s action and subject. Keep it concise.

Description82/100

Get a comprehensive list of all 71 composables available in @vuetify/v0, organized by category (foundation, registration, selection, forms, system, plugins, data, reactivity, transformers).

The description explains the capability, when to use it, and what to expect.

Inputs100/100

This tool declares no inputs, so argument descriptions are not needed.

No input fields.

Annotations25/100

Declare destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

{
  "title": "Get Vuetify0 composable list",
  "readOnlyHint": true
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_vuetify0_composable_list",
  "description": "Get a comprehensive list of all 71 composables available in @vuetify/v0, organized by category (foundation, registration, selection, forms, system, plugins, data, reactivity, transformers).",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "annotations": {
    "title": "Get Vuetify0 composable list",
    "readOnlyHint": true
  }
}

get_vuetify0_component_listTitles 99Descriptions 72Inputs 100Annotations 25Outputs 075/100

Title99/100

Get Vuetify0 component list

The title clearly communicates the tool’s action and subject. Keep it concise.

Description72/100

Get a list of all 40 headless components available in @vuetify/v0.

Describe the returned information so the agent knows whether it will answer the request.

Inputs100/100

This tool declares no inputs, so argument descriptions are not needed.

No input fields.

Annotations25/100

Declare destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

{
  "title": "Get Vuetify0 component list",
  "readOnlyHint": true
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_vuetify0_component_list",
  "description": "Get a list of all 40 headless components available in @vuetify/v0.",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "annotations": {
    "title": "Get Vuetify0 component list",
    "readOnlyHint": true
  }
}

get_vuetify0_composable_guideTitles 98Descriptions 71Inputs 81Annotations 25Outputs 069/100

Title98/100

Get Vuetify0 composable guide

The title clearly communicates the tool’s action and subject. Keep it concise.

Description71/100

Get detailed documentation and source code for a specific @vuetify/v0 composable.

Describe the returned information so the agent knows whether it will answer the request.

Inputs81/100

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

category

The category of the composable. Available categories: foundation, registration, selection, forms, system, plugins, data, semantic, reactivity, transformers

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

name

The name of the composable (e.g., "createContext", "useSelection", "useTheme")

Clear enough to supply this argument.

Annotations25/100

Declare destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

{
  "title": "Get Vuetify0 composable guide",
  "readOnlyHint": true
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_vuetify0_composable_guide",
  "description": "Get detailed documentation and source code for a specific @vuetify/v0 composable.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "category",
      "name"
    ],
    "properties": {
      "name": {
        "type": "string",
        "description": "The name of the composable (e.g., \"createContext\", \"useSelection\", \"useTheme\")"
      },
      "category": {
        "enum": [
          "foundation",
          "registration",
          "selection",
          "forms",
          "system",
          "plugins",
          "data",
          "semantic",
          "reactivity",
          "transformers"
        ],
        "type": "string",
        "description": "The category of the composable. Available categories: foundation, registration, selection, forms, system, plugins, data, semantic, reactivity, transformers"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "title": "Get Vuetify0 composable guide",
    "readOnlyHint": true
  }
}

get_vuetify0_component_guideTitles 97Descriptions 73Inputs 75Annotations 25Outputs 068/100

Title97/100

Get Vuetify0 component guide

The title clearly communicates the tool’s action and subject. Keep it concise.

Description73/100

Get detailed documentation and source code for a specific @vuetify/v0 component.

Describe the returned information so the agent knows whether it will answer the request.

Inputs75/100

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

name

The name of the component. Available components: AlertDialog, AspectRatio, Atom, Avatar, Breadcrumbs, Button, Carousel, Checkbox, Collapsible, Combobox, Dialog, ExpansionPanel, Form, Group, Image, Input, Locale, NumberField, Overflow, Pagination, Popover, Portal, Presence, Progress, Radio, Rating, Scrim, Select, Selection, Single, Slider, Snackbar, Splitter, Step, Switch, Tabs, Theme, Toggle, Tooltip, Treeview

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

Annotations25/100

Declare destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

{
  "title": "Get Vuetify0 component guide",
  "readOnlyHint": true
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_vuetify0_component_guide",
  "description": "Get detailed documentation and source code for a specific @vuetify/v0 component.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "name"
    ],
    "properties": {
      "name": {
        "enum": [
          "AlertDialog",
          "AspectRatio",
          "Atom",
          "Avatar",
          "Breadcrumbs",
          "Button",
          "Carousel",
          "Checkbox",
          "Collapsible",
          "Combobox",
          "Dialog",
          "ExpansionPanel",
          "Form",
          "Group",
          "Image",
          "Input",
          "Locale",
          "NumberField",
          "Overflow",
          "Pagination",
          "Popover",
          "Portal",
          "Presence",
          "Progress",
          "Radio",
          "Rating",
          "Scrim",
          "Select",
          "Selection",
          "Single",
          "Slider",
          "Snackbar",
          "Splitter",
          "Step",
          "Switch",
          "Tabs",
          "Theme",
          "Toggle",
          "Tooltip",
          "Treeview"
        ],
        "type": "string",
        "description": "The name of the component. Available components: AlertDialog, AspectRatio, Atom, Avatar, Breadcrumbs, Button, Carousel, Checkbox, Collapsible, Combobox, Dialog, ExpansionPanel, Form, Group, Image, Input, Locale, NumberField, Overflow, Pagination, Popover, Portal, Presence, Progress, Radio, Rating, Scrim, Select, Selection, Single, Slider, Snackbar, Splitter, Step, Switch, Tabs, Theme, Toggle, Tooltip, Treeview"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "title": "Get Vuetify0 component guide",
    "readOnlyHint": true
  }
}

get_vuetify0_exports_listTitles 99Descriptions 75Inputs 100Annotations 25Outputs 076/100

Title99/100

Get Vuetify0 exports list

The title clearly communicates the tool’s action and subject. Keep it concise.

Description75/100

Get a list of all subpath exports available in @vuetify/v0 (utilities, types, constants, date, data-table, palettes, theme, locale, logger, and more).

Describe the returned information so the agent knows whether it will answer the request.

Inputs100/100

This tool declares no inputs, so argument descriptions are not needed.

No input fields.

Annotations25/100

Declare destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

{
  "title": "Get Vuetify0 exports list",
  "readOnlyHint": true
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_vuetify0_exports_list",
  "description": "Get a list of all subpath exports available in @vuetify/v0 (utilities, types, constants, date, data-table, palettes, theme, locale, logger, and more).",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "annotations": {
    "title": "Get Vuetify0 exports list",
    "readOnlyHint": true
  }
}

get_vuetify0_skillTitles 93Descriptions 80Inputs 100Annotations 25Outputs 075/100

Title93/100

Get Vuetify0 skill

The title clearly communicates the tool’s action and subject. Keep it concise.

Description80/100

Get the latest SKILL.md reference for @vuetify/v0 — a compact guide with patterns, anti-patterns, and common mistakes optimized for AI coding assistants.

The description explains the capability, when to use it, and what to expect.

Inputs100/100

This tool declares no inputs, so argument descriptions are not needed.

No input fields.

Annotations25/100

Declare destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

{
  "title": "Get Vuetify0 skill",
  "readOnlyHint": true
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_vuetify0_skill",
  "description": "Get the latest SKILL.md reference for @vuetify/v0 — a compact guide with patterns, anti-patterns, and common mistakes optimized for AI coding assistants.",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "annotations": {
    "title": "Get Vuetify0 skill",
    "readOnlyHint": true
  }
}

create_bug_reportTitles 99Descriptions 76Inputs 63Annotations 25Outputs 066/100

Title99/100

Create bug report

The title clearly communicates the tool’s action and subject. Keep it concise.

Description76/100

Generate a link to the Vuetify issues site with the repository and bug report type pre-selected.

Describe the returned information so the agent knows whether it will answer the request.

Inputs63/100

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

repo

The repository to report a bug against. Available: vuetify, vuetify/docs, vuetify0, mcp, play, bin, studio, snips, link, issues

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

label

Optional label to pre-fill on the bug report.

Explain the meaning of this value, not just its name.

Annotations25/100

Declare destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

{
  "title": "Create bug report",
  "readOnlyHint": true
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "create_bug_report",
  "description": "Generate a link to the Vuetify issues site with the repository and bug report type pre-selected.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "repo"
    ],
    "properties": {
      "repo": {
        "enum": [
          "vuetify",
          "vuetify/docs",
          "vuetify0",
          "mcp",
          "play",
          "bin",
          "studio",
          "snips",
          "link",
          "issues"
        ],
        "type": "string",
        "description": "The repository to report a bug against. Available: vuetify, vuetify/docs, vuetify0, mcp, play, bin, studio, snips, link, issues"
      },
      "label": {
        "type": "string",
        "description": "Optional label to pre-fill on the bug report."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "title": "Create bug report",
    "readOnlyHint": true
  }
}

Put your MCP to the test

A few tasks worth trying with this server, chosen from its reviewed tools. These have not been run.

01Get feature guideGet the information about a specific feature in the documentation.
02Get installation guideGet detailed information about how to install Vuetify in a variety of environments.
03Get component API by versionReturn the API list for a Vuetify component
04Get release notes by versionGet release notes for one or more versions of Vuetify.
05Get Vuetify0 component guideGet detailed documentation and source code for a specific @vuetify/v0 component.

Want to run these tasks against your MCP server with us?

Test your MCP in Cloud Book a test call

About this server

Overview

Author: Vuetify
Verification: partner
Auth: None (public endpoint)
Category: Developer tools
Works with: claude
claude-api
claude-code
claude-desktop
Docs: Documentation

Tools (31)

create_bug_reportcreate_vuetify_bincreate_vuetify_linkcreate_vuetify_playgroundget_all_binsget_all_linksget_all_playgroundsget_binget_component_api_by_versionget_directive_api_by_versionget_exposed_exportsget_feature_guide+19 more

FAQ

Vuetify MCP setup, tools, quality score, publishing readiness, and alternatives.

How do I add Vuetify MCP to Claude, ChatGPT, or Cursor?

Add Vuetify MCP to Claude, ChatGPT, or Cursor by connecting its remote MCP URL in each client's MCP settings. In Claude, add a custom connector. In ChatGPT, add an MCP app. In Cursor, add an MCP server under Settings. The MCP URL is https://mcp.vuetifyjs.com/mcp.

Is Vuetify MCP MCP ready for ChatGPT and Claude?

As of October 5, 2026, Vuetify MCP scores 94/100 on Manufact's MCP publishing checklist. The scan does not yet meet ChatGPT publishing checks and meets Claude publishing checks. Passing these checks does not guarantee marketplace approval.

How clear is Vuetify MCP's MCP tool documentation?

As of October 5, 2026, Vuetify MCP scores 73/100 in Manufact's review of tool titles, descriptions, input and output schemas, and behavior annotations. The review covers 28 of 28 discovered tools. The quality score measures documentation clarity; runtime behavior and marketplace readiness require separate checks.

What tools does the Vuetify MCP MCP server provide?

Vuetify MCP lists 31 MCP tools, including create_bug_report, create_vuetify_bin, create_vuetify_link, create_vuetify_playground, get_all_bins, get_all_links, get_all_playgrounds, get_bin, get_component_api_by_version, get_directive_api_by_version, get_exposed_exports, and get_feature_guide.

What are the best alternatives to Vuetify MCP?

As of October 20, 2026, alternatives to Vuetify MCP in developer-tools on the Manufact MCP leaderboard include Held at the Gate, Speko, turva.dev, AgentMail, and AgentPhone.

Does Vuetify MCP MCP require authentication?

Vuetify MCP does not require authentication. It is a public MCP endpoint you can connect without logging in.

How can Vuetify MCP improve its MCP documentation?

get_release_notes_by_version is the lowest-scoring reviewed tool at 61/100. No output schema is declared. Add one for structured results so clients can interpret returned fields. Open its review for feedback and a copyable fix prompt, then rerun the documentation review after updating your tool metadata.

Who develops Vuetify MCP?

Vuetify MCP is developed by Vuetify. It is listed as partner on the Claude connector directory.

Not your MCP?

Review any public or OAuth MCP server for protocol compatibility, tool documentation, and ChatGPT and Claude publishing readiness. No account required.

Get your MCP score

Back to leaderboard

Opening your score report…