Model Context Protocol moderate risk

Mem0

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.

Connections & Capabilities

Connects To

GitHubDocker

Capabilities

readwriteadmin

Quickstart

Install

pip install mem0-mcp-server

Config

{
  "mcpServers": {
    "mem0": {
      "command": "uvx",
      "args": ["mem0-mcp-server"],
      "env": {
        "MEM0_API_KEY": "m0-...",
        "MEM0_DEFAULT_USER_ID": "your-handle"
      }
    }
  }
}

Exposed MCP Tools (9)

moderate

add_memory

Saves text or conversation history for a user/agent.

Adds data to memory, potentially increasing storage costs.

safe

search_memories

Performs semantic search across existing memories.

Read-only operation, no data modification.

safe

get_memories

Lists memories with structured filters and pagination.

Read-only operation, no data modification.

safe

get_memory

Retrieves a single memory by its `memory_id`.

Read-only operation, no data modification.

high

update_memory

Overwrites a memory's text once the user confirms the `memory_id`.

Modifies existing data, potentially leading to data corruption if not handled carefully.

critical

delete_memory

Deletes a single memory by `memory_id`.

Deletes data, potentially leading to irreversible data loss.

critical

delete_all_memories

Bulk deletes all memories in the confirmed scope.

Bulk deletion can cause significant and irreversible data loss.

critical

delete_entities

Deletes a user/agent/app/run entity and its memories.

Deletes entities and associated memories, leading to significant data loss.

safe

list_entities

Enumerates users/agents/apps/runs stored in Mem0.

Read-only operation, no data modification.

Safety Assessment

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.

Requires API key for authentication.
Provides tools for managing memories, but includes delete operations.
Can be run locally, in Docker, or via Smithery, offering deployment flexibility.
Default user ID can be configured.

Includes tools for deleting memories, which could lead to data loss.
API key management is crucial to prevent unauthorized access.
Exposure of the API key in the environment variables poses a risk if not properly secured.
Bulk delete operations can be destructive if not used carefully.