Ext Ops Panel
Open dashboard
Comparison

GitMCP vs cxpak

GitMCP is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). cxpak is a plugin bundle for AI coding tools published by Barnett-Studios. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). 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

Where each is published
MarketplaceGitMCPcxpak
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 3.1.3
Forks (GitHub): 2
Stars (GitHub): 31
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

GitMCP vs cxpak
FactGitMCPcxpak
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub31
Forks (GitHub) (differs)No figure on GitHub2
Last releaseNot publishedNot published
Where it runs (differs)Remote server (gitmcp.io/docs)Installs as a plugin bundle
Transport (differs)Streamable HTTPNot stated
Tools it declares (differs)5Not published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)Not a bundle8
Licence (differs)Apache-2.0MIT
Repository (differs)Not statedgithub.com/barnett-studios/cxpak
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)not checked yetno remote endpoint we check

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

GitMCP

In its own words, on Docker MCP Catalog:

Tools for interacting with Git repositories.

cxpak

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

Token-budgeted codebase context for Claude Code. One call to auto_context gives Claude the optimal context for any task — automatically selecting, ranking, noise-filtering, and packing the most relevant code from your entire codebase. 11 MCP tools including symbol tracing, blast radius analysis, API surface extraction, and semantic search. Supports 42 programming languages via tree-sitter.

How to run each

GitMCP

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

cxpak

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 cxpak 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: GitMCP · What it can do: cxpak · 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