Hosting

Local process or Neo4j Aura-hosted per-instance service

Transport

stdio or HTTP/Streamable HTTP

Endpoint

Local process; no hosted endpoint documented

Authentication

Local stdio uses Neo4j database URI, username, and password. Aura-hosted use requires Tool authentication enabled for the organization and authorization for the selected Aura instance. HTTP mode supports documented bearer-token or basic authentication.

Requirements

• A Neo4j instance accessible to the server (Aura, self-managed, Desktop, Docker, or Sandbox, subject to deployment support).
• For local install, Python/pip or the official binary/Homebrew option.
• Appropriate database credentials and privileges.

Setup steps

1. For a local stdio server, install with `pip install neo4j-mcp-server` and configure the client to run `python -m neo4j_mcp_server`.
2. Set NEO4J_URI, NEO4J_USERNAME, NEO4J_PASSWORD, and NEO4J_DATABASE in the client�s secure environment configuration. Set NEO4J_READ_ONLY=true unless write access is deliberately needed.
3. For Aura-hosted MCP, enable Tool authentication in the Aura organization�s Security settings, copy the instance MCP URL from the Aura console, and add it to a remote HTTP MCP client.
4. Reconnect and confirm tool discovery. Use `get-schema` or a harmless `read-cypher` query to verify access; do not test the write tool against production data.

Neo4j documentation names four tools: get-schema, read-cypher, write-cypher, and list-gds-procedures. Availability of the GDS tool depends on server/database configuration; write-cypher is hidden in read-only mode.

• get-schema

  Read graph labels, relationship types, and property keys.

  01
• read-cypher

  Execute a Cypher query with write/schema/admin operations rejected.

  02
• write-cypher

  Execute a write or administrative Cypher statement; disabled when NEO4J_READ_ONLY=true.

  03
• list-gds-procedures

  List Graph Data Science procedures available in the Neo4j instance.

  04

• Write Cypher can modify or remove graph data; Neo4j recommends read-only mode unless writes are required.
• Aura-hosted endpoint is instance-specific and requires Tool authentication to be enabled.
• Tool visibility may depend on server configuration and installed Graph Data Science capabilities.

• official installation and client setup

  Documents Aura instance endpoint retrieval, Tool authentication prerequisite, local pip installation, stdio invocation, and client environment variables.

• official tool reference

  Current Neo4j reference lists four tools and documents that write Cypher is hidden in read-only mode and GDS availability depends on configuration.

• official configuration reference

  Documents NEO4J_URI, database credentials, transport modes, read-only mode, and HTTP configuration.

• official installation reference

  Documents package installation and binary/Homebrew alternatives.

• official repository

  Neo4j product documentation links the official source repository.

• official complete tool reference

  Current docs enumerate four tools, read-only mode, and optional GDS availability.

Documentation checked 2026-10-28T00:00:00Z. Connection has not been runtime tested.