{"id":"pinkpixel-dev-mem0-mcp","name":"mem0-mcp","af_score":57.0,"security_score":53.5,"reliability_score":32.5,"what_it_does":"Provides an MCP server exposing tools (add_memory, search_memory, delete_memory) backed by Mem0 for long-term memory storage and retrieval across LLM sessions. Supports three modes: Mem0 cloud, Supabase (self-host), and local/in-memory (dev).","best_when":"You want drop-in MCP tool access for semantic long-term memory and can configure the appropriate storage mode (cloud for simplest; Supabase for self-hosting; local only for development).","avoid_when":"You need a REST/HTTP API surface or fine-grained authorization per caller beyond a single MCP server process configured for a given user/app scope.","last_evaluated":"2026-03-30T13:48:23.403575+00:00","has_mcp":true,"has_api":false,"auth_methods":["Environment-variable API key for Mem0 Cloud (MEM0_API_KEY)","Environment-variable credentials for Supabase (SUPABASE_URL, SUPABASE_KEY)","Environment-variable API key for embeddings (OPENAI_API_KEY)"],"has_free_tier":false,"known_gotchas":["MCP server requires clean stdout for protocol communication—logging to stdout may break the MCP protocol.","Tool scoping relies on userId/appId/sessionId parameters and environment defaults; missing or conflicting IDs can cause memories to be written/read under the wrong scope.","Local mode is non-persistent by default (data loss on restart) unless configured otherwise."],"error_quality":0.0}