DuckDB Graph Memory MCP — File-Backed Memory DB

Practical Notes

• Quant: memory is stored in a DuckDB file, so you can backup/rotate it like any other database artifact.
• Quant: treat memory writes as an explicit policy—capture only verified facts to keep retrieval precision high.

Rollout pattern

• Start with a dedicated memory file per project to avoid cross-project contamination.
• Define a memory write policy: only write decisions, constraints, and stable preferences.
• Schedule periodic cleanup or consolidation so the knowledge graph stays useful over time.

Watchouts

A local memory file can still leak secrets if your agent writes them. Treat the file as sensitive and keep it out of synced folders or shared drives.

FAQ

Q: Is this the official MCP memory server? A: It is a fork of the official knowledge graph memory server with DuckDB storage changes.

Q: Where is data stored? A: In a DuckDB database file at MEMORY_FILE_PATH.

Q: How do I keep it clean? A: Write only verified facts and run periodic consolidation/cleanup so retrieval stays high-signal.