Provides persistent graph-based memory storage using Neo4j database, enabling AI assistants to store, search, and retrieve interconnected knowledge with semantic vector search, graph traversal, and relationship management across isolated project contexts.
Neo4j Memory Server
A Model Context Protocol (MCP) server that provides AI assistants with persistent, intelligent memory capabilities using Neo4j's graph database with unified architecture
What it does
This server enables AI assistants to:
Remember - Store memories as interconnected knowledge nodes with observations and metadata
Search - Find relevant memories using semantic vector search, exact matching, and graph traversal
Connect - Create meaningful relationships between memories with batch operations and cross-references
Organize - Separate memories by project using different databases
Evolve - Track how knowledge develops over time with temporal metadata and relationship networks
Features
Core Capabilities
🧠 Graph Memory - Memories as nodes, relationships as edges, observations as content
🔍 Unified Search - Semantic vectors, exact matching, wildcards, and graph traversal in one tool
🔗 Smart Relations - Typed connections with strength, source tracking, and temporal metadata
📊 Multi-Database - Isolated project contexts with instant switching
Advanced Operations
⚡ Batch Operations - Create multiple memories with relationships in single request using localId
🎯 Context Control - Response detail levels: minimal (lists), full (complete data), relations-only
📅 Time Queries - Filter by relative ("7d", "30d") or absolute dates on any temporal field
🌐 Graph Traversal - Navigate networks in any direction with depth control
Architecture
🚀 MCP Native - Seamless integration with Claude Desktop and MCP clients
💾 Persistent Storage - Neo4j graph database with GDS plugin for vector operations
⚠️ Zero-Fallback - Explicit errors for reliable debugging, no silent failures
Technical Highlights
Built on Neo4j for scalable graph operations
Vector embeddings using sentence transformers (384 dimensions)
Clean architecture with domain-driven design
Supports GDS plugin for advanced vector operations (necessary)
Unified Architecture - 4 comprehensive tools for complete memory operations
Quick Start
Add to Claude Desktop config:
Neo4j Setup
Working setup: DozerDB with GDS Plugin
For the database, use DozerDB with the Graph Data Science plug-in, GDS is not only recommended but necessary:
For current installation instructions, see: https://dozerdb.org/
Example setup:
Unified Tools
The server provides 4 unified MCP tools that integrate automatically with Claude:
memory_store- Create memories with observations and immediate relations in ONE operationmemory_find- Unified search/retrieval with semantic search, direct ID lookup, date filtering, and graph traversalmemory_modify- Comprehensive modification operations (update, delete, observations, relations)database_switch- Switch database context for isolated environments
Memory Structure
System Prompt
The simplest use of the memory tool, the following usually is more than enough.
Troubleshooting
Vector Search Issues:
Check logs for
[VectorSearch] GDS Plugin detectedGDS Plugin requires DozerDB setup (see Neo4j Setup section)
Connection Issues:
Verify Neo4j is running:
docker psTest connection:
curl http://localhost:7474Check credentials in environment variables
License
MIT
This server cannot be installed