Ext Ops Panel
Open dashboard
Comparison

GitMCP vs gitpro

GitMCP is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). gitpro is an MCP server published by Yantrakar. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. 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
MarketplaceGitMCPgitpro
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.4.3
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

GitMCP vs gitpro
FactGitMCPgitpro
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub1
Forks (GitHub) (differs)No figure on GitHub0
Last release (differs)Not published2026-10-21
Where it runs (differs)Remote server (gitmcp.io/docs)On your machine (gitpro)
Transport (differs)Streamable HTTPstdio
Tools it declares (differs)5Not published
Environment variables it asks forNot publishedNot published
Licence (differs)Apache-2.0Not stated
Repository (differs)Not statedgithub.com/yantrakar/gitpro
Changes in the last 7 days (differs)06
First seen (differs)2026-10-112026-10-15
Endpoint at the last check (differs)Responded 31 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.

gitpro

In its own words, on Official MCP Registry:

Read-only checks of which git name, email and SSH key a repository uses, and why.

How to run each

GitMCP As a remote MCP server

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

gitpro As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio gitpro -- uvx gitpro mcp

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

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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