mcp-mem0
Provides an MCP server template integrated with Mem0 to let AI agents save, retrieve, and semantically search long-term memories backed by Supabase/PostgreSQL (vector storage) and configurable via an LLM provider for embeddings.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
TLS enforcement is not explicitly documented; SSE examples use http:// (could be TLS-terminated by a proxy). Authentication/authorization for the MCP server itself is not described. Secrets are referenced via environment variables, which is a positive sign, but there’s no explicit guidance on logging hygiene or secret management. Data governance/compliance not covered.
⚡ Reliability
Best When
You control the deployment (stdio or SSE) and can configure the LLM provider and PostgreSQL/Supabase for embeddings and storage.
Avoid When
You need a multi-tenant, internet-exposed service with robust authentication/authorization and documented security guarantees.
Use Cases
- • Long-term memory for MCP-enabled agent workflows
- • Semantic memory retrieval (context augmentation)
- • Building an MCP server template using Python and Mem0
- • Agent memory search across past interactions
Not For
- • Use as a standalone hosted API service without running/configuring the server
- • Storing sensitive data without evaluating privacy/security controls (no data governance details provided)
- • Environments requiring strong auth/access controls for the MCP server itself
Interface
Authentication
README describes configuration via environment variables for the upstream LLM and DATABASE_URL, but does not describe any authentication/authorization for the MCP server endpoints (especially SSE).
Pricing
Cost depends on the chosen LLM provider and database/embedding compute; not described in the repository materials provided.
Agent Metadata
Known Gotchas
- ⚠ If using SSE transport, ensure the client URL/path matches the server’s expected MCP SSE endpoint (README uses /sse in examples).
- ⚠ Embedding/LLM provider configuration is required for semantic indexing; misconfiguration will likely prevent memory operations but retry/error guidance is not documented.
- ⚠ No mention of server-side auth: do not expose SSE publicly without compensating controls (network/VPC/firewall).
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for mcp-mem0.
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.