Ext Ops Panel
Open dashboard
Comparison

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

memory-mcp is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑28.

memory-mcp is a plugin bundle for AI coding tools published by Michael Denyer. 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-11-13. 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
Marketplacememory-mcpio.github.neo4j-contrib/mcp-neo4j-memory
Community marketplace michael-denyer/memory-mcp Removed on 2026-10-28
Version: 0.8.0
Forks (GitHub): 2
Stars (GitHub): 14
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
Downloads/month (PyPI): 23 826
Downloads/week (PyPI): 4 464
Forks (GitHub): 262
Stars (GitHub): 989
Not marked · First seen
Docker MCP Catalog Not listed Listed
Version: sha256:0f04105a1006
Forks (GitHub): 262
Pulls (Docker Hub): 46 196
Stars (Docker Hub): 9
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

memory-mcp vs io.github.neo4j-contrib/mcp-neo4j-memory
Factmemory-mcpno longer listed · io.github.neo4j-contrib/mcp-neo4j-memory
Marketplaces that list it (differs)02
Stars (GitHub) (differs)14989
Pulls (Docker Hub) (differs)No figure on Docker Hub46 196
Forks (GitHub) (differs)2262
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (mcp-neo4j-memory)
Transport (differs)Not statedstdio
Tools it declares (differs)Not published9
Environment variables it asks for (differs)Not published10, secrets among them: 1
Hooks it runs (differs)4Not published
Parts of the bundle (differs)17Not a bundle
LicenceMITMIT
Repository (differs)github.com/michael-denyer/memory-mcpgithub.com/neo4j-contrib/mcp-neo4j
Changes in the last 7 days00
First seen (differs)2026-10-142026-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 memory-mcp

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

  • XMemo

    Shared, governed long-term memory for AI agents across tools and sessions via MCP and REST.

    by yonro · MCP server

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

  • Pryzm Memory

    Encrypted long-term memory shared across your AI assistants (Claude, ChatGPT, Perplexity).

    by pryzm-memory.com · MCP server

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

  • MemoCat — Shared AI Memory

    One shared, persistent memory across AI agents and systems, with semantic recall and live updates.

    by MontyGovernance · MCP server

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

  • ourmem

    Persistent memory for Claude Code — memories survive across sessions, projects, and machines

    by ourmem · Plugin bundle

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

  • agentcairn

    Local-first agent memory for Claude Code — recall, remember, ambient capture.

    by Charles C. Figueiredo · Plugin bundle

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

  • engram

    Persistent memory with session tracking, compaction recovery, and Memory Protocol. Gives Claude a brain that survives across sessions.

    by Gentleman Programming · Plugin bundle

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

Its card, with similar plugins by marketplace

What each says it does

memory-mcp

In its own words, on Community GitHub marketplaces:

Persistent memory for Claude Code with hot cache instant recall and semantic search. Give your AI assistant a second brain.

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

memory-mcp

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 memory-mcp publish no list of tools, so we do not compare tools.

Settings each asks for

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

What it can do: memory-mcp · 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 . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built