dev-squad vs GitWhy — The Context Layer for Git
dev-squad is a plugin bundle for AI coding tools published by briannaworkman. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). GitWhy — The Context Layer for Git is an MCP server published by gitwhy-cli. Marketplaces we read that list it: 1 (Official MCP Registry). 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
| Marketplace |  dev-squad |  GitWhy — The Context Layer for Git |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: eb5e3c6 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.7.9 Downloads/month (npm): 151 Downloads/week (npm): 33 Forks (GitHub): 0 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
| Fact | dev-squad | GitWhy — The Context Layer for Git |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (gitwhy-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Parts of the bundle (differs) | 9 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/briannaworkman/dev-squad-plugin | github.com/gitwhy-cli/gitwhy |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-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
dev-squad
Spins up a full AI dev team to implement GitHub issues end-to-end and deliver a PR
GitWhy — The Context Layer for Git
The shared AI context engine for git — save, search, and share the reasoning behind code changes.
How to run each
dev-squad As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install dev-squad@claude-communityGitWhy — The Context Layer for Git As a local MCP server: npm package
claude mcp add --env "GITWHY_API_KEY=<YOUR_GITWHY_API_KEY>" --transport stdio gitwhy -- npx -y gitwhy-mcpRequires: GITWHY_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 dev-squad publish no settings it asks for, so we do not compare settings.
What it can do: dev-squad · What it can do: GitWhy — The Context Layer for 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.