Ext Ops Panel
Open dashboard
Comparison

Git (Reference) vs ws

Git (Reference) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). ws is a plugin bundle for AI coding tools published by n-filatov. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). 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
MarketplaceGit (Reference)ws
Docker MCP Catalog Listed
Version: sha256:ad6af958e794
Forks (GitHub): 11 780
Pulls (Docker Hub): 166 628
Stars (Docker Hub): 30
Stars (GitHub): 91 180
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 1.2.0
Forks (GitHub): 0
Stars (GitHub): 3
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

Git (Reference) vs ws
FactGit (Reference)ws
Marketplaces that list it11
Stars (GitHub) (differs)91 180 (better)3 (worse)
Pulls (Docker Hub) (differs)166 628No figure on Docker Hub
Forks (GitHub) (differs)11 780 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/git)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)12Not published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)Not a bundle9
Licence (differs)NOASSERTIONMIT
Repository (differs)github.com/modelcontextprotocol/serversgithub.com/n-filatov/ws
Changes in the last 7 days00
First seen (differs)2026-10-112026-10-12

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

Git (Reference)

In its own words, on Docker MCP Catalog:

Git repository interaction and automation.

ws

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

ws is a working set manager for Claude Code. Use /ws:map to describe a feature and Claude automatically identifies relevant files across your codebase, adding them to a focused, navigable list. Use /ws:install to set up the ws CLI on any OS. Working sets are branch-scoped and persistent — switch git branches and your context switches with you. Built for AI-assisted coding workflows where you need to track a curated set of files rather than browse your entire project tree.

How to run each

Git (Reference) As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio git -- docker run -i --rm mcp/git

ws

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

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

The marketplaces of ws publish no list of tools, so we do not compare tools.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: Git (Reference) · What it can do: ws · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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