mammoth vs io.github.neo4j-contrib/mcp-neo4j-memory
mammoth is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑18.
mammoth is a plugin bundle for AI coding tools published by AllSource. 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 | ||
|---|---|---|
| Community marketplace all-source-os/all-source | Removed on 2026-10-18 Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 3 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 | mammothno longer listed · | io.github.neo4j-contrib/mcp-neo4j-memory |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 3 | 989 |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 40 594 |
| 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 |
| Parts of the bundle (differs) | 8 | Not a bundle |
| Licence | MIT | MIT |
| Repository (differs) | github.com/all-source-os/all-source | github.com/neo4j-contrib/mcp-neo4j |
| Changes in the last 7 days | 0 | 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 mammoth
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
engram io.github.tstockham96/engram
Intelligent agent memory with automatic extraction, consolidation, and bi-temporal recall.
-
One memory, every AI. A shared, user-owned markdown memory your AI clients read and write over MCP.
-
Persistent semantic memory for AI agents using local ChromaDB vector search. No cloud required.
-
Persistent memory for AI agents. Infinite context with sub-millisecond recall.
-
Memoize — persistent agent memory
Persistent cross-session memory shared by Codex, Claude Code, ChatGPT, and other AI agents.
-
memory com.leapmemory/memory
Long-term memory for AI assistants. Isolated per-user storage, recall across conversations.
What each says it does
mammoth
Durable agent memory. Your coding agent remembers decisions, task history, and code context across sessions and recalls them automatically. caveman make few token, mammoth never forget token.
io.github.neo4j-contrib/mcp-neo4j-memory
MCP Neo4j Knowledge Graph Memory Server
How to run each
mammoth
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-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 mammoth publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of mammoth publish no settings it asks for, so we do not compare settings.
What it can do: mammoth · 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.