Graphiti vs Mem0 Platform + MCP

Graphiti

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

Mem0 Platform + MCP

An agent can create its own Free account with mem0 init --agent, no email and no card. Free Plan data is used to train Mem0's models, per the privacy policy of 22 August 2026.

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

Mem0 Platform + MCP

1. Send the REST key as Authorization: Token <key>, and the MCP key as Bearer
2. Don't search for a memory straight after adding it. Adds are queued, so poll get_event_status with the returned event ID
3. Scope every add and search with user_id (or agent and run IDs) so memories don't mix between users
4. Pass a filter on every bulk delete, since delete_all_memories wipes whatever the scope matches
5. On Hobby and Starter, count retrievals rather than adds. The retrieval quota is a tenth the size