Simple Memory MCP
eragonht1LABSCO SUMMARY
Same memory contract as the reference server, with a graph database behind it.
This is the official Knowledge Graph Memory Server's interface pointed at Neo4j, which buys two things a file-backed store cannot: multi-hop traversal in Cypher, and the ability to open the graph in Neo4j Browser and look at what the assistant has actually been remembering. The cost is that you now run a database — the bundled docker-compose is the shortest way to that.
What it is
A memory server that stores an assistant's knowledge graph in Neo4j instead of a JSON file. Entities become labelled nodes, observations hang off them as HAS_OBSERVATION relationships, and relations between entities are typed edges.
What you get
- create_entities stores a name, an entityType and a list of observations — the example in the README creates a person with typed observations attached
- Full create, read, update and delete over entities, relations and observations
- Search combines Neo4j's full-text index with Fuse.js fuzzy matching, so exact and partial hits come back ranked by relevance
- Because the store is Neo4j, the same graph is traversable with Cypher and viewable in Neo4j's own visualisation tools
- A docker-compose file brings up Neo4j and the server together
Requirements
Node.js 22.0.0 or newer and a Neo4j database, local or remote. Install the npm package @jovanhsu/mcp-neo4j-memory-server. Connection details come from NEO4J_URI (default bolt://localhost:7687), NEO4J_USER, NEO4J_PASSWORD and NEO4J_DATABASE.
Setup effort
Build from source — git clone https://github.com/JovanHsu/mcp-neo4j-memory-server.git
USE CASES
01
Keeping what an assistant learns across conversations
Entities and observations persist in Neo4j rather than a file that lives with one client.
02
Asking questions that need more than one hop
Relations are first-class edges, so traversal is a database operation instead of a scan.
03
Seeing what is actually in the memory
Neo4j's own visualisation opens the same graph for inspection and cleanup.
BEFORE YOU INSTALL
What to know first
Requires
- Node.js >= 22.0.0
- NEO4J_PASSWORD in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/JovanHsu/mcp-neo4j-memory-server.git
cd mcp-neo4j-memory-server
pnpm install
pnpm buildMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"graph-memory": {
"command": "node",
"args": [
"<YOUR_MCP_NEO4J_MEMORY_SERVER_CLONE>/dist/index.mjs"
],
"env": {
"NEO4J_URI": "bolt://localhost:7687",
"NEO4J_USER": "neo4j",
"NEO4J_PASSWORD": "<YOUR_NEO4J_PASSWORD>",
"NEO4J_DATABASE": "neo4j"
}
}
}
}
