Graphiti vs Memory (MCP reference server)

Graphiti

Apache-2.0, with FalkorDB, Neo4j or Amazon Neptune as the store. Every add runs LLM extraction, so ingestion costs tokens and time.

Memory (MCP reference server)

Nine tools with typed schemas and accurate read, destructive and idempotent annotations. No pagination or limits. read_graph returns everything and search_nodes every match.

Graphiti

1. Set OPENAI_API_KEY (or another provider's key) and MODEL_NAME before starting the MCP server
2. Use search_memory_facts for facts and search_nodes for entities instead of reading whole episodes
3. Never call clear_graph to fix one fact. Use delete_episode or delete_entity_edge
4. Pass group_ids on every search and add so one user's graph doesn't leak into another's
5. Call get_status to check the database connection before a long ingest

Memory (MCP reference server)

1. Set MEMORY_FILE_PATH to an absolute path. The default sits inside the npx cache
2. Use search_nodes or open_nodes instead of read_graph once the graph has more than a few hundred entities
3. Make memory writes one at a time. Parallel calls in one turn can overwrite each other in 2026.8.31
4. Create both entities before create_relations. A missing endpoint fails the whole batch
5. Keep observations short and factual. They come back verbatim in every later read