Ext Ops Panel
Open dashboard
Comparison

Git (Reference) vs contextweave-mcp

Git (Reference) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 2 (Docker MCP Catalog, PyPI (MCP servers)). contextweave-mcp is an MCP server published by matthew-brough. Marketplaces we read that list it: 1 (PyPI (MCP servers)). As of our marketplace pass on 2026-11-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
MarketplaceGit (Reference)contextweave-mcp
Docker MCP Catalog Listed
Version: sha256:ad6af958e794
Forks (GitHub): 11 968
Pulls (Docker Hub): 202 475
Stars (Docker Hub): 30
Stars (GitHub): 92 004
Not marked · First seen
Not listed
PyPI (MCP servers) Listed
Version: 2026.11.11
Downloads/month (PyPI): 175 042
Downloads/week (PyPI): 107 195
Forks (GitHub): 11 968
Stars (GitHub): 92 004
Not marked · First seen
Listed
Version: 0.6.5
Downloads/month (PyPI): 0
Downloads/week (PyPI): 184
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

Git (Reference) vs contextweave-mcp
FactGit (Reference)contextweave-mcp
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)92 004 (better)0 (worse)
Pulls (Docker Hub) (differs)202 475No figure on Docker Hub
Forks (GitHub) (differs)11 968 (better)0 (worse)
Last release (differs)2026-11-11 (better)2026-11-05 (worse)
Where it runs (differs)On your machine (mcp/git)On your machine (contextweave-mcp)
Transport (differs)stdioNot stated
Tools it declares (differs)12Not published
Environment variables it asks forNot publishedNot published
Licence (differs)NOASSERTIONMPL-2.0
Repository (differs)github.com/modelcontextprotocol/serversgithub.com/matthew-brough/contextweave
Changes in the last 7 days11
First seen (differs)2026-10-112026-10-14

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.

contextweave-mcp

In its own words, on PyPI (MCP servers):

Unified code-context MCP server: structural, lexical and semantic retrieval

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

contextweave-mcp

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 contextweave-mcp 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: contextweave-mcp · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Package data comes from the Python Package Index (pypi.org). 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