Overview
Features
Cross-session memory storage
Keeps memory across Claude conversations and sessions so context isn’t lost when token limits are reached or chats reset.
Multi-project isolation
Maintains separate memory, context, decisions, and history for each project to prevent cross-project leakage.
Automatic save & restore of memory categories
Automatically saves and restores project context, current work status, architectural decisions, and user preferences.
MCP server integration for Desktop Claude
Runs as an MCP server that directly integrates with the Desktop Claude app (not a CLI tool).
Memory toolset
Provides tools like save_context, load_contexts, forget_context, list_all_projects, and get_popular_tags for managing memory.
Privacy-first local storage
All data stays local to the user with no cloud sync, no telemetry, and full user control.
Configurable storage backend and OS notes
Default storage is a local database; optional Redis storage is available (experimental); configurable via environment variables and STORAGE_CONNECTION_STRING.
Who Is This For?
- Desktop Claude users:Persist memory across conversations and projects within the Claude Desktop app, maintaining context between sessions.
- MCP integrators / developers:Run Extended Memory MCP as an MCP server and wire it into Desktop Claude, with optional Redis storage and environment-based configuration.




