Loading...
Mem0 MCP Server provides a bridge between Mem0's Memory API and MCP clients, enabling LLMs to add, search, update, and delete long-term memories.
Boost this tool
Subscribe to listing upgrades or segmented pushes.
Mem0 MCP Server provides a bridge between Mem0's Memory API and MCP clients, enabling LLMs to add, search, update, and delete long-term memories.
The Mem0 MCP Server offers memory management capabilities with some inherent risks due to write and delete operations. It's relatively safe when used with strong API key management and careful consideration of delete operations. Risks increase with exposure of the API key and misuse of bulk delete functionalities.
Performance depends on the Mem0 API's responsiveness and the size of the memory store. Semantic search may be slower with large datasets.
Cost is primarily driven by Mem0 API usage, including storage and API call volume. Monitor usage to avoid unexpected charges.
pip install mem0-mcp-server{
"mcpServers": {
"mem0": {
"command": "uvx",
"args": ["mem0-mcp-server"],
"env": {
"MEM0_API_KEY": "m0-...",
"MEM0_DEFAULT_USER_ID": "your-handle"
}
}
}
}OPENAI_API_KEYadd_memorySaves text or conversation history for a user/agent.
Adds data to memory, potentially increasing storage costs.
search_memoriesPerforms semantic search across existing memories.
Read-only operation, no data modification.
get_memoriesLists memories with structured filters and pagination.
Read-only operation, no data modification.
get_memoryRetrieves a single memory by its `memory_id`.
Read-only operation, no data modification.
update_memoryOverwrites a memory's text once the user confirms the `memory_id`.
Modifies existing data, potentially leading to data corruption if not handled carefully.
delete_memoryDeletes a single memory by `memory_id`.
Deletes data, potentially leading to irreversible data loss.
delete_all_memoriesBulk deletes all memories in the confirmed scope.
Bulk deletion can cause significant and irreversible data loss.
delete_entitiesDeletes a user/agent/app/run entity and its memories.
Deletes entities and associated memories, leading to significant data loss.
list_entitiesEnumerates users/agents/apps/runs stored in Mem0.
Read-only operation, no data modification.
API Key
The Mem0 MCP Server offers memory management capabilities with some inherent risks due to write and delete operations. It's relatively safe when used with strong API key management and careful consideration of delete operations. Risks increase with exposure of the API key and misuse of bulk delete functionalities.
The agent has full read/write access to Mem0 based on the configured API key. Exercise caution when granting autonomy, especially with delete operations.
Production Tip
Implement robust API key management and monitoring to prevent unauthorized access and data loss.
The Mem0 API key authenticates your application with the Mem0 platform and grants access to the Memory API.
Store the API key securely, avoid committing it to version control, and use environment variables to manage it.
Immediately revoke the compromised key and generate a new one to prevent unauthorized access.
Currently, Mem0 does not offer granular permission scopes for API keys. Treat the key with utmost care.
Monitor API usage through the Mem0 platform's dashboard or by tracking API call volume in your application logs.
The default user ID is used when no specific user ID is provided in the API calls. It helps to organize and filter memories.
Costs are primarily associated with Mem0 API usage, including storage and API call volume. Monitor usage to avoid unexpected charges.