Mem0 MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MEM0_API_KEY | Yes | Your mem0 API key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_memoryB | Store a new preference, fact, or conversation snippet. Requires at least one: user_id, agent_id, or run_id. |
| search_memoriesA | Run a semantic search over existing memories. |
| get_memoriesA | Page through memories using filters instead of search. |
| delete_all_memoriesC | Delete every memory in the given user/agent/app/run but keep the entity. |
| list_entitiesB | List which users/agents/apps/runs currently hold memories. |
| get_memoryB | Fetch a single memory once you know its memory_id. |
| update_memoryB | Overwrite an existing memory’s text. |
| delete_memoryB | Delete one memory after the user confirms its memory_id. |
| delete_entitiesA | Remove a user/agent/app/run record entirely (and cascade-delete its memories). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| memory_assistant | Get help with memory operations and best practices. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Most tools have distinct purposes, but get_memories and search_memories could cause confusion as both involve retrieving memories with filters, though search_memories adds semantic search. The other tools (add, delete, update, list) are clearly differentiated by their actions on memories or entities.
All tools follow a consistent verb_noun pattern (e.g., add_memory, delete_memory, get_memories), with clear and predictable naming. There are no deviations in style or convention across the set.
With 9 tools, this server is well-scoped for memory management, covering core operations like CRUD for memories and entities, plus search and listing. Each tool serves a clear purpose without redundancy or bloat.
The toolset provides complete coverage for memory management: create (add_memory), read (get_memory, get_memories, search_memories), update (update_memory), delete (delete_memory, delete_all_memories, delete_entities), and list (list_entities). No obvious gaps exist for the domain.