Neo4j Memory MCP Server
Neo4j Memory MCP server (part of the neo4j-contrib MCP suite) providing AI agents with graph-based persistent memory — storing entities and their relationships as a knowledge graph in Neo4j, enabling semantic memory retrieval, managing entity attributes and connections, and integrating Neo4j's graph database as a long-term memory backend for AI agent knowledge graphs.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Bolt TLS. User/pass. SOC2/GDPR. Neo4j-contrib. Store creds in env var. Sensitive memory data.
⚡ Reliability
Best When
An agent needs structured relationship-aware memory — tracking how entities connect to each other rather than just storing isolated facts, using Neo4j's graph model for rich knowledge representation.
Avoid When
You need simple persistent memory without relationship tracking — use lighter alternatives. Or if you prefer vector-based semantic search.
Use Cases
- • Storing entities and relationships as persistent knowledge graph memory
- • Building and querying agent knowledge graphs from personal assistant agents
- • Maintaining long-term user preference graphs from personalization agents
- • Tracking entity relationships over time from analysis agents
- • Implementing semantic memory with graph traversal for reasoning agents
- • Building organizational knowledge graphs from enterprise knowledge agents
Not For
- • Teams without Neo4j instance (AuraDB free tier available)
- • Simple key-value memory (use lighter alternatives like mcp-memory-keeper)
- • Vector similarity search (use ChromaDB or LanceDB for embedding-based memory)
Interface
Authentication
Neo4j username/password required. Uses Neo4j Bolt protocol. AuraDB free tier supported. Same auth as standard mcp-neo4j-server.
Pricing
AuraDB Free is sufficient for agent memory use cases. Community/Enterprise self-hosted is free. MCP from neo4j-contrib.
Agent Metadata
Known Gotchas
- ⚠ Entity naming and relationship types must be consistent — agents should establish naming conventions
- ⚠ Graph can grow unbounded — implement cleanup or archival strategies for long-running agents
- ⚠ Cypher queries required for complex memory retrieval — simpler than raw Neo4j MCP
- ⚠ Part of neo4j-contrib MCP suite — same high quality as mcp-neo4j-server
- ⚠ Memory retrieval is relationship-traversal based — different paradigm from vector similarity
- ⚠ AuraDB Free tier node limit (50K) is sufficient for most agent memory use cases
Alternatives
Full Evaluation Report
Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for Neo4j Memory MCP Server.
Scores are editorial opinions as of 2026-03-06.