Back to MCP Directory
Neo4j
Model Context Protocol moderate risk

Neo4j

A suite of MCP servers enabling natural language interaction with Neo4j, including query generation, knowledge graph management, Aura cloud service control, and data modeling.

Connections & Capabilities

Connects To

GitHubAWSAzure

Capabilities

readwriteexecadmin

Exposed MCP Tools (4)

high
mcp-neo4j-cypher

Translates natural language into Cypher queries and executes them against a Neo4j database.

Executes arbitrary Cypher queries, potentially modifying or deleting data.

moderate
mcp-neo4j-memory

Stores and retrieves entities and relationships in a Neo4j knowledge graph.

Allows writing and retrieval of knowledge graph data, potentially exposing sensitive information.

critical
mcp-neo4j-cloud-aura-api

Manages Neo4j Aura instances, including creation, deletion, and scaling.

Provides administrative access to Neo4j Aura cloud resources, enabling potentially destructive actions.

safe
mcp-neo4j-data-modeling

Creates, validates, and visualizes Neo4j graph data models.

Primarily a design and visualization tool with minimal risk of data modification.

Safety Assessment

The overall safety depends heavily on the specific server being used and its configuration. Read-only servers are generally safe, while those managing Aura instances or executing Cypher queries require careful access control and monitoring. Production deployments should prioritize secure configuration and consider the lack of formal support.

  • Supports multiple transport modes, including STDIO for local tools.
  • Cloud deployment options allow for scalable and potentially isolated environments.
  • Individual servers have varying levels of risk based on their function (read vs. write).
  • Clear documentation encourages responsible use and configuration.
  • Servers actively developed, backwards compatibility not guaranteed.
  • Some servers allow write operations and instance management, posing potential risks.
  • Secrets management relies on environment variables, requiring secure handling.
  • Lack of SLAs or guarantees increases risk in production environments.
  • Potential for exposure if HTTP transport is misconfigured.