Comparison

graphmem vs io.github.neo4j-contrib/mcp-neo4j-memory

graphmem is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑23.

graphmem is a plugin bundle for AI coding tools published by Graphmem. No marketplace we read lists it any more. 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-23. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplace	graphmem	io.github.neo4j-contrib/mcp-neo4j-memory
Community marketplace sonic182/graphmem	Removed on 2026-10-23 Version: 0.14.0 Forks (GitHub): 0 Stars (GitHub): 8 Not marked · First seen 2026-10-14	Not listed
Official MCP Registry	Not listed	Listed Version: 1.0.0 Downloads/month (PyPI): 23 826 Downloads/week (PyPI): 3 565 Forks (GitHub): 264 Stars (GitHub): 989 Not marked · First seen 2026-10-11
Docker MCP Catalog	Not listed	Listed Version: sha256:0f04105a1006 Forks (GitHub): 264 Pulls (Docker Hub): 38 815 Stars (Docker Hub): 9 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

graphmem vs io.github.neo4j-contrib/mcp-neo4j-memory
Fact	graphmemno longer listed · 2026-10-23	io.github.neo4j-contrib/mcp-neo4j-memory
Marketplaces that list it (differs)	0	2
Stars (GitHub) (differs)	8	989
Pulls (Docker Hub) (differs)	No figure on Docker Hub	38 815
Forks (GitHub) (differs)	0	264
Last release	Not published	Not published
Where it runs (differs)	Installs as a plugin bundle	On your machine (mcp-neo4j-memory)
Transport (differs)	Not stated	stdio
Tools it declares (differs)	Not published	9
Environment variables it asks for (differs)	Not published	10, secrets among them: 1
Hooks it runs (differs)	2	Not published
Parts of the bundle (differs)	7	Not a bundle
Licence	MIT	MIT
Repository (differs)	github.com/sonic182/graphmem	github.com/neo4j-contrib/mcp-neo4j
Changes in the last 7 days (differs)	5	0
First seen (differs)	2026-10-14	2026-10-11

Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.

What to use instead of graphmem

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

remem-mcp — Local-first MCP Memory + CodeGraph + Wiki

Local-first memory for AI coding agents. Memory + CodeGraph + Wiki in one SQLite file.

by tinhien11 · MCP server

Listed on: Official MCP Registry, npm registry (MCP servers) · Describes nearly the same job
claude-memory

Long-term memory for Claude Code. Recalls architecture, conventions, and decisions across sessions, plus an episodic observation log of what happened — so Claude explains your…

by Valentino Stoll · Plugin bundle

Listed on: Community GitHub marketplaces · Describes nearly the same job
memora

Persistent semantic memory for Claude Code — auto-injects relevant context at session start, captures git commits, test results, and research via hooks, and provides 30+ MCP tools…

by agentic-mcp-tools · Plugin bundle

Listed on: Community GitHub marketplaces · Describes nearly the same job
agent-knowledge io.github.keshrath/agent-knowledge

Cross-session memory for AI agents - knowledge graph, scoring, semantic search

by keshrath · MCP server

Listed on: Official MCP Registry, Claude Code: claude-plugins-community, Community GitHub marketplaces · Describes nearly the same job
Tentra — Memory for AI Coding Agents

Memory for AI coding agents. Call graphs + refactor safety + persistent code context. 35 MCP tools.

by rdanieli · MCP server

Listed on: Official MCP Registry · Describes nearly the same job
leankg

Lightweight knowledge graph for AI-assisted development. Impact analysis, code search, dependency tracking, and context generation.

by FreePeak · Plugin bundle

Listed on: Community GitHub marketplaces · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

graphmem

In its own words, on Community GitHub marketplaces:

Recall and store durable engineering knowledge over a local MCP server.

io.github.neo4j-contrib/mcp-neo4j-memory

In its own words, on Official MCP Registry:

MCP Neo4j Knowledge Graph Memory Server

How to run each

graphmem

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

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

Claude Code

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-memory

Requires: 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

The marketplaces of graphmem publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of graphmem publish no settings it asks for, so we do not compare settings.

What it can do: graphmem · What it can do: io.github.neo4j-contrib/mcp-neo4j-memory · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on 2026-10-23. We publish no contact details for plugin publishers.