Ext Ops Panel
Open dashboard
Comparison

GitMCP vs git-workflow-expert

GitMCP is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). git-workflow-expert is a plugin bundle for AI coding tools published by curiositech. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-11-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
MarketplaceGitMCPgit-workflow-expert
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Community marketplace curiositech/some_claude_skills Not listed Listed
Version: not stated
Forks (GitHub): 44
Stars (GitHub): 265
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 git-workflow-expert
FactGitMCPgit-workflow-expert
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub265
Forks (GitHub) (differs)No figure on GitHub44
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
Licence (differs)Apache-2.0Not stated
Repository (differs)Not statedgithub.com/curiositech/some_claude_skills
Changes in the last 7 days00
First seen (differs)2026-10-112026-10-15
Endpoint at the last check (differs)Responded 4 h agono 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.

git-workflow-expert

In its own words, on Community GitHub marketplaces:

Git branching strategies, conflict resolution, rebase workflows, monorepo patterns, and advanced operations like cherry-pick, bisect, and reflog recovery. Activate on "git", "branching strategy", "merge conflict", "rebase", "cherry-pick", "monorepo git", "git bisect", "git reflog", "squash commits". NOT for GitHub Actions CI/CD (use github-actions-pipeline-builder), GitHub API/webhooks, or PR review processes (use code-review-checklist).

How to run each

GitMCP As a remote MCP server

Claude Code
claude mcp add --transport http gitmcp https://gitmcp.io/docs

git-workflow-expert As a Claude Code plugin

Claude Code
/plugin marketplace add curiositech/some_claude_skills
/plugin install git-workflow-expert@some-claude-skills

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

Only GitMCP has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of git-workflow-expert 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: git-workflow-expert · Compare two other plugins

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