membase vs io.github.neo4j-contrib/mcp-neo4j-memory
membase is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑24.
membase is a plugin bundle for AI coding tools published by Membase. 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-27. 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
| Marketplace |  io.github.neo4j-contrib/mcp-neo4j-memory | |
|---|---|---|
| Community marketplace aristoapp/membase | Removed on 2026-10-24 Version: 0.3.0 Forks (GitHub): 1 Stars (GitHub): 8 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 594 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
| Fact | membaseno longer listed · | 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 | 40 594 |
| Forks (GitHub) (differs) | 1 | 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) | 1, secrets among them: 0 | 10, secrets among them: 1 |
| Hooks it runs (differs) | 8 | Not published |
| Parts of the bundle (differs) | 27 | Not a bundle |
| Licence | MIT | MIT |
| Repository (differs) | github.com/aristoapp/membase | github.com/neo4j-contrib/mcp-neo4j |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-15 | 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 membase
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Membase connects Claude Code to Membase Cloud, giving Claude persistent memory and wiki workflows across coding sessions. It can recall relevant prior context before prompts, save…
-
Persistent long-term memory for Claude Desktop / Claude Code, backed by EvolutionDB.
-
SAME - Stateless Agent Memory Engine
Persistent memory for AI coding agents. Local-first SQLite + vector search. 17 MCP tools.
-
Persistent, cross-device memory for your AI coding agents — self-hosted and AGPL, so your knowledge never leaves your own infrastructure. Connect to a Mori server you run; every…
-
memory com.leapmemory/memory
Long-term memory for AI assistants. Isolated per-user storage, recall across conversations.
-
Local-first memory for AI coding agents — Markdown + SQLite FTS5, shared across editors via MCP.
What each says it does
membase
Connect Claude Code to Membase persistent memory over MCP — memory search and store, wiki, and session handoffs.
io.github.neo4j-contrib/mcp-neo4j-memory
MCP Neo4j Knowledge Graph Memory Server
How to run each
membase
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 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
The marketplaces of membase publish no list of tools, so we do not compare tools.
Settings each asks for
Only membase asks for
MEMBASE_CLAUDE_PLUGIN
Only io.github.neo4j-contrib/mcp-neo4j-memory asks for
NEO4J_DATABASENEO4J_MCP_SERVER_ALLOWED_HOSTSNEO4J_MCP_SERVER_ALLOW_ORIGINSNEO4J_MCP_SERVER_HOSTNEO4J_MCP_SERVER_PATHNEO4J_MCP_SERVER_PORTNEO4J_NAMESPACENEO4J_PASSWORD (secret)NEO4J_TRANSPORTNEO4J_URINEO4J_URLNEO4J_USERNAME
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: membase · 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.