Mem0 MCP Server
Persistent memory storage and retrieval for AI agents using the Mem0.ai platform.
Data last scanned 2 days ago · Reviewed 2 days ago
Overview
The Mem0 MCP Server provides tools for AI models to maintain persistent state across sessions by integrating with the Mem0.ai ecosystem. It facilitates the storage of long-term memory via the add_memory tool, allowing agents to retain context through complex user or agent identifiers. Beyond simple storage, the server offers advanced retrieval capabilities, including semantic and BM25 hybrid search. It supports full memory lifecycle management, such as paginated listing, individual record updates, and detailed retrieval through dedicated tool interfaces.
Our verdict
With a security score of 38/100, this server is classified as high-risk. The score is primarily impacted by the fact that it is a community-maintained project rather than an official vendor release, and critical aspects such as authentication methods and read-only mode safety have not been editorially reviewed. It is suitable for experimental development and testing environments, but should be avoided in production architectures handling sensitive user data.
- Uses only two direct dependencies for a smaller supply-chain footprint
- Supports modern Mem0 API V3 features with asynchronous polling
- Provides backward-compatible tool aliases for easier integration
- Authentication methods remain unreviewed for potential security exposures
- Community-maintained status lacks formal vendor verification
- Safety measures for read-only modes have not been audited
Setup
{
"mcpServers": {
"mem0-mcp": {
"args": [
"-y",
"@pinkpixel/mem0-mcp"
],
"command": "npx"
}
}
}Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Some servers require API keys or tokens as environment variables — check the project's README and add an "env" object if needed.
- No read-only mode — running this grants full read/write access.
- No built-in authentication — anyone with access to this config can invoke every tool it exposes.
Tools
| Tool | Description | Risk |
|---|---|---|
| add_memory | Stores a memory from text content or structured message arrays. | medium |
| search_memories | Searches memories using semantic and BM25 hybrid filters. | low |
| search_memory | Backward-compatible alias for search_memories. | low |
| list_memories | Paginated listing of memory records scoped by identifiers. | low |
| get_memory | Retrieves a single memory record by its ID. | low |
| update_memory | Modifies the text or metadata of an existing memory. | medium |
| delete_memory | Deletes a specific memory record by ID. | high |
| get_memory_history | Retrieves the audit trail of memory revisions (cloud only). | low |
| get_memory_capabilities | Exposes the feature matrix and support flags of the active backend storage mode. | low |
| batch_update_memories | Performs bulk updates of text contents for multiple memories (cloud only). | medium |
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| ChatGPT | ||||
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf |
Frequently asked questions
›What are the storage modes available for this server?
This server supports Cloud Storage using a Mem0 API key, Supabase Storage for self-hosting with your own database and OpenAI credentials, and Local Storage for development and testing.
›What is the behavior of the add_memory tool regarding background tasks?
By default, the tool polls the background queue until the operation is completed. You can set the waitForCompletion parameter to false if you prefer to receive the eventId immediately.
›Which features are exclusive to the Cloud Storage mode?
Cloud-only features include memory history tracking, batch updates, memory rating/feedback, and memory export job management.
›Is data persistence guaranteed in Local Storage mode?
No, Local Storage mode uses an in-memory vector database and data is lost when the server restarts unless specifically configured otherwise.
›What prerequisites are required for Supabase Storage mode?
You must provide SUPABASE_URL, SUPABASE_KEY, and an OPENAI_API_KEY for embedding generation, as well as perform the necessary initial database SQL migrations.
›Are there any safety requirements for the batch_delete_memories tool?
Yes, to prevent accidental deletion, the confirm parameter must be explicitly set to true to execute a batch deletion.
Badge
Maintain this server? Add the live badge to your README.