MCP Memory Server with Neo4j backend for AI knowledge graph storage
MCP Memory Server with Neo4j backend for AI knowledge graph storage
Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.
{
"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 |
Store entities, relations and observations in a local knowledge graph with the reference Memory MCP server.
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.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
Chat with your second brain — search, read and write vault notes through the Local REST API.
Enables AI assistants to securely interact with Azure DevOps through a standardized protocol.