Ext Ops Panel
Open dashboard
Comparison

caveman vs Git

caveman is a plugin bundle for AI coding tools published by JuliusBrussee. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Git is an MCP server published by Abhishekkumar2021. 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
MarketplacecavemanGit
Claude Code: claude-plugins-community Listed
Version: 3098342
Forks (GitHub): 6 487
Stars (GitHub): 111 856
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.0
Downloads/month (npm): 183
Downloads/week (npm): 32
Forks (GitHub): 0
Stars (GitHub): 1
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

caveman vs Git
FactcavemanGit
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)111 856 (better)1 (worse)
Forks (GitHub) (differs)6 487 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (@abhishekmcp/git)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 0
Hooks it runs (differs)2Not published
Parts of the bundle (differs)171
Licence (differs)Not statedMIT
Repository (differs)github.com/juliusbrussee/cavemangithub.com/abhishekkumar2021/mcp-suite
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

caveman

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

Auto-activation works differently per agent: Claude Code uses SessionStart hooks, this repo's Codex dogfood setup uses .codex/hooks.json, Gemini uses context files. Cursor/Windsurf/Cline/Copilot can be made always-on, but npx skills add installs only the skill, not the repo rule/instruction files. ¹ Codex uses $caveman syntax, not /caveman. This repo ships .codex/hooks.json, so caveman auto-starts when you run Codex inside this repo. The installed plugin itself gives you $caveman; copy the same hook into another repo if you want always-on behavior there too. caveman-commit and caveman-review are not in the Codex plugin bundle — use the SKILL.md files directly. ² Add the "Want it always on?" snippet below to those agents' system prompt or rule file if you want session-start activation. ³ Cursor and Windsurf receive the full SKILL.md with all intensity levels. Mode switching works on-demand via the skill; no slash command. ⁴ Available in Claude Code, but plugin install only nudges setup. Standalone install.sh /

Git

In its own words, on Official MCP Registry:

Local Git via MCP: status, log, diff, file history, branches, and gated stage/commit. Pure-JS.

How to run each

caveman As a Claude Code plugin

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

Git As a local MCP server: npm package

Claude Code
claude mcp add --env "GIT_ROOTS=<YOUR_GIT_ROOTS>" --transport stdio git -- npx -y @abhishekmcp/git

Requires: GIT_ROOTS

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 caveman publish no settings it asks for, so we do not compare settings.

What it can do: caveman · What it can do: Git · 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