M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

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

DimensionNeo4j Knowledge Graph Memory ServerPersonal knowledge graph memory stored in Neo4jMCP Toolbox for DatabasesGoogle's official database MCP toolbox — define AI-accessible database tools via config
FMRS59 / 100 · C74 / 100 · B
Reliability10 / 2013 / 20
Security and permissions12 / 2013 / 20
Maintenance14 / 2017 / 20
Documentation11 / 2016 / 20
Setup experience12 / 2015 / 20
Best for
  • Users who already have a Neo4j instance (local or remote) and want an AI assistant to reuse memory
  • Developers who need knowledge and relationships preserved across sessions and clients
  • Users comfortable with experimental Neo4j Labs software and willing to absorb version-change risk
  • 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
  • Users looking for official Neo4j product support, SLAs, or backwards-compatibility guarantees
  • Users who have no Neo4j instance and do not want to deploy or maintain a database
  • Users who need Cypher query execution, Aura cloud instance management, or graph data modeling from this server (those are other servers in the same repository)
  • 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 and write nodes and relationships in the configured Neo4j database (for storing and retrieving memories)
  • Read NEO4J_URI, NEO4J_USERNAME, NEO4J_PASSWORD, NEO4J_DATABASE, and NEO4J_NAMESPACE environment variables at runtime
  • 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
  • Neo4j credentials live in the client configuration as environment variables; NEO4J_PASSWORD is secret and must be protected
  • Memories stored in the knowledge graph may be read during sessions, so sensitive or private content should be assessed beforehand
  • As a Neo4j Labs server it is experimental and may change incompatibly or drop features
  • Database read/write scope is determined by the supplied Neo4j account; overly broad permissions mean mistaken writes can affect other data in that database
  • 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