mem0-mcp
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).
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Uses environment variables for API keys (reduces risk of hardcoding). However, the provided content does not specify TLS requirements at the MCP transport layer, nor does it describe request-level authorization or fine-grained scopes; access appears governed by userId/appId arguments and server configuration. Ensure server stdout is clean (protocol reliability) and avoid leaking secrets in logs. Supabase mode requires embedding via OpenAI; ensure appropriate key handling and data governance.
⚡ Reliability
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.
Use Cases
- • Give LLM agents persistent, queryable memory across conversations
- • Store user/agent-specific notes, preferences, or facts and retrieve them semantically
- • Implement agent workflows that add, search, and prune memories via MCP tool calls
Not For
- • Highly sensitive data processing without a clear compliance posture
- • Environments that require strict, well-defined data retention guarantees without configuring expiration
- • Production setups where you cannot securely manage OpenAI/Mem0/Supabase credentials
Interface
Authentication
Authentication is configuration-based via environment variables; no per-request user auth model is described at the MCP layer beyond userId/appId parameters.
Pricing
Pricing details for Mem0 Cloud/OpenAI/Supabase are not specified in the provided content; Supabase notes mention a free tier, but limits are not given.
Agent Metadata
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.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for mem0-mcp.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-30.