memory-mcp
The memory-mcp server provides a persistent memory service for Claude Code, enabling automatic saving, recall, and semantic search of conversation context, decisions, preferences, and knowledge entities across sessions.
Episode Management
Start, close, and archive conversation sessions (episodes) with tags and auto-generated summaries
Get the currently active episode, list all historical episodes, or retrieve full details (messages + linked entities) of a specific episode
Knowledge Entity Management
Add, confirm, reject, or deprecate knowledge entities of types:
Decision,Preference,Concept,Habit,File, orArchitectureList pending auto-detected entity candidates awaiting review
Memory Retrieval & Search
Semantic search across all stored episodes and entities using natural language queries
Filter entity searches by type (e.g., all Decisions or Preferences)
Message Caching
Manually cache user or assistant messages (with automatic entity detection)
Clear the entire cache or clean up messages older than a specified number of days
System & Status
Retrieve system statistics (episodes, entities, etc.) and check vector encoder status
Automatic Context Management When configured with Claude Code hooks, it automatically saves messages, recalls relevant memories, and injects context into ongoing conversations.
Dual-Layer Storage Supports both user-level (shared across projects) and project-level (isolated per project) memory storage.
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., "@memory-mcprecall what we discussed about authentication"
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.
Memory MCP Service
A persistent memory MCP service for Claude Code. Automatically saves conversations and retrieves relevant history across sessions.
What it does: Every time you chat with Claude Code, your conversation context (decisions, preferences, key discussions) is saved and automatically recalled in future sessions — so Claude always has the background it needs.

Quick Start
Prerequisites
Install uv (Python package runner):
# Windows
powershell -c "irm https://astral.sh/uv/install.ps1 | iex"
# Mac/Linux
curl -LsSf https://astral.sh/uv/install.sh | shRequires Python 3.10 - 3.13 (chromadb is not compatible with Python 3.14+).
1. Initialize (First Time Only)
Download the vector model (~400MB, one-time):
uvx --from chenxiaofie-memory-mcp memory-mcp-init2. Add MCP Server to Claude Code
claude mcp add memory-mcp -s user -- uvx --from chenxiaofie-memory-mcp memory-mcp3. Configure Hooks (Recommended)
Hooks enable fully automatic message saving. Without hooks, you need to manually call memory tools.
Add the following to ~/.claude/settings.json:
{
"hooks": {
"SessionStart": [{
"matcher": ".*",
"hooks": [{ "type": "command", "command": "uvx --from chenxiaofie-memory-mcp memory-mcp-session-start" }]
}],
"UserPromptSubmit": [{
"matcher": ".*",
"hooks": [{ "type": "command", "command": "uvx --from chenxiaofie-memory-mcp memory-mcp-auto-save" }]
}],
"Stop": [{
"matcher": ".*",
"hooks": [{ "type": "command", "command": "uvx --from chenxiaofie-memory-mcp memory-mcp-save-response" }]
}],
"SessionEnd": [{
"matcher": ".*",
"hooks": [{ "type": "command", "command": "uvx --from chenxiaofie-memory-mcp memory-mcp-session-end" }]
}]
}
}4. Verify
claude mcp listYou should see memory-mcp: ... - ✓ Connected.
That's it! Start a new Claude Code session and your conversations will be automatically saved and recalled.
Related MCP server: claude-memory-mcp
How It Works
Session Start ──► Create Episode ──► Monitor Process (background)
│
User Message ──► Save Message ──► Recall Related Memories ──► Inject Context
│
Claude Reply ──► Save Response │
│
Session End ──► Close Signal ──► Archive Episode + Generate SummaryEpisodes: Each conversation session is an "episode" with auto-generated summaries
Entities: Key knowledge extracted from conversations (decisions, preferences, concepts)
Dual-layer storage: User-level (shared across projects) + Project-level (isolated per project)
Semantic search: Vector-based retrieval finds relevant past context
Usage
Automatic Mode (With Hooks)
Once hooks are configured, everything is automatic. Claude will see relevant history from past sessions as context.
Manual Mode
You can also call memory tools directly in Claude Code:
# Start a new episode
memory_start_episode("Login Feature Development", ["auth"])
# Record a decision
memory_add_entity("Decision", "Use JWT + Redis", "For distributed deployment")
# Search history
memory_recall("login implementation")
# Close episode
memory_close_episode("Completed JWT login feature")Hooks Reference
Hook | What it does | Timing |
SessionStart | Creates a new episode | ~50ms |
UserPromptSubmit | Saves user message + retrieves related memories | ~1-2s |
Stop | Saves assistant response | ~1s |
SessionEnd | Signals episode closure | ~50ms |
Tools Reference
Tool | Description |
| Start a new episode |
| Close and archive current episode |
| Get current active episode |
| Add a knowledge entity |
| Confirm a detected entity candidate |
| Reject a false detection |
| Mark an entity as outdated |
| List pending entity candidates |
| Semantic search across episodes and entities |
| Search entities by type |
| Get full episode details |
| List all episodes chronologically |
| Get system statistics |
| Check vector encoder status |
| Manually cache a message |
| Clear message cache |
| Clean up old cached messages |
Entity Types
Type | Level | Description |
| Project | Technical decisions for this project |
| Project | Architecture designs |
| Project | Important file descriptions |
| User | Personal preferences (shared across projects) |
| User | General concepts |
| User | Work habits |
Storage Locations
User-level:
~/.claude-memory/Project-level:
{project-root}/.claude/memory/
If you need to run from source (e.g., for development):
git clone https://github.com/chenxiaofie/memory-mcp.git
cd memory-mcp
# Windows:
install.bat
# Mac/Linux:
chmod +x install.sh && ./install.shThen configure MCP server with the venv Python:
# Windows:
claude mcp add memory-mcp -s user -- "C:\path\to\memory-mcp\venv310\Scripts\python.exe" -m memory_mcp.server
# Mac/Linux:
claude mcp add memory-mcp -s user -- /path/to/memory-mcp/venv310/bin/python -m memory_mcp.serverAuthor
陈佳俊 (Jiajun Chen) — front-end engineer based in Hangzhou, China. GitHub @chenxiaofie · feifeichen1999@gmail.com
本项目由陈佳俊(GitHub: chenxiaofie)开发并维护。
License
MIT License - see LICENSE file for details.
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-qualityDmaintenanceAn MCP server that gives Claude persistent memory by storing conversation context, entities, and enabling semantic search across sessions.Last updated331MIT
- Alicense-qualityCmaintenanceAn MCP server that gives Claude Code cross-session memory persisted to a plain .claude-memory.md file in your repo.Last updatedMIT
- Alicense-qualityDmaintenancePersistent memory MCP server for Claude Code that captures and recalls project context across sessions, eliminating the need to re-explain architecture and decisions daily.Last updated231MIT
- Alicense-qualityBmaintenanceA persistent memory MCP server for Claude Code that enables long-term recall across sessions via hybrid search, code intelligence, and tools for reading/writing memory.Last updated39MIT
Related MCP Connectors
Cloud-hosted MCP server for durable AI memory
Persistent memory and cross-session learning for AI coding assistants (hosted remote MCP).
One memory, every AI: Claude, ChatGPT, Perplexity, Gemini, Cursor, OpenClaw, Hermes, any MCP client.
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/chenxiaofie/memory-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server