← Explore all mcp servers

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

  • README.md, go.mod, cmd/neo4j-mcp/main.go, internal/config/config.go and internal/server/tools_register.go at 0f851d06092ab6e2914af55662d11a226efe8924.
  • internal/tools/cypher/read_cypher_handler.go, LICENSE.txt and NOTICE.txt at the same commit; the installation and configuration pages on neo4j.com, read 2026-10-13.

Our findings

  • The implementation is Go even though the README also offers a Python distribution wrapper.
  • Stdio uses environment credentials; HTTP mode takes per-request credentials. The configuration page names Bearer token or Basic authentication; config.go rejects a username and password set for HTTP mode.
  • The README lists four tools: get-schema, read-cypher, write-cypher (disabled when NEO4J_MCP_READ_ONLY=true) and list-gds-procedures.
  • config.go reads both NEO4J_MCP_* and NEO4J_* names for each setting; the README uses the first, the configuration page the second. ReadOnly defaults to false and Telemetry to true.
  • configExample is the README's VS Code mcp.json block at 0f851d06; its NEO4J_MCP_PASSWORD value is the README's placeholder.
  • The README and the files cited here are byte-identical between 905121a3 and 0f851d06.

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.

Upstream setup instructions ↗

DOCUMENTED COMMAND

pip install neo4j-mcp-server

Copying does not execute this command. It may retrieve a newer version than the reviewed source.

  1. Install using the PyPI command above, or the documented Homebrew (brew install neo4j-mcp) or release-binary route.
  2. Configure the database URI, database and credentials in your client; set NEO4J_MCP_READ_ONLY=true for exploration.
  3. Follow the separate HTTP instructions if exposing a listener, including authentication and TLS configuration.
  4. The command was copied from the README and not run.

Before you start

  • An accessible Neo4j database and credentials.
  • Python for the shown distribution route, or the platform-appropriate native executable.

Documented configuration example

Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.

{
  "servers": {
    "neo4j": {
      "type": "stdio",
      "command": "python",
      "args": [
        "-m",
        "neo4j_mcp_server"
      ],
      "env": {
        "NEO4J_MCP_URI": "bolt://localhost:7687",
        "NEO4J_MCP_USERNAME": "neo4j",
        "NEO4J_MCP_PASSWORD": "password",
        "NEO4J_MCP_DATABASE": "neo4j",
        "NEO4J_MCP_READ_ONLY": "true",
        "NEO4J_MCP_TELEMETRY": "false",
        "NEO4J_MCP_LOG_LEVEL": "info",
        "NEO4J_MCP_LOG_FORMAT": "text",
        "NEO4J_MCP_SCHEMA_SAMPLE_SIZE": "100"
      }
    }
  }
}

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. https://raw.githubusercontent.com/neo4j/mcp/0f851d06092ab6e2914af55662d11a226efe8924/README.md

    Supports: summary, upstreamDescription, whySelected, bestFor, limitations, install, access, compatibility, transports, review, configExample

  2. https://neo4j.com/docs/mcp/current/installation/

    Supports: install, compatibility

  3. Neo4j MCP configuration ↗Checked

    https://neo4j.com/docs/mcp/current/configuration/

    Supports: limitations, install, access, transports

  4. https://raw.githubusercontent.com/neo4j/mcp/0f851d06092ab6e2914af55662d11a226efe8924/internal/config/config.go

    Supports: language, review, limitations, transports

  5. https://raw.githubusercontent.com/neo4j/mcp/0f851d06092ab6e2914af55662d11a226efe8924/internal/server/tools_register.go

    Supports: review, access

  6. https://raw.githubusercontent.com/neo4j/mcp/0f851d06092ab6e2914af55662d11a226efe8924/internal/tools/cypher/read_cypher_handler.go

    Supports: review, limitations

  7. Neo4j source licence ↗Checked

    https://raw.githubusercontent.com/neo4j/mcp/0f851d06092ab6e2914af55662d11a226efe8924/LICENSE.txt

    Supports: license

  8. https://raw.githubusercontent.com/neo4j/mcp/0f851d06092ab6e2914af55662d11a226efe8924/NOTICE.txt

    Supports: license, limitations

Evidence & Ask