MCP Neo4j Memory Server

@sylweriusz

About MCP Neo4j Memory Server

No overview available yet

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "mcp-neo4j-memory-server": {
      "command": "docker",
      "args": [
        "run",
        "\\"
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is MCP Neo4j Memory Server?

An MCP server that gives AI assistants persistent, intelligent memory using Neo4j’s graph database. It stores memories as interconnected knowledge nodes, supports semantic and exact search, creates typed relationships, organizes data by project, and tracks knowledge evolution over time.

How to use MCP Neo4j Memory Server?

Install via npm install @sylweriusz/mcp-neo4j-memory-server, then add the tool to your Claude Desktop config with environment variables NEO4J_URI, NEO4J_USERNAME, and NEO4J_PASSWORD. You must run a Neo4j database with the GDS plugin (recommended: DozerDB). Four unified MCP tools—memory_store, memory_find, memory_modify, and database_switch—handle all memory operations.

Key features of MCP Neo4j Memory Server

Stores memories as nodes with typed relationships and temporal metadata
Unified search: vectors, exact matches, wildcards, and graph traversal
Creates multiple memories with relations in a single batch request
Isolates projects via separate databases with instant switching
Filters memories by relative or absolute date on any temporal field
Zero-fallback error handling for reliable debugging

Use cases of MCP Neo4j Memory Server

Remember facts, preferences, and context across AI conversations
Find relevant memories using semantic search or exact ID lookups
Create meaningful connections between memories with cross-references
Organize and isolate memories for different projects or topics
Track how knowledge changes over time with versioned observations

FAQ from MCP Neo4j Memory Server

What database does the server require?

It requires Neo4j with the Graph Data Science (GDS) plugin. The recommended setup is DozerDB (docker pull graphstack/dozerdb). GDS is necessary for vector operations.

What are the four MCP tools?

memory_store (create memories with relations), memory_find (search/retrieve), memory_modify (update, delete, manage observations/relations), and database_switch (change project context).

How do I troubleshoot vector search failures?

Check the server logs for [VectorSearch] GDS Plugin detected. If missing, ensure the GDS plugin is installed and Neo4j is running with the correct configuration.

Can I use this server without a graph database?

No. Neo4j (with GDS) is a required persistent storage layer. The server has no fallback or in‑memory mode.

How do I connect to an existing Neo4j instance?

Set the NEO4J_URI, NEO4J_USERNAME, and NEO4J_PASSWORD environment variables in your MCP client config. Test connectivity via curl http://localhost:7474.

Frequently asked questions

What database does the server require?

It requires Neo4j with the Graph Data Science (GDS) plugin. The recommended setup is DozerDB (docker pull graphstack/dozerdb). GDS is necessary for vector operations.

What are the four MCP tools?

`memory_store` (create memories with relations), `memory_find` (search/retrieve), `memory_modify` (update, delete, manage observations/relations), and `database_switch` (change project context).

How do I troubleshoot vector search failures?

Check the server logs for `[VectorSearch] GDS Plugin detected`. If missing, ensure the GDS plugin is installed and Neo4j is running with the correct configuration.

Can I use this server without a graph database?

No. Neo4j (with GDS) is a required persistent storage layer. The server has no fallback or in‑memory mode.

How do I connect to an existing Neo4j instance?

Set the `NEO4J_URI`, `NEO4J_USERNAME`, and `NEO4J_PASSWORD` environment variables in your MCP client config. Test connectivity via `curl http://localhost:7474`.

Comments

Basic information

More Memory & Knowledge MCP servers

The Cloud

Teka

The Cloud is the AI-native workspace that gives every AI — Claude, ChatGPT, Gemini, and other Frontier & Free or Local models — shared memory and real agents. Not cloud computing: thecloud.so is one workspace where your

Tempreon

Person-owned, portable AI memory served over MCP. Your knowledge, preferences, and decisions — captured in one assistant, available in all of them.

Rust Docs MCP Server

Govcraft

🦀 Prevents outdated Rust code suggestions from AI assistants. This MCP server fetches current crate docs, uses embeddings/LLMs, and provides accurate context via a tool call.

286

ctxfile

Local-first MCP server that snapshots your project's working state into one context object. Open-core, privacy-first.

Agimem

Persistent memory for AI agents. Hosted MCP server with capsule-scoped key/value storage, tags, TTL expiration, bulk ops, and RBAC.