DATABASE EXPLORATION / Neo4j
Neo4j MCP
Explore a Neo4j graph schema and run Cypher through a server with an explicit read-only configuration.
“Neo4j MCP gives AI assistants and LLM-powered tools direct, structured access to your Neo4j graph database.”
01 / THE REASONING
Why this made the selection.
- Schema introspection helps an agent discover graph labels, relationships and properties before writing queries.
- The read-only setting removes the write-Cypher tool, with separate database credentials still controlling access.
02 / THE REVIEW RECORD
What we actually inspected.
Source review has boundaries.
A clear record is more useful than a “safe” badge.
Material inspected
- Pinned README, Go manifest, server/tool registration and configuration.
- Read-Cypher handler, current installation/configuration docs, LICENSE.txt and NOTICE.txt.
Our findings
- The implementation is Go even though the README also offers a Python distribution wrapper.
- Stdio uses environment credentials; HTTP mode receives per-request Basic credentials. These are different authentication setups.
Not established by this review
- Server launch, authenticated tool calls, and release-to-source parity were not tested.
The review applies to the material and revision named here. A newer upstream release can change its behavior.
03 / PUT IT TO WORK
Connect a server deliberately.
DOCUMENTED COMMAND
pip install neo4j-mcp-server Copying does not execute this command. It may retrieve a newer version than the reviewed source.
- Install using the official PyPI command below or choose the documented binary/container route.
- Configure the database URI, database and credentials in your client; set NEO4J_MCP_READ_ONLY=true for exploration.
- Follow the separate HTTP instructions if exposing a listener, including authentication and TLS configuration.
Before you start
- An accessible Neo4j database and credentials.
- Python for the shown distribution route, or the platform-appropriate native executable.
04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
- Neo4j MCP setup and scope ↗Checked
https://raw.githubusercontent.com/neo4j/mcp/905121a3d5295323a9f3971701b7aefae989fcad/README.md
Supports: summary, upstreamDescription, whySelected, bestFor, limitations, install, access, compatibility, transports, review
https://neo4j.com/docs/mcp/current/installation/
Supports: install, compatibility
- Neo4j MCP configuration ↗Checked
https://neo4j.com/docs/mcp/current/configuration/
Supports: limitations, install, access, transports
https://raw.githubusercontent.com/neo4j/mcp/905121a3d5295323a9f3971701b7aefae989fcad/internal/config/config.go
Supports: language, review, limitations, transports
https://raw.githubusercontent.com/neo4j/mcp/905121a3d5295323a9f3971701b7aefae989fcad/internal/server/tools_register.go
Supports: review, access
- Neo4j read query handler ↗Checked
https://raw.githubusercontent.com/neo4j/mcp/905121a3d5295323a9f3971701b7aefae989fcad/internal/tools/cypher/read_cypher_handler.go
Supports: review, limitations
- Neo4j source licence ↗Checked
https://raw.githubusercontent.com/neo4j/mcp/905121a3d5295323a9f3971701b7aefae989fcad/LICENSE.txt
Supports: license
https://raw.githubusercontent.com/neo4j/mcp/905121a3d5295323a9f3971701b7aefae989fcad/NOTICE.txt
Supports: license, limitations