Ext Ops Panel
Open dashboard
Comparison

distill vs SnapDoczilla

distill is a plugin bundle for AI coding tools published by UtkarshJain98. 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-15. 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
MarketplacedistillSnapDoczilla
Claude Code: claude-plugins-community Listed
Version: 0.2.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
Downloads/month (PyPI): 0
Downloads/week (PyPI): 139
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

distill vs SnapDoczilla
FactdistillSnapDoczilla
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub)00
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 bundle11
LicenceMITMIT
Repository (differs)github.com/utkarshjain98/distillgithub.com/julvc/skills
Changes in the last 7 days (differs)02
First seen2026-10-112026-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

distill

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

distill analyzes your codebase and generates structured context files in .claude/docs/. Instead of Claude reading source files to orient itself every session, it reads concise, pre-built docs on demand — testing.md when working on tests, api.md when working on endpoints, nothing when the task doesn't need it. Token cost becomes proportional to task relevance, not project size. Supports incremental updates (--update only regenerates stale docs), depth profiles (--lean for 30-line summaries, --deep for comprehensive reference), parallel generation for large doc sets, monorepo detection, team configuration via .distill.yml, and a pre-push hook that warns when docs drift.

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

distill As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install distill@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: distill · 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