mcp-openmemory
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MEM0_API_KEY | No | Admin API key, sent as X-API-Key | |
| MEM0_TIMEOUT | No | HTTP timeout (s) for reads (search/list) | 10 |
| MEM0_MEM0_URL | No | Base URL of the mem0 REST server | http://mem0:8000 |
| MEM0_SERVER_HOST | No | Bind host for the SSE server | 0.0.0.0 |
| MEM0_SERVER_PORT | No | Bind port for the SSE server | 8000 |
| MEM0_SEARCH_LIMIT | No | Default number of memories per search | 5 |
| MEM0_WRITE_TIMEOUT | No | HTTP timeout (s) for writes (add runs a server-side LLM extraction) | 60 |
| MEM0_DEFAULT_USER_ID | No | Bucket used when no user_id is passed | coder-agent |
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_memoryA | Search long-term memory for entries relevant to a query. Call this at the start of a task (or whenever prior context would help) to recall what was learned in earlier sessions. The memory bucket is determined automatically from your authenticated identity; you cannot and need not specify whose memory to read. |
| add_memoryA | Store a new memory (a fact, preference, or exchange) in long-term memory. Use this automatically when you learn something durable about the user or project, or on explicit request ("remember that ..."). mem0 runs a server-side extraction to decide what is worth keeping, so not every call creates a stored entry. The memory bucket is determined automatically from your authenticated identity; you cannot and need not specify whose memory to write. |
| list_memoriesA | List all stored memories for your authenticated identity's bucket. Returns: A list of memory objects with their ids and remembered text. |
| delete_memoryA | Delete a single memory by its id. Note: mem0 deletes by id without a user filter, so ids should only be
obtained from this identity's own |
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/dedsxc/mcp-openmemory'
If you have feedback or need assistance with the MCP directory API, please join our Discord server