MemoryLayer vs io.github.neo4j-contrib/mcp-neo4j-memory
MemoryLayer is an MCP server published by memorylayer.in. Marketplaces we read that list it: 1 (Official MCP Registry). 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-30. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  MemoryLayer |  io.github.neo4j-contrib/mcp-neo4j-memory |
|---|---|---|
| Official MCP Registry | Listed Version: 1.7.1 Downloads/month (npm): 405 Downloads/week (npm): 246 Not marked · First seen |
Listed Version: 1.0.0 Downloads/month (PyPI): 23 826 Downloads/week (PyPI): 7 866 Forks (GitHub): 263 Stars (GitHub): 989 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:0f04105a1006 Forks (GitHub): 263 Pulls (Docker Hub): 41 670 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 | MemoryLayer | io.github.neo4j-contrib/mcp-neo4j-memory |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 989 |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 41 670 |
| Forks (GitHub) (differs) | No figure on GitHub | 263 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@raajvamsy/memorylayer) | On your machine (mcp-neo4j-memory) |
| Transport | stdio | stdio |
| Tools it declares (differs) | Not published | 9 |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 10, secrets among them: 1 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | Not stated | github.com/neo4j-contrib/mcp-neo4j |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
MemoryLayer
Local-first persistent memory for AI agents, with reasoning and formal verification.
io.github.neo4j-contrib/mcp-neo4j-memory
MCP Neo4j Knowledge Graph Memory Server
How to run each
MemoryLayer As a local MCP server: npm package
claude mcp add --env "MEMORY_API_KEY=<YOUR_MEMORY_API_KEY>" --transport stdio memorylayer -- npx -y --stdio "<YOUR_STDIO>" @raajvamsy/memorylayerRequires: MEMORY_API_KEY (secret), --stdio
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 MemoryLayer publish no list of tools, so we do not compare tools.
Settings each asks for
Only MemoryLayer asks for
MEMORY_API_KEY (secret)
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: MemoryLayer · What it can do: io.github.neo4j-contrib/mcp-neo4j-memory · Compare two other plugins
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.