mem0-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MEM0_API_KEY | Yes | API key for mem0 | |
| MEM0_API_URL | Yes | URL of the mem0 API, e.g. http://your-mem0-host:8888 | |
| MEM0_DEFAULT_USER_ID | No | Fallback user ID when no user_id, agent_id, or run_id is provided | |
| MEM0_DEFAULT_AGENT_ID | No | Default agent ID added to memories on add_memory when not provided |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_memoryA | Store a new memory. Provide at least one of user_id, agent_id, or run_id to scope it; if none are given, falls back to MEM0_DEFAULT_USER_ID. Tagged with MEM0_DEFAULT_AGENT_ID unless agent_id is given explicitly. |
| search_memoriesB | Semantic search over stored memories, scoped to a user_id/agent_id/run_id. |
| list_memoriesA | List stored memories for a given user_id/agent_id/run_id. |
| get_memoryA | Retrieve a single memory by its id. |
| update_memoryA | Update an existing memory's text and/or metadata. Confirm the memory_id with the user first if it wasn't just returned by another tool call. |
| delete_memoryA | Delete a single memory by its id. Confirm the memory_id with the user first if it wasn't just returned by another tool call. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/andresmorales07/mem0-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server