MCP Memory Server with Neo4j backend for AI knowledge graph storage
Connect MCP Neo4j Memory Server to Claude, Cursor or any other MCP client and it stops being a tab you switch to. MCP Memory Server with Neo4j backend for AI knowledge graph storage. The mcp neo4j memory server mcp server is what makes that connection.
Installation goes through your MCP client rather than a global install: point it at @jovanhsu/mcp-neo4j-memory-server on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Configuration is passed through the environment: NEO4J_URI, NEO4J_USER, NEO4J_PASSWORD, NEO4J_DATABASE. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
This sits in the knowledge and memory group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. It is maintained by JovanHsu; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against MCP Neo4j Memory Server's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
{
"mcpServers": {
"graph-memory": {
"command": "npx",
"args": [
"-y",
"@izumisy/mcp-neo4j-memory-server"
],
"env": {
"NEO4J_URI": "neo4j://localhost:7687",
"NEO4J_USER": "neo4j",
"NEO4J_PASSWORD": "password",
"NEO4J_DATABASE": "memory"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| NEO4J_URI | Configuration value read at startup. | Optional |
| NEO4J_USER | Configuration value read at startup. | Optional |
| NEO4J_PASSWORD | Configuration value read at startup. | Optional |
| NEO4J_DATABASE | Configuration value read at startup. | Optional |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.