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.
What's Changed
- fix(ci): bump gh-action-pypi-publish for metadata 2.5 by @prasmussen15 in #1821
- Bump graphiti-core to 0.30.1 by @prasmussen15 in #1822
- Fix Neo4j database routing and honor NEO4J_DATABASE in MCP server by @mehulp93 in #1812
Full Changelog: v0.30.0...mcp-v1.10
