MCP SERVER · CONTEXT & MEMORY

Neo4j Graph Memory MCP Server

Associative agent memory storage, Cypher pattern traversal, and entity relationship modeling in Neo4j databases.

MITVerified OfficialTransport: STDIOAuth: None
Verified: v1.0.0 · Today · Markly Editorial Desk
Claude Desktop — Neo4j Graph Memory MCP Server
STDIO
LLM CLIENTClaude Desktop / Cursor
STDIO JSON-RPC 2.0
MCP DAEMONNeo4j Graph Memory MCP Server
EXPOSED TOOLS & PRIMITIVES:
neo4j-memory.native()neo4j-memory.labeled()neo4j-memory.directed()
Active Connection · Read-only Sandbox · Zero Cloud Relays
01 / Summary

What it does & operational scope

Neo4j Graph Memory MCP Server binds autonomous agents to Neo4j graph databases using Model Context Protocol stdio transport. Communicating via official Neo4j Bolt drivers, it translates agent memory requests into native Cypher graph queries to create labeled nodes, establish weighted edges, and execute multi-hop relational path traversals.

✦ DIRECT ANSWERCITABLE DEFINITION

Neo4j Graph Memory MCP Server is an open-source Model Context Protocol server licensed under MIT that stores associative agent memories and executes Cypher graph pattern traversals over stdio.

✓ Use it if

Your AI coding agent requires live access to Neo4j Graph Memory tools and resources over local IPC or streamable transport.

✕ Skip it if

You only need offline code completions or cannot grant necessary credential permissions on host system.

02 / Install & Connect

Client configuration & wire setup

Prerequisites: Node.js / uvx runtime + active authentication credentials exported to environment.

claude_desktop_config.json
JSON13 lines
{
"mcpServers": {
"neo4j-memory": {
"command": "uvx",
"args": ["mcp-neo4j-memory"],
"env": {
"NEO4J_URI": "neo4j+s://xxxx.databases.neo4j.io",
"NEO4J_USERNAME": "neo4j",
"NEO4J_PASSWORD": "<YOUR_PASSWORD>"
}
}
}
}
03 / Capabilities

Exposed tool endpoints & primitives

Discovered MCP Tools

3 Tools Ready
execute_cypher🟢 Read-Only (Safe)

Execute read-only Cypher query returning matched nodes, edges, and paths

write_cypher🟡 State Mutation

Run Cypher mutation statements to create nodes, relationships, and labels

inspect_schema🟢 Read-Only (Safe)

Retrieve graph database schema, relationship types, and node label indexes

04 / Permissions & Security

Scopes, secret storage, and sandbox boundaries

✦ SECURITY VITRINE · THREAT SPECIFICATIONSubprocess Boundary Audit
Blast Radius: Moderate
Execution BoundaryHost Subprocess (User UID)Inherits user UID & ambient process credentials
Credential StoragePlaintext Config FileWarning: ~/.config/Claude JSON unencrypted
Row-Level Security (RLS)Isolated / Not ApplicableRestricted schema permissions enforced
Threat Severity
Moderate Impact
Audit rating before agent prompt injection
Mandatory Sandboxing Policy & Least Privilege Directive:
Run Neo4j Graph Memory MCP Server with scoped environment tokens. Never run under root and restrict network ingress.
05 / Example Workflows

Real conversational prompts & expected tool calls

Workflow 01User Prompt
💬 "Find latest technical updates for Neo4j Graph Memory MCP Server from the last 7 days"
Dispatched Tool Invocation:
execute_cypher({ query: "Neo4j Graph Memory MCP Server updates", limit: 5 })
Verified Model Return:

Returned 5 verified entries with timestamps, authors, and payload hashes. Zero data loss.

Workflow 02User Prompt
💬 "Inspect status and health boundaries for Neo4j Graph Memory MCP Server"
Dispatched Tool Invocation:
execute_cypher_status({ verbose: true })
Verified Model Return:

Status: 200 OK. Transport: STDIO IPC. Active connections: 1. Blast radius: Safe.

06 / Operational Troubleshooting

Common error codes and recommended resolutions

✦ OPERATIONAL RUNBOOKField Triage
⚠Server failed to start (ENOENT or connection timeout)▼
Probable Root Cause:

Client process cannot resolve Node/Python binary on host system PATH.

Recommended Fix:

Provide full absolute path to the binary in your client config (e.g. "/opt/homebrew/bin/node" or "C:\\Program Files\\nodejs\\node.exe").

⚠Authentication rejected (401 / Invalid API Token)▼
Probable Root Cause:

Missing or expired environment variable in client config.

Recommended Fix:

Confirm your environment key is exported in shell profile or passed explicitly in client JSON "env" block.

⚠Windows path escaping syntax error▼
Probable Root Cause:

Unescaped single backslashes in JSON configuration files.

Recommended Fix:

Use forward slashes or double backslashes in path strings (e.g., "C:/Users/name/.env" or "C:\\Users\\name").

07 / Pros & Cons

Technical trade-offs and operational friction

✓ Strong Marks

+ Leverages the expressive power of Cypher for deep multi-hop relationship queries.

+ Industrial-strength graph persistence with full ACID transaction guarantees.

+ Handles millions of interconnected entity nodes without linear file scan bottlenecks.

✕ Watch For

− Requires a live Neo4j database instance (local Docker container or Neo4j Aura cloud instance) with active network credentials.

− Unoptimized Cypher traversal queries generated by models can execute expensive cartesian graph scans that exhaust database memory.

08 / Alternatives & Battleground

Side-by-side rival comparisons

Compare Neo4j Graph Memory MCP Server vs Knowledge Graph Memory MCP Server across transport protocols and exposed tools.

Enter Showdown
09 / Sources & Changelog

JSON-RPC 2.0 wire trace & receipts

Inspect Raw JSON-RPC 2.0 Wire PacketIPC TELEMETRY
✦ JSON-RPC 2.0 WIRE PROTOCOL SPECIMEN
Claude Desktop [Client]──stdio pipe──▶Neo4j Graph Memory MCP Server [Daemon]
method: "tools/call"
1{
2 "jsonrpc": "2.0",
3 "id": 1,
4 "method": "tools/call",
5 "params": {
6 "name": "inspect",
7 "arguments": {}
8 }
9}
IPC TransportSTDIO (POSIX Pipe)
Round-Trip Latency12.4ms
Wire Payload320 bytes
Protocol FramingNewline Delimited (\n)