caveman vs GitHub
caveman is a plugin bundle for AI coding tools published by JuliusBrussee. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). GitHub is an MCP server published by github. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). As of our marketplace pass on 2026-10-12. 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 | ||
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 3098342 Forks (GitHub): 6 428 Stars (GitHub): 111 029 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.0.2 Forks (GitHub): 5 131 Stars (GitHub): 33 515 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:ffced0d76e77 Forks (GitHub): 5 131 Stars (GitHub): 33 515 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 | caveman | GitHub |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 111 029 (better) | 33 515 (worse) |
| Forks (GitHub) (differs) | 6 428 (better) | 5 131 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server or your machine |
| Transport (differs) | Not stated | Streamable HTTP, stdio |
| Tools it declares (differs) | Not published | 40 |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Hooks it runs (differs) | 2 | Not published |
| Parts of the bundle (differs) | 17 | Not a bundle |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/juliusbrussee/caveman | github.com/github/github-mcp-server |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | not checked yet |
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
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 /
GitHub
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
How to run each
caveman
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
GitHub As a local MCP server: Docker image
claude mcp add --env "GITHUB_PERSONAL_ACCESS_TOKEN=<YOUR_GITHUB_PERSONAL_ACCESS_TOKEN>" --transport stdio github-official -- docker run -i --rm -e GITHUB_PERSONAL_ACCESS_TOKEN ghcr.io/github/github-mcp-serverRequires: GITHUB_PERSONAL_ACCESS_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of caveman publish no list of tools, so we do not compare tools.
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: GitHub · 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 the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.