Delv
Official (Vendor)Slow· 2mo★ 4.3by Neo4j Labs

Neo4j MCP

Neo4j servers for running Cypher queries, persistent knowledge graph memory, and managing Neo4j Aura instances.

View repo
A
Safety & Trust

Delv Safety Grade: A

Score 83/100 · assessed 2026-04-28

Maintainer85
Permissions75
Supply chain75
Transparency90
Incidents100

Neo4j MCP is an official vendor integration from Neo4j Labs, providing three distinct servers for Cypher queries, persistent knowledge graphs, and Aura instance management. The maintainer credentials are strong given Neo4j's established position in graph databases, though Neo4j Labs is a community-focused arm rather than core product. The permission model is moderately scoped: it requires database credentials and can execute arbitrary Cypher queries, meaning full read-write access to your graph data. The Aura provisioning server adds cloud resource creation capabilities. Supply chain is reasonable via uvx but lacks traditional package registry distribution. Transparency is excellent with open source code and clear documentation. No known security incidents. The main risk is the broad database access granted through credential environment variables, which is inherent to database integration but requires careful credential management.

Lethal Trifecta (prompt-injection exposure)

ONE OF THREE
Private dataYes
Reads secrets, credentials, private files
Untrusted inputNo
Ingests web pages, PRs, issues, emails
External commsNo
Can send data outbound

Graph DB; usually private.

Green flags

  • Official Neo4j Labs project with established vendor backing
  • Open source with active GitHub repository and clear documentation
  • Scoped to Neo4j operations only, no filesystem or shell access
  • Three separate servers allow granular deployment choices
  • No known security incidents or vulnerabilities

Red flags

  • Full database read-write via Cypher execution with provided credentials
  • Aura provisioning server can create cloud resources with associated costs
  • No package registry distribution, relies on uvx direct execution
  • Neo4j Labs is community arm, not core product team

Permissions requested

DB readDB writeOutbound networkAccess secrets
Assessed by Delv Editorial using public metadata. Grades are advisory and update as the ecosystem changes. They do not replace your own review of permissions and code before granting an agent access to sensitive systems.

Install

uvx mcp-neo4j-cypher
Env vars needed: NEO4J_URLNEO4J_USERNAMENEO4J_PASSWORD

Review

Neo4j MCP is the official vendor bridge between Claude and Neo4j graph databases. It gives you three distinct servers: one for running Cypher queries directly, one for persistent knowledge graph memory that survives across sessions, and one for provisioning Neo4j Aura instances on the fly. I've found the Cypher query server the most immediately useful. Point it at your existing Neo4j instance and you can ask Claude to analyse relationships, traverse paths, or debug schema issues without context-switching to the browser console. The knowledge graph memory server is more ambitious. It lets Claude persist entities and relationships across conversations, building a queryable memory layer that actually remembers what you discussed three sessions ago. It's genuinely clever for long-running projects where you want Claude to recall past decisions or domain models. The Aura provisioning server is niche but handy if you're spinning up throwaway graph databases for experiments or demos. You'll need credentials for all three: NEO4J_URL, NEO4J_USERNAME, NEO4J_PASSWORD. The install is straightforward via uvx, and it works cleanly in Claude Desktop, Claude Code, and Cursor. One quirk: the knowledge graph memory server creates its own schema, so don't point it at a production database unless you're comfortable with it writing nodes and relationships. The Cypher server is read-write by default, which means Claude can mutate your data if you're not careful with prompts. I'd reach for this when I'm prototyping graph models, debugging complex traversals, or building agents that need to remember structured context. If you're already using Neo4j for anything beyond toy projects, this MCP is a no-brainer. If you've never touched a graph database, the learning curve for Cypher will slow you down before the MCP pays off.
Verdict

Install this if you already work with Neo4j and want Claude to query or remember graph-structured data. Skip it if you're not committed to graph databases, the setup overhead isn't worth it for casual use. The knowledge graph memory feature alone justifies the install for anyone building stateful agents.

Good at

  • Official Neo4j integration means it tracks database API changes and won't break on version updates.
  • Knowledge graph memory server genuinely persists context across sessions, which is rare and useful for long-running projects.
  • Supports three distinct workflows (query, memory, provisioning) without forcing you to install all three.
  • Cypher query assistance lets you debug graph traversals or schema issues without leaving Claude.
  • Works cleanly across Claude Desktop, Claude Code, and Cursor with the same config.

Watch out

  • Requires Neo4j credentials and a running instance, so you can't try it without setup overhead.
  • The Cypher server has write access by default, which is risky if you point it at production data.
  • Knowledge graph memory server creates its own schema, so you need a dedicated database or careful namespace management.
  • No built-in safeguards against expensive queries, Claude can accidentally run traversals that lock up your database.
  • Documentation assumes familiarity with Cypher, newcomers to graph databases will struggle to get value quickly.

Use cases

  • graph analytics
  • Cypher query assistance
  • knowledge graph memory
  • Aura provisioning

Getting started

1. Run `uvx mcp-neo4j-cypher` to install the Cypher query server (or use `mcp-neo4j-memory` for knowledge graph memory, `mcp-neo4j-aura` for provisioning). 2. Add the server to your Claude Desktop config at `~/Library/Application Support/Claude/claude_desktop_config.json` with environment variables NEO4J_URL, NEO4J_USERNAME, and NEO4J_PASSWORD pointing to your Neo4j instance. 3. Restart Claude Desktop and verify by asking Claude to run a simple Cypher query like `MATCH (n) RETURN count(n)` to confirm connectivity. 4. Watch out: the Cypher server has write access by default, so Claude can mutate your database. Use a development instance or add constraints if you're nervous. 5. For the memory server, expect it to create its own schema for entities and relationships, don't point it at production data without reviewing what it writes.

Works with

Claude DesktopClaude CodeCursor

Similar MCPs