mcp-memori
OfficialThe mcp-memori server provides persistent, structured memory for MCP-compatible AI agents, enabling long-term context retention across sessions and workflows.
Recall relevant memories (
recall): Call at the start of each user turn to fetch prior context, preferences, and facts relevant to the current query — grounding responses with stored knowledge.Store durable memories (
advanced_augmentation): Call after composing a response to persist important facts, preferences, and outcomes for future sessions.Agent-native memory: Captures memory from tool calls, decisions, and results — not just natural language conversations.
Reduce token usage: Retrieves only relevant memories (~5% of full-context footprint) instead of loading full conversation histories, lowering costs while improving accuracy.
Isolate memory by process: Use an optional
process_idto scope memory to specific agents, apps, or workflows for multi-agent separation.Zero-friction integration: Works with any MCP-compatible client — no SDK or code changes required, only API key configuration. Sessions are derived automatically from entity ID and UTC timestamp.
Memori MCP
Persistent AI memory for any MCP-compatible agent — no SDK required.
memori-mcp is the official Memori MCP server. Connect it to your AI agent to give it long-term memory: recall relevant facts before answering, store durable preferences after responding, and maintain context across sessions.
Why Memori MCP?
Memori turns stateless agents into stateful systems by providing structured, persistent memory that works across sessions and workflows.
Persistent state beyond prompts — Most agents rely on prompt context and lose state between runs. Memori provides durable, structured memory so agents can retain facts, decisions, and outcomes over time.
Memory from execution (not just natural language) — Traditional systems extract memory from chat. Memori builds memory from agent execution itself — including tool calls, decisions, and results. This enables true agent-native memory, not just conversational recall.
Lower cost, higher accuracy — Instead of expanding prompt context, Memori retrieves only what matters.
Significantly reduced token usage
Faster responses
Improved accuracy vs long-context approaches
Works with any MCP client and production-ready - No SDK, no code changes, just config
Memori is state infrastructure for production agents — enabling persistent memory, efficient retrieval, and structured context across both natural language and agent execution.
LoCoMo Benchmark
Memori was evaluated on the LoCoMo benchmark for long-conversation memory and achieved 81.95% overall accuracy while using an average of 1,294 tokens per query. That is just 4.97% of the full-context footprint, showing that structured memory can preserve reasoning quality without forcing large prompts into every request.
Compared with other retrieval-based memory systems, Memori outperformed Zep, LangMem, and Mem0 while reducing prompt size by roughly 67% vs. Zep and lowering context cost by more than 20x vs. full-context prompting.
Read the benchmark overview or download the paper.
How It Works
The server exposes two tools:
Tool | When to call | What it does |
| Start of each user turn | Fetches relevant memories for the current query |
| After composing a response | Stores durable facts and preferences for future sessions |
Example Agent Flow
Given the message: "I prefer Python and use uv for dependency management."
Agent calls
recallwith the user message asqueryAgent uses any returned facts to compose a response
Agent calls
advanced_augmentationwith the user message and response
On a later turn — "Write a hello world script" — the agent recalls the Python + uv preference and personalizes its response automatically.
Prerequisites
A Memori API key from app.memorilabs.ai
An
entity_idto identify the end user (e.g.user_123)An optional
process_idto identify the agent or workflow (e.g.my_agent)
Export these in your shell or replace the placeholders directly in your config:
export MEMORI_API_KEY="your-memori-api-key"
export MEMORI_ENTITY_ID="user_123"
export MEMORI_PROCESS_ID="my_agent" # optionalServer Details
Property | Value |
Endpoint |
|
Transport | Stateless HTTP |
Auth | API key via request headers |
Headers
Header | Required | Description |
| Yes | Your Memori API key |
| Yes | Stable end-user identifier (e.g. |
| No | Process, app, or workflow identifier for memory isolation |
session_id is derived automatically as <entity_id>-<UTC year-month-day:hour> — you do not need to provide it.
Verifying the Connection
After configuring any client:
Confirm the MCP server shows as connected in your client's UI
Check that
recallandadvanced_augmentationappear in the tools listSend a test message —
recallshould return a response (even if empty for new entities)Verify
advanced_augmentationreturnsmemory being created
If you receive 401 errors, double-check your X-Memori-API-Key value. See the Troubleshooting guide for more help.
Links
Latest Blog Posts
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/MemoriLabs/mcp-memori'
If you have feedback or need assistance with the MCP directory API, please join our Discord server