deprecationhigh
Neo4j MCP server 行为变化:NEO4J_DATABASE 设置现在对所有操作都生效
具有自定义数据库设置(非默认的 'neo4j')的自托管 Neo4j Enterprise 部署可能会在数据库间分割数据。用户必须明确验证 NEO4J_DATABASE 配置,并检查升级前可能已写入主数据库的数据。
证据
+WHO IS AFFECTED: Self-hosted Neo4j Enterprise deployments where NEO4J_DATABASE (or database: in config.yaml) was set to something other than neo4j. Standard setups using the default neo4j database need no action.
Before: The MCP server ignored your database setting; add_memory / search could hit the server's home database while other operations used the configured one — data could be split across two databases.
After: All operations consistently use the configured database. Set NEO4J_DATABASE explicitly in .env or config.yaml:
NEO4J_DATABASE=your_database_name
Migration: If you previously ran with a custom database name configured but data appeared missing, check your Neo4j home database — earlier writes may have landed there and may need to be migrated.