Ext Ops Panel
Open dashboard
Comparison

Git (Reference) vs mcp-logseq

Git (Reference) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 2 (Docker MCP Catalog, PyPI (MCP servers)). mcp-logseq is an MCP server published by ergut. Marketplaces we read that list it: 1 (PyPI (MCP servers)). As of our marketplace pass on 2026-11-10. 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)mcp-logseq
Docker MCP Catalog Listed
Version: sha256:ad6af958e794
Forks (GitHub): 11 930
Pulls (Docker Hub): 196 764
Stars (Docker Hub): 30
Stars (GitHub): 91 903
Not marked · First seen
Not listed
PyPI (MCP servers) Listed
Version: 2026.11.4
Downloads/month (PyPI): 175 042
Downloads/week (PyPI): 107 195
Forks (GitHub): 11 930
Stars (GitHub): 91 903
Not marked · First seen
Listed
Version: 1.10.0
Downloads/month (PyPI): 1 891
Downloads/week (PyPI): 152
Forks (GitHub): 51
Stars (GitHub): 350
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 mcp-logseq
FactGit (Reference)mcp-logseq
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)91 903 (better)350 (worse)
Pulls (Docker Hub) (differs)196 764No figure on Docker Hub
Forks (GitHub) (differs)11 930 (better)51 (worse)
Last release (differs)2026-11-05Not published
Where it runs (differs)On your machine (mcp/git)On your machine (mcp-logseq)
Transport (differs)stdioNot stated
Tools it declares (differs)12Not published
Environment variables it asks forNot publishedNot published
Licence (differs)NOASSERTIONMIT
Repository (differs)github.com/modelcontextprotocol/serversgithub.com/ergut/mcp-logseq
Changes in the last 7 days (differs)10
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.

mcp-logseq

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

MCP server to work with LogSeq via the local HTTP server

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

mcp-logseq

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 mcp-logseq 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: mcp-logseq · 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