Cross-session memory for Claude Code β context capture, semantic search, recall
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
π‘ Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows)
Cross-session memory for Claude Code β never lose context between sessions.
Claude Memory Manager automatically captures architectural decisions, code changes, bug fixes, and configuration choices from your Claude Code sessions, then intelligently retrieves relevant context when you start new sessions.
Every time you use Claude Code, valuable context is created and lost when the session ends:
Claude Memory Manager solves this by:
For local embeddings (no API key needed):
For development:
This creates the SQLite database at ~/.claude-memory/memory.db and saves a config file.
Add to your Claude Desktop config (see MCP Setup):
| Command | Description |
|---|---|
claude-memory init | Initialize the SQLite database |
claude-memory ingest [PATH] | Ingest session logs from path |
claude-memory ingest --watch | Watch and auto-ingest new sessions |
claude-memory search "query" | Hybrid semantic + keyword search |
claude-memory context [PROJECT] | Generate context summary |
claude-memory list | List all indexed sessions |
claude-memory stats | Database statistics |
claude-memory prune --older-than 90d | Remove old memories |
claude-memory export | Export memories as JSON |
claude-memory serve | Start MCP server mode |
| Option | Description |
|---|---|
--config PATH | Custom config file path |
--verbose / -v | Enable debug logging |
--version | Show version |
| Option | Description |
|---|---|
--project / -p | Filter by project path |
--category / -c | Filter by category |
--limit / -n | Max results (default: 5) |
Memories are classified into these categories:
decision β Architectural and design decisionscode_change β Significant code modificationsbug_fix β Bug identification and resolutionconfig β Configuration and environment changeserror_resolution β Errors encountered and solvedpreference β User preferences and conventionsdiscussion β General discussion summariesFind your Claude Desktop config file:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonAdd the memory server:
See examples/claude-desktop-config.json for a complete example.
Once connected, Claude Desktop can use these tools:
| Tool | Description |
|---|---|
memory_search | Search memories by query with optional filters |
memory_recall | Get a formatted context summary for a project |
memory_save | Save a new memory directly |
memory_stats | Get database statistics |
Configuration is loaded from (in priority order):
~/.claude-memory/config.json)| Variable | Description | Default |
|---|---|---|
CLAUDE_SESSIONS_PATH | Path to session logs | ~/.claude/projects |
CLAUDE_MEMORY_DB_PATH | Database file path | ~/.claude-memory/memory.db |
CLAUDE_MEMORY_EMBEDDING_PROVIDER | anthropic, voyage, or local | local |
ANTHROPIC_API_KEY | Anthropic API key | β |
VOYAGE_API_KEY | Voyage AI API key | β |
CLAUDE_MEMORY_MAX_TOKENS | Max tokens for context | 2000 |
CLAUDE_MEMORY_LOG_LEVEL | Log level | INFO |
| Provider | Dimension | Requires |
|---|---|---|
voyage | 1024 | VOYAGE_API_KEY |
anthropic | 1024 | ANTHROPIC_API_KEY |
local | 384 | pip install claude-memory-manager[local] |
If no provider is available, a stub provider is used (keyword search still works, but semantic search is disabled).
Where are my memories stored?
In a SQLite database at ~/.claude-memory/memory.db. All data stays local.
Does this send my code to any API?
Only if you configure the Voyage or Anthropic embedding provider. In that case, only memory text content (not full session logs) is sent to generate embeddings. Use local for fully offline operation.
How does deduplication work? Each memory's content is hashed (SHA-256). If a memory with the same hash already exists, it is skipped during ingestion.
How does hybrid search work? Results from cosine-similarity vector search (70% weight) are combined with SQLite FTS5 keyword search results (30% weight). Memories appearing in both get combined scores.
Can I export my memories?
Yes: claude-memory export > memories.json or claude-memory export -o file.json.
How do I prune old memories?
claude-memory prune --older-than 90d removes memories older than 90 days. Supports d (days), w (weeks), m (months), y (years).
MIT License. Copyright (c) 2026 NyxTools.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/claude-memory-manager)<a href="https://allmcps.com/mcp/claude-memory-manager"><img src="https://allmcps.com/api/badge/claude-memory-manager?style=directory" alt="Claude Memory Manager on AllMCPs" /></a>