vibe-doc vs SnapDoczilla
vibe-doc is a plugin bundle for AI coding tools published by estevanhernandez-stack-ed. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). SnapDoczilla is an MCP server published by julvc. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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
| Marketplace |  vibe-doc |  SnapDoczilla |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 0.8.2 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.2.0 Downloads/month (PyPI): 0 Downloads/week (PyPI): 25 Forks (GitHub): 1 Stars (GitHub): 0 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
| Fact | vibe-doc | SnapDoczilla |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 0 (worse) | 1 (better) |
| Last release (differs) | Not published | 2026-10-21 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (snapdoczilla-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 12 | Not a bundle |
| Licence | MIT | MIT |
| Repository (differs) | github.com/estevanhernandez-stack-ed/vibe-doc | github.com/julvc/skills |
| Changes in the last 7 days (differs) | 0 | 1 |
| First seen (differs) | 2026-10-12 | 2026-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
vibe-doc
Vibe Doc is an AI-powered documentation gap analyzer for any codebase. It scans your project's artifacts, classifies the project type (web app, API, data pipeline, Claude Code plugin, etc.), measures coverage against a tier-appropriate documentation matrix, and either generates the missing docs from your existing artifacts or hands you a ranked list of gaps to close. Five slash commands cover the loop: /vibe-doc:scan (analyze), /vibe-doc:generate (write missing docs), /vibe-doc:check (CI deployment-readiness gate), /vibe-doc:status (snapshot), and /vibe-doc:evolve (Level-3 self-improvement — the plugin reads its own session logs and proposes SKILL improvements). Honest about coverage: no cherry-picked denominators, no false negatives the matcher has learned to flag.
SnapDoczilla
Offline docs-as-code for any backend and frontend: a MkDocs site in your repo, by your AI agent.
How to run each
vibe-doc As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install vibe-doc@claude-communitySnapDoczilla As a local MCP server: PyPI package
claude mcp add --transport stdio snapdoczilla -- uvx snapdoczilla-mcpCommands 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: vibe-doc · What it can do: SnapDoczilla · 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.