Ext Ops Panel
Open dashboard
Comparison

vue-lsp vs io.github.Alberto-Codes/docvet

vue-lsp is a plugin bundle for AI coding tools published by popov-do. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.Alberto-Codes/docvet is an MCP server published by Alberto-Codes. Marketplaces we read that list it: 3 (Official MCP Registry, Claude Code: claude-plugins-community, Community GitHub marketplaces). As of our marketplace pass on 2026-10-21. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacevue-lspio.github.Alberto-Codes/docvet
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 1
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 1.15.1
Forks (GitHub): 1
Stars (GitHub): 9
Not marked · First seen
Official MCP Registry Not listed Listed
Version: 3.0.0
Downloads/month (PyPI): 14 540
Downloads/week (PyPI): 1 669
Forks (GitHub): 1
Stars (GitHub): 9
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

vue-lsp vs io.github.Alberto-Codes/docvet
Factvue-lspio.github.Alberto-Codes/docvet
Marketplaces that list it (differs)1 (worse)3 (better)
Stars (GitHub) (differs)1 (worse)9 (better)
Forks (GitHub)11
Last release (differs)Not published2026-10-21
Where it runs (differs)Installs as a plugin bundleOn your machine (docvet)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)1Not published
Parts of the bundle (differs)1Not a bundle
LicenceMITMIT
Repository (differs)github.com/popov-do/vue-lspgithub.com/alberto-codes/docvet
Changes in the last 7 days (differs)05
First seen (differs)2026-10-122026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

vue-lsp

In its own words, on Claude Code: claude-plugins-community:

Vue 3 LSP plugin for Claude Code. Combines vue-language-server (Volar v3) with typescript-language-server into a single LSP server, providing full TypeScript intelligence for .vue files — hover, go-to-definition, references, document symbols, call hierarchy, diagnostics, completions, and rename.

io.github.Alberto-Codes/docvet

In its own words, on Official MCP Registry:

Docstring quality vetting for Python -- enrichment, freshness, coverage, and presence checks

How to run each

vue-lsp As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install vue-lsp@claude-community

io.github.Alberto-Codes/docvet As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio docvet -- uvx docvet

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: vue-lsp · What it can do: io.github.Alberto-Codes/docvet · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built