Vuetify MCP
Capped at 90: 2 of 3 real tool calls passed in our test; the tests add up to 100. Why scores are capped
Test points add up to 100; the score is capped at 90 because not every real tool call passed. Not a quality or security rating. Why scores are capped
Test points before the cap (100/100)
- Install20/20
- Handshake30/30
- Maintenance25/25
- Docs15/15
- License10/10
Tested npm @vuetify/mcp 0.12.2 (MIT; repo vuetifyjs/mcp). Installed pinned with scripts off (npm --ignore-scripts) and launched: initialize and tools/list over stdio succeeded with no credentials and listed 38 tools (38 annotated by the server: 33 read-only, 5 destructive). Real calls: 2 of 3 real function calls passed.
Tool-call test (2026-11-19 UTC, direct MCP stdio client, no LLM): partial. 2 of 3 real function calls passed. Evidence: local test run, Nov 19, 2026 UTC.
Transport (tested 2026-11-19 UTC): stdio
Token cost (estimate): approx. 4479 tokens, cl100k estimate (38 tools, measured 2026-11-19 UTC, version 0.12.2). This is an estimate from our testing of the tool names, descriptions and input schemas, counted with cl100k_base.
Permissions: 32 read, 6 write (state-changing), 0 unclassified · Auth: none · Rate limit: unknown · Pricing unit: unknown
Auth: none. Rate limit: unknown. Pricing unit: unknown.
create_bug_report— write (state-changing)create_vuetify_bin— write (state-changing)create_vuetify_link— write (state-changing)create_vuetify_playground— write (state-changing)get_all_bins— readget_all_links— readget_all_playgrounds— readget_bin— readget_component_api_by_version— readget_directive_api_by_version— readget_exposed_exports— readget_feature_guide— readget_feature_guides— readget_frequently_asked_questions— readget_installation_guide— readget_migration_receipt_schema— readget_playground— readget_release_notes_by_version— readget_upgrade_guide— readget_upgrade_plan— readget_upgrade_rules— readget_v2_to_v3_component_map— readget_v3_breaking_changes— readget_v3_upgrade_baseline_recipe— readget_v3_upgrade_playbook— readget_v4_breaking_changes— readget_vuetify0_component_guide— readget_vuetify0_component_list— readget_vuetify0_composable_guide— readget_vuetify0_composable_list— readget_vuetify0_exports_list— readget_vuetify0_installation_guide— readget_vuetify0_package_guide— readget_vuetify0_skill— readget_vuetify_api_by_version— readget_vuetify_one_installation_guide— readupdate_vuetify_bin— write (state-changing)update_vuetify_playground— write (state-changing)
handshake and tools listed without a recorded key or OAuth
Score 90/100 · Tools 38 · Token cost approx. 4,479 tokens · Compare · Last tested 2026-11-19 UTC · Version tested 0.12.2 · Package @vuetify/mcp · Repo vuetifyjs/mcp
Summary: Vuetify MCP completed an MCP handshake without credentials and exposed 38 tools.
Evidence summary
- Handshake
- pass
- Tools listed
- 38
- Context cost
- approx. 4479 tokens, cl100k estimate (38 tools, measured 2026-11-19 UTC, version 0.12.2; an estimate) ranking · add up your servers' context cost
- API key
- No key needed for the tools we called
- Tested
- 2026-11-19 UTC
Test results
| Test | Result | Points | Evidence |
|---|---|---|---|
| install | pass | 20 | npm install @vuetify/mcp --ignore-scripts (Node v24.22.1, Linux) succeeded in 1s. |
| handshake | pass | 30 | MCP initialize + tools/list over stdio succeeded with no credentials; 38 tools listed in 1.6s. |
| maintenance | pass | 25 | Repo pushed 27 days before test; 115 GitHub stars. |
| docs | pass | 15 | README over 3,000 chars; install instructions present; mcpServers config example present. Check of the package's own README (README shipped in npm package). |
| license | pass | 10 | MIT (OSI-approved). |
Local-model readiness
Token cost (estimate): approx. 4479 tokens, cl100k estimate for 38 tools · about 55% of an 8k context. This is an estimate from our testing (counted with cl100k_base).
Small-model friendly (schema heuristic, not a model result): unknown.
Not tested
Small-model task runs: Not yet tested.
What we tested and what we didn't
Tested on 2026-11-19 UTC
- Install from the registry
- We connected with no credentials and asked for its tool list: it listed 38 tools (Method details: MCP
initializethentools/list) - Maintenance signals (last push, archived/deprecated status)
- Docs (README length, install and config example)
- License (OSI-approved or not)
- Token cost (estimate)
Not tested
- Security: not audited (no code review, no permission or data-flow analysis)
- Real tasks (no functional task runs yet)
- Behaviour with real credentials or a real account
- Performance, rate limits or load
- Correctness of results beyond the listed tasks
Methodology: how we test. A high score means it installs and responds, not that giving it access to your data carries no risk.
Known security issues
Not yet checked.
Monthly roundup: MCP security issues, October 2026.
Tool list changes
Baseline recorded from the 2026-11-19 UTC test run; changes appear after the next test.
Snapshot hash (fingerprint of the tool list)
40902df6b863: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed.
Raw test record (JSON)
{
"name": "@vuetify/mcp",
"version": "0.12.2",
"registry": "npm",
"status": "working",
"tested": "2026-11-19",
"tools_count": 38,
"deprecated": false,
"archived": false,
"tests": {
"install": [
"pass",
20,
"`npm install @vuetify/mcp --ignore-scripts` (Node v24.22.1, Linux) succeeded in 1s."
],
"handshake": [
"pass",
30,
"MCP `initialize` + `tools/list` over stdio succeeded with no credentials; 38 tools listed in 1.6s."
],
"maintenance": [
"pass",
25,
"Repo pushed 27 days before test; 115 GitHub stars."
],
"docs": [
"pass",
15,
"README over 3,000 chars; install instructions present; `mcpServers` config example present. Check of the package's own README (README shipped in npm package)."
],
"license": [
"pass",
10,
"MIT (OSI-approved)."
]
},
"testedAt": "2026-11-19T06:10:29.927Z"
}Install
npx -y @vuetify/mcp
Pin the version we tested
npx -y --ignore-scripts @vuetify/mcp@0.12.2
tested 2026-11-19 UTC. Newer versions may differ and were not tested by us.
{
"mcpServers": {
"vuetify-mcp": {
"command": "npx",
"args": [
"-y",
"@vuetify/mcp@0.12.2"
]
}
}
}Tools listed
get_vuetify_api_by_version, get_component_api_by_version, get_directive_api_by_version, get_installation_guide, get_feature_guides, get_feature_guide, get_exposed_exports, get_frequently_asked_questions, get_release_notes_by_version, get_vuetify_one_installation_guide, get_upgrade_guide, get_upgrade_plan, get_upgrade_rules, get_migration_receipt_schema, get_v4_breaking_changes, get_v3_breaking_changes, get_v2_to_v3_component_map, get_v3_upgrade_playbook, get_v3_upgrade_baseline_recipe, get_vuetify0_installation_guide, get_vuetify0_package_guide, get_vuetify0_composable_list, get_vuetify0_component_list, get_vuetify0_composable_guide, get_vuetify0_component_guide, get_vuetify0_exports_list, get_vuetify0_skill, create_bug_report, create_vuetify_bin, get_all_bins, update_vuetify_bin, get_bin, create_vuetify_link, get_all_links, create_vuetify_playground, get_all_playgrounds, update_vuetify_playground, get_playground
Quick config
{
"mcpServers": {
"vuetify-mcp": {
"command": "npx",
"args": [
"-y",
"@vuetify/mcp"
]
}
}
}Add to config Opens the config generator with this server selected.
Setup
- Install. Run
npm install @vuetify/mcp --ignore-scripts(Node v24.22.1). This is the exact command we ran on 2026-11-19 UTC. - Configure. Add the mcpServers entry below to your MCP client config.
- Verify. Restart the client and check that tools/list returns tools (38 in our test).
{
"mcpServers": {
"vuetify-mcp": {
"command": "npx",
"args": [
"-y",
"@vuetify/mcp"
]
}
}
}Test history
- 2026-11-19 UTC: New
Related: Best design MCP servers
FAQ
Is Vuetify MCP deprecated?
No. Vuetify MCP was not deprecated or archived when we last tested it on 2026-11-19 UTC.
What replaces Vuetify MCP?
Nothing; Vuetify MCP is not deprecated as of 2026-11-19 UTC.
Does Vuetify MCP need an API key?
No. It completed an MCP handshake with no credentials and listed 38 tools.
Embed the badge
Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.