mcp-openmemory
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-openmemorysearch my memories about the recent bug fix"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-openmemory
A FastMCP server that exposes mem0 long-term memory to MCP clients (e.g. an AI coding agent) over SSE.
It is a thin, stateless MCP layer over an existing mem0 REST server
(http://mem0:8000) — it does not run its own vector store. This keeps a
single source of truth for memory (the mem0 pgvector store) instead of
introducing a second, disconnected memory silo.
Tools
Tool | Purpose |
| Recall memories relevant to a query. Call at the start of a task. |
| Store a fact/preference/exchange. Use automatically when you learn something durable, or on explicit request. |
| List stored memories for a bucket. |
| Forget a single memory by id. |
Memory is isolated per user_id ("bucket"). When a caller omits user_id,
MEM0_DEFAULT_USER_ID is used, giving the agent a single shared memory.
Related MCP server: mem0-agent-memory
Configuration
Environment variables (prefix MEM0_):
Variable | Default | Description |
|
| Base URL of the mem0 REST server |
| (none) | Admin API key, sent as |
|
| Bucket used when no |
|
| Primary trusted header carrying the end-user identity |
| (none) | Extra identity headers, tried after |
|
| Default number of memories per search |
|
| HTTP timeout (s) for reads (search/list) |
|
| HTTP timeout (s) for writes (add runs a server-side LLM extraction) |
|
| Bind host for the SSE server |
|
| Bind port for the SSE server |
Run
pip install -e .
openmemory-mcp-sse # SSE at http://0.0.0.0:8000/sse
# or
openmemory-mcp # stdio modeContainer
Built by the release-containers workflow (release-please) to
ghcr.io/dedsxc/openmemory-mcp:<version> for linux/amd64,linux/arm64.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Alicense-qualityBmaintenanceSelf-hosted remote MCP memory server for ChatGPT and AI agents.Last updated2MIT
- Alicense-qualityDmaintenanceAn MCP server that provides persistent memory capabilities for AI agents using Mem0, enabling storage, search, and management of contextual information across conversations with support for multiple backends and LLM providers.Last updatedMIT
- Flicense-qualityDmaintenanceA remote MCP server deployed on Cloudflare Workers for memory storage and retrieval using Mem0, supporting SSE and standard MCP connections.Last updated1
- AlicenseAqualityBmaintenanceA long-term memory MCP server for AI agents that stores memories (facts, decisions, etc.) in a single SQLite database with hybrid search and full edit history, ensuring consistency across sessions.Last updated24MIT
Related MCP Connectors
User-owned memory for AI agents, Copilot, Claude, IDEs, CLIs, and chat apps over remote MCP.
Person-owned, portable AI memory as a remote MCP server, readable and writable by any MCP client.
Cloud-hosted MCP server for durable AI memory
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