Comparison

Memory (Reference) vs io.github.neo4j-contrib/mcp-neo4j-data-modeling

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-data-modeling 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-26. 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
Marketplace	Memory (Reference)	io.github.neo4j-contrib/mcp-neo4j-data-modeling
Docker MCP Catalog	Listed Version: sha256:db0c2db07a44 Forks (GitHub): 11 868 Pulls (Docker Hub): 563 220 Stars (Docker Hub): 26 Stars (GitHub): 91 555 Not marked · First seen 2026-10-11	Listed Version: sha256:3c72de00df50 Forks (GitHub): 264 Pulls (Docker Hub): 24 188 Stars (Docker Hub): 1 Stars (GitHub): 989 Not marked · First seen 2026-10-11
Official MCP Registry	Not listed	Listed Version: 1.0.0 Downloads/month (PyPI): 2 484 Downloads/week (PyPI): 115 Forks (GitHub): 264 Stars (GitHub): 989 Not marked · First seen 2026-10-11

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

Memory (Reference) vs io.github.neo4j-contrib/mcp-neo4j-data-modeling
Fact	Memory (Reference)	io.github.neo4j-contrib/mcp-neo4j-data-modeling
Marketplaces that list it (differs)	1 (worse)	2 (better)
Stars (GitHub) (differs)	91 555 (better)	989 (worse)
Pulls (Docker Hub) (differs)	563 220 (better)	24 188 (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-data-modeling)
Transport	stdio	stdio
Tools it declares (differs)	9	16
Environment variables it asks for (differs)	Not published	6, secrets among them: 0
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)

In its own words, on Docker MCP Catalog:

Knowledge graph-based persistent memory system.

io.github.neo4j-contrib/mcp-neo4j-data-modeling

In its own words, on Official MCP Registry:

A simple Neo4j MCP server for creating graph data models.

How to run each

Memory (Reference) As a local MCP server: Docker image

Claude Code

claude mcp add --transport stdio memory -- docker run -i --rm mcp/memory

io.github.neo4j-contrib/mcp-neo4j-data-modeling As a local MCP server: PyPI package

Claude Code

claude mcp add --transport stdio mcp-neo4j-data-modeling -- uvx mcp-neo4j-data-modeling

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

add_observations
create_entities
create_relations
delete_entities
delete_observations
delete_relations
open_nodes
read_graph
search_nodes

Only io.github.neo4j-contrib/mcp-neo4j-data-modeling declares

export_to_arrows_json
export_to_neo4j_graphrag_pkg_schema
export_to_owl_turtle
export_to_pydantic_models
get_constraints_cypher_queries
get_example_data_model
get_mermaid_config_str
get_node_cypher_ingest_query
get_relationship_cypher_ingest_query
list_example_data_models
load_from_arrows_json
load_from_neo4j_graphrag_pkg_schema

Show the remaining 4

load_from_owl_turtle
validate_data_model
validate_node
validate_relationship

Both declare

None

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-data-modeling · 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 2026-10-26. We publish no contact details for plugin publishers.