Ext Ops Panel
Open dashboard
Comparison

Git (Reference) vs Library of Alexandria

Git (Reference) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 2 (Docker MCP Catalog, PyPI (MCP servers)). Library of Alexandria is an MCP server published by ltvspot. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. 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)Library of Alexandria
Docker MCP Catalog Listed
Version: sha256:ad6af958e794
Forks (GitHub): 11 923
Pulls (Docker Hub): 193 623
Stars (Docker Hub): 30
Stars (GitHub): 91 847
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 923
Stars (GitHub): 91 847
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.0
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 Library of Alexandria
FactGit (Reference)Library of Alexandria
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)91 847 (better)0 (worse)
Pulls (Docker Hub) (differs)193 623No figure on Docker Hub
Forks (GitHub) (differs)11 923 (better)0 (worse)
Last release (differs)2026-11-05Not published
Where it runs (differs)On your machine (mcp/git)Remote server (mcp.libraryofalexandria.com/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)12Not published
Environment variables it asks forNot publishedNot published
Licence (differs)NOASSERTIONNot stated
Repository (differs)github.com/modelcontextprotocol/serversgithub.com/ltvspot/library-of-alexandria-mcp
Changes in the last 7 days (differs)10
First seen (differs)2026-10-112026-10-26
Endpoint at the last check (differs)no remote endpoint we checkResponded 29 h ago

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.

Library of Alexandria

In its own words, on Official MCP Registry:

Classic books in 25 languages: search, print editions, the free shelf. Read-only, no sign-in.

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

Library of Alexandria As a remote MCP server

Claude Code
claude mcp add --transport http library-of-alexandria https://mcp.libraryofalexandria.com/mcp

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

Only Library of Alexandria has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of Library of Alexandria 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: Library of Alexandria · 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). 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