Ext Ops Panel
Open dashboard
Comparison

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

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

Itsuki Memory is a plugin bundle for AI coding tools published by Itsuki. 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-28. 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
MarketplaceItsuki Memoryio.github.neo4j-contrib/mcp-neo4j-memory
Community marketplace 12ziyad/universal-memory-engine Removed on 2026-10-28
Version: 0.7.0
Forks (GitHub): 4
Stars (GitHub): 13
Not marked · First seen
Not listed
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
Docker MCP Catalog Not listed Listed
Version: sha256:0f04105a1006
Forks (GitHub): 264
Pulls (Docker Hub): 40 985
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

Itsuki Memory vs io.github.neo4j-contrib/mcp-neo4j-memory
FactItsuki Memoryno longer listed · io.github.neo4j-contrib/mcp-neo4j-memory
Marketplaces that list it (differs)02
Stars (GitHub) (differs)13989
Pulls (Docker Hub) (differs)No figure on Docker Hub40 985
Forks (GitHub) (differs)4264
Last releaseNot publishedNot published
Where it runs (differs)Remote server (itsuki.app/mcp)On your machine (mcp-neo4j-memory)
Transport (differs)Streamable HTTPstdio
Tools it declares (differs)Not published9
Environment variables it asks for (differs)Not published10, secrets among them: 1
Hooks it runs (differs)3Not published
Parts of the bundle (differs)5Not a bundle
Licence (differs)Apache-2.0MIT
Repository (differs)github.com/12ziyad/universal-memory-enginegithub.com/neo4j-contrib/mcp-neo4j
Changes in the last 7 days (differs)20
First seen (differs)2026-10-152026-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 Itsuki Memory

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

  • CogniCore Memory

    Persistent memory for Claude across conversations.

    by CogniCore · 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

  • 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

  • basic-memory

    The bridge between Claude's working memory and Basic Memory's durable knowledge graph — session briefings, pre-compaction checkpoints, and capture reflexes

    by Basic Machines · Plugin bundle

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

  • MCP AutoMem

    Graph-vector memory for AI assistants using FalkorDB and Qdrant

    by verygoodplugins · MCP server

    Listed on: Official MCP Registry, Community GitHub marketplaces · Describes nearly the same job

  • remnic

    Persistent long-term memory for Claude Code — wires SessionStart/UserPromptSubmit/PostToolUse hooks, MCP tools, memory skills, and the memory-review agent into a running Remnic…

    by Joshua Warren · Plugin bundle

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

Its card, with similar plugins by marketplace

What each says it does

Itsuki Memory

In its own words, on Community GitHub marketplaces:

Persistent memory for Claude Code: save durable facts and decisions, recall them in any future session. Receipts for every write; your rules decide what is remembered.

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

Itsuki Memory

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

Settings each asks for

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

What it can do: Itsuki Memory · 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