← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionNeo4j Cypher MCP ServerAn MCP server for running Cypher queries against a Neo4j database.MCP Toolbox for DatabasesGoogle's official database MCP toolbox — define AI-accessible database tools via config
FMRS56 / 100 · C74 / 100 · B
Reliability8 / 2013 / 20
Security and permissions11 / 2013 / 20
Maintenance13 / 2017 / 20
Documentation12 / 2016 / 20
Setup experience12 / 2015 / 20
Best for
  • Developers who already run a Neo4j instance and want to query it in natural language
  • Users of MCP clients such as Claude Desktop, VS Code, Cursor, Windsurf, or Gemini CLI
  • Teams looking to connect a graph database to LLM workflows
  • Users comfortable with lab-stage experimental features and self-supported maintenance
  • Teams that want precise control over which database operations an AI can perform, rather than open arbitrary SQL execution
  • Scenarios needing a unified MCP setup across multiple database engines
Not for
  • Production users who need official product support, SLAs, or backwards compatibility guarantees
  • Neo4j instances where the APOC plugin cannot be installed or enabled (schema inspection will not work)
  • Users who only want the officially supported Neo4j MCP server
  • Users without an accessible Neo4j instance or database credentials
  • Lightweight cases that just want to run a few ad-hoc SQL queries without maintaining a tools.yaml config (a simpler single-database MCP may be a better fit)
Required permissions
  • Read the configured Neo4j database and its schema
  • Execute read and write Cypher queries on the configured Neo4j database
  • Access Neo4j credentials, including NEO4J_URI, NEO4J_USERNAME, and the sensitive NEO4J_PASSWORD
  • Database credentials (username/password/connection string) are supplied via env vars or config
  • A tool's actual permission is whatever SQL statement is defined in tools.yaml — designed for least privilege, but misconfiguration can still over-expose access
Risks and side effects
  • This is an experimental Neo4j Labs project with no SLAs or backwards compatibility guarantees, and it may change between versions
  • Write Cypher queries can be executed by default, potentially modifying or deleting data in the database
  • NEO4J_PASSWORD is sensitive and can leak if misconfigured
  • The server is not officially supported by the Neo4j product team
  • Deploying in HTTP/SSE mode on a network may expose the endpoint to unauthorized access
  • If tools.yaml defines SQL statements that allow unconstrained writes or deletes, the AI could accidentally modify data
  • The prebuilt toolsets (--prebuilt) favor convenience and may expose broader query capability than a specific business actually needs — use a custom tools.yaml in production
Supported clientsClaude Desktop, VS Code, Cursor, Windsurf, Gemini CLIClaude Code, Gemini CLI, Zed, Antigravity
Tools00