Memory (Reference) vs io.github.neo4j-contrib/mcp-neo4j-memory
Memory (Reference) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.neo4j-contrib/mcp-neo4j-memory is an MCP server published by neo4j-contrib. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). As of our marketplace pass on 2026-10-25. 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
| Marketplace |  Memory (Reference) |  io.github.neo4j-contrib/mcp-neo4j-memory |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:db0c2db07a44 Forks (GitHub): 11 868 Pulls (Docker Hub): 562 923 Stars (Docker Hub): 26 Stars (GitHub): 91 555 Not marked · First seen |
Listed Version: sha256:0f04105a1006 Forks (GitHub): 264 Pulls (Docker Hub): 39 966 Stars (Docker Hub): 9 Stars (GitHub): 989 Not marked · First seen |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 Downloads/month (PyPI): 23 826 Downloads/week (PyPI): 7 866 Forks (GitHub): 264 Stars (GitHub): 989 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
| Fact | Memory (Reference) | io.github.neo4j-contrib/mcp-neo4j-memory |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 91 555 (better) | 989 (worse) |
| Pulls (Docker Hub) (differs) | 562 923 (better) | 39 966 (worse) |
| Forks (GitHub) (differs) | 11 868 (better) | 264 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/memory) | On your machine (mcp-neo4j-memory) |
| Transport | stdio | stdio |
| Tools it declares | 9 | 9 |
| Environment variables it asks for (differs) | Not published | 10, secrets among them: 1 |
| Licence (differs) | NOASSERTION | MIT |
| Repository (differs) | github.com/modelcontextprotocol/servers | github.com/neo4j-contrib/mcp-neo4j |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
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
Memory (Reference)
Knowledge graph-based persistent memory system.
io.github.neo4j-contrib/mcp-neo4j-memory
MCP Neo4j Knowledge Graph Memory Server
How to run each
Memory (Reference) As a local MCP server: Docker image
claude mcp add --transport stdio memory -- docker run -i --rm mcp/memoryio.github.neo4j-contrib/mcp-neo4j-memory As a local MCP server: PyPI package
claude mcp add --env "NEO4J_PASSWORD=<YOUR_NEO4J_PASSWORD>" --env "NEO4J_URI=<YOUR_NEO4J_URI>" --env "NEO4J_USERNAME=<YOUR_NEO4J_USERNAME>" --transport stdio mcp-neo4j-memory -- uvx mcp-neo4j-memoryRequires: NEO4J_PASSWORD (secret), NEO4J_URI, NEO4J_USERNAME
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Only Memory (Reference) declares
open_nodessearch_nodes
Only io.github.neo4j-contrib/mcp-neo4j-memory declares
find_memories_by_namesearch_memories
Both declare
add_observationscreate_entitiescreate_relationsdelete_entitiesdelete_observationsdelete_relationsread_graph
Tool names as each marketplace publishes them. More tools is not better in itself: compare what each needs for the job.
Settings each asks for
The marketplaces of Memory (Reference) publish no settings it asks for, so we do not compare settings.
What it can do: Memory (Reference) · What it can do: io.github.neo4j-contrib/mcp-neo4j-memory · 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.