Ext Ops Panel
Open dashboard
Comparison

hit-em-with-the-docs vs io.github.puglieseweb/systemdox

hit-em-with-the-docs is a plugin bundle for AI coding tools published by TheGlitchKing. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.puglieseweb/systemdox is an MCP server published by puglieseweb. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. 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
Marketplacehit-em-with-the-docsio.github.puglieseweb/systemdox
Claude Code: claude-plugins-community Listed
Version: 2.2.0
Forks (GitHub): 2
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.38
Downloads/month (npm): 1 124
Downloads/week (npm): 289
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

hit-em-with-the-docs vs io.github.puglieseweb/systemdox
Facthit-em-with-the-docsio.github.puglieseweb/systemdox
Marketplaces that list it11
Stars (GitHub) (differs)0No figure on GitHub
Forks (GitHub) (differs)2No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (@systemdox/mcp-server)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
Hooks it runs (differs)1Not published
Parts of the bundle (differs)5Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/theglitchking/hit-em-with-the-docsgithub.com/puglieseweb/product-systemdox
Changes in the last 7 days00
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

hit-em-with-the-docs

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

Self-managing documentation system with a 15-domain hierarchy, 22-field metadata schema, intelligent pattern discovery, and GitHub Actions automation. Generates and maintains hierarchical documentation with rich metadata, auto-discovers undocumented patterns, and self-heals stale or missing docs. Available as both a CLI tool and GitHub Action for CI/CD integration.

io.github.puglieseweb/systemdox

In its own words, on Official MCP Registry:

Your architecture in your agents' context: checks, specs, ADRs and docs over MCP, at write time.

How to run each

hit-em-with-the-docs As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install hit-em-with-the-docs@claude-community

io.github.puglieseweb/systemdox As a local MCP server: npm package

Claude Code
claude mcp add --env "SYSTEMDOX_API_KEY=<YOUR_SYSTEMDOX_API_KEY>" --transport stdio systemdox -- npx -y @systemdox/mcp-server

Requires: SYSTEMDOX_API_KEY (secret)

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

The marketplaces of hit-em-with-the-docs publish no settings it asks for, so we do not compare settings.

What it can do: hit-em-with-the-docs · What it can do: io.github.puglieseweb/systemdox · 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. 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