Ext Ops Panel
Open dashboard
Comparison

sync-docs vs SnapDoczilla

sync-docs is a plugin bundle for AI coding tools published by agent-sh. 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: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-13. 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
Marketplacesync-docsSnapDoczilla
Claude Code: claude-plugins-community Listed
Version: 5.1.0
Forks (GitHub): 0
Stars (GitHub): 3
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
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

sync-docs vs SnapDoczilla
Factsync-docsSnapDoczilla
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)3 (better)0 (worse)
Forks (GitHub) (differs)0 (worse)1 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (snapdoczilla-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)31
LicenceMITMIT
Repository (differs)github.com/agent-sh/sync-docsgithub.com/julvc/skills
Changes in the last 7 days (differs)02
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

sync-docs

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

Detect outdated documentation by comparing docs against actual code state — broken references, version mismatches, stale code examples, and missing CHANGELOG entries. Documentation drifts from code silently: a function gets renamed, an import path changes, a version bumps, but the README and CHANGELOG still reference the old state. `/sync-docs` compares documentation files against the current codebase, finds the gaps, and auto-applies safe fixes (version updates, CHANGELOG entries) while flagging ambiguous cases (removed exports referenced in docs, code examples needing context) for manual review. Plug into /next-task and /prepare-delivery as the pre-ship docs gate.

SnapDoczilla

In its own words, on Official MCP Registry:

Offline docs-as-code for any backend and frontend: a MkDocs site in your repo, by your AI agent.

How to run each

sync-docs As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install sync-docs@claude-community

SnapDoczilla As a local MCP server: PyPI package

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

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: sync-docs · 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.

Where the data comes from: how the catalog is built