Ext Ops Panel
Open dashboard
Comparison

project-version-workflow vs Git

project-version-workflow is a plugin bundle for AI coding tools published by ATreep. 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-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

Where each is published
Marketplaceproject-version-workflowGit
Claude Code: claude-plugins-community Listed
Version: v260627-121434
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.0
Downloads/month (npm): 188
Downloads/week (npm): 25
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

project-version-workflow vs Git
Factproject-version-workflowGit
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)0 (worse)1 (better)
Forks (GitHub)00
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
Parts of the bundle (differs)31
Licence (differs)Not statedMIT
Repository (differs)github.com/atreep/project-version-workflowgithub.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

project-version-workflow

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

Manage project's versions and iterations by a standard workflow on Claude Code. Generates a daily version tag (e.g. v260416), records the changes in update_log.txt along with the git username when available, commits them, and optionally pushes to remote. It checks for a clean repo, asks you to confirm the change summary, warns about sensitive files, and never force-pushes.

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

project-version-workflow

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

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

What it can do: project-version-workflow · 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