← Back to directory
N

Neo4j Knowledge Graph Memory Server

Community
Personal knowledge graph memory stored in Neo4j
GitHub source repository ↗
★ 980 Stars Category · Database Very popular
59FMRS · C

A narrowly scoped MCP server: it persists personal knowledge graph memory into Neo4j and reuses it across sessions and clients. It is a Neo4j Labs experimental project without official product support, suited to users who already run Neo4j and accept version-change risk. It requires database credentials, and the capabilities of sibling servers in the same repository (Cypher, Aura management, data modeling) should not be attributed to it.

Reliability
10/20
Security and permissions
12/20
Maintenance
14/20
Documentation
11/20
Setup experience
12/20
Read the FMRS scoring method →

The Neo4j Knowledge Graph Memory Server is part of the Neo4j Labs collection of MCP servers, developed and maintained by the Neo4j Field GenAI team and explicitly not supported by the Neo4j product team (no SLAs, no backwards-compatibility guarantees, experimental features are common). It stores and retrieves entities and relationships from your personal knowledge graph in a local or remote Neo4j instance, so that information can be accessed across different sessions, conversations, and clients. It runs as the PyPI package mcp-neo4j-memory (version 0.4.5) over stdio and requires Neo4j connection settings such as NEO4J_URI, NEO4J_USERNAME, and NEO4J_PASSWORD.

Setup

  1. Have a reachable Neo4j instance (local or remote) and its connection URI, username, and password ready.
  2. Install the server package from PyPI (identifier: mcp-neo4j-memory), or follow the instructions in the servers/mcp-neo4j-memory directory of the repository.
  3. Configure it as a stdio server in your MCP client and set the environment variables: NEO4J_URI, NEO4J_USERNAME, NEO4J_PASSWORD (required), plus NEO4J_DATABASE and NEO4J_NAMESPACE (optional).
  4. Restart the MCP client and confirm the server can connect to Neo4j and start a session.

Fit and risk

Best for

  • Users who already have a Neo4j instance (local or remote) and want an AI assistant to reuse memory
  • Developers who need knowledge and relationships preserved across sessions and clients
  • Users comfortable with experimental Neo4j Labs software and willing to absorb version-change risk

Not for

  • Users looking for official Neo4j product support, SLAs, or backwards-compatibility guarantees
  • Users who have no Neo4j instance and do not want to deploy or maintain a database
  • Users who need Cypher query execution, Aura cloud instance management, or graph data modeling from this server (those are other servers in the same repository)

Required permissions

  • Read and write nodes and relationships in the configured Neo4j database (for storing and retrieving memories)
  • Read NEO4J_URI, NEO4J_USERNAME, NEO4J_PASSWORD, NEO4J_DATABASE, and NEO4J_NAMESPACE environment variables at runtime

Risks and side effects

  • Neo4j credentials live in the client configuration as environment variables; NEO4J_PASSWORD is secret and must be protected
  • Memories stored in the knowledge graph may be read during sessions, so sensitive or private content should be assessed beforehand
  • As a Neo4j Labs server it is experimental and may change incompatibly or drop features
  • Database read/write scope is determined by the supplied Neo4j account; overly broad permissions mean mistaken writes can affect other data in that database

Troubleshooting

  1. Verify NEO4J_URI, NEO4J_USERNAME, and NEO4J_PASSWORD are set correctly and no required value is missing
  2. Check that the Neo4j instance is reachable and that network/port access is allowed
  3. If using a non-default database, confirm NEO4J_DATABASE names the correct database
  4. Check MCP client logs for stdio startup or connection errors
  5. Confirm the installed package version matches expectations and reinstall or upgrade if needed

Use cases

Let an AI assistant remember persistent facts about you and your projects
Share one personal knowledge graph across sessions and different clients
Query and update entity and relationship memories stored in Neo4j
Build a long-accumulating memory layer for personal or team conversations

Supported clients

Claude DesktopFull support
VS CodePartial support
CursorPartial support
WindsurfPartial support
Gemini CLIPartial support