MCP Connector Featured

Maintain Claude Desktop Context Across Sessions

Extended Memory MCP gives Claude Desktop persistent, project-isolated cross-session memory stored locally on your machine.

Works with redissqlite

15
Spark score
out of 100
Status Verified Official
Updated 10 months ago
Version 1.0.0
Models

Add to Favorites

Why it matters

This asset ensures your Claude Desktop application remembers context, architectural decisions, and communication preferences between sessions, preventing data loss and maintaining project continuity.

Outcomes

What it gets done

01

Save and restore project context automatically.

02

Maintain complete isolation between different projects.

03

Store architectural decisions and communication preferences.

04

Utilize local storage with optional Redis support.

Install

Add it to your toolbox

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/vb-extended-memory | bash

Capabilities

Tools your agent gets

save_context

Save important information with tags for later retrieval.

load_contexts

Load previous context and conversations from memory storage.

forget_context

Delete outdated information from memory storage.

list_all_projects

View all your projects stored in memory.

get_popular_tags

Find frequently used tags in your saved contexts.

Overview

Extended Memory MCP Server

Extended Memory MCP gives Claude Desktop cross-session memory: it saves and restores project context, architectural decisions, and working preferences locally, with isolation between projects. Use it when you work on the same project across many separate Claude Desktop conversations and want prior decisions and context to persist automatically.

What it does

Extended Memory MCP is a Model Context Protocol server that gives Claude Desktop cross-session memory. Without it, a Claude conversation loses all context once it hits token limits or you start a new chat: project details, architectural decisions, and working preferences all have to be re-explained from scratch. The server automatically saves and restores your project context and current work status, architectural decisions and their reasoning, and Claude's communication style and your working preferences, with complete isolation between different projects.

When to use - and when NOT to

Use it if you work with the Desktop Claude app across multiple sessions on the same project and want Claude to remember prior decisions and context without you re-explaining them each time. It is built specifically for the Desktop Claude app, not as a CLI tool - it runs as an MCP server integrated through the Model Context Protocol. Memory is per-project: without explicitly telling Claude a project_id in your custom instructions, every conversation shares the same "general" scope, so isolation has to be set up deliberately rather than relying on auto-detection. It is also worth knowing that Claude decides when to use the memory tools; it may not load memory automatically for conversations that don't look memory-related, and you may need to prompt it explicitly.

Capabilities

  • save_context: save important information with tags
  • load_contexts: load previous context and conversations
  • forget_context: remove outdated information
  • list_all_projects: view all your projects
  • get_popular_tags: find commonly used tags
  • Local, private storage: no cloud sync, no analysis of stored data, no telemetry, and full user control - the project describes itself as a "dumb" storage client
  • Storage backends: SQLite by default, with STORAGE_CONNECTION_STRING defaulting to ~/.local/share/extended-memory-mcp/memory.db on macOS/Linux, plus experimental Redis support via a redis:// connection string

How to install

Install from PyPI:

pip install extended-memory-mcp

Then add it to the Desktop Claude app's MCP configuration (Settings, Developer, Edit Config):

{
  "mcpServers": {
    "extended-memory": {
      "command": "python3",
      "args": ["-m", "extended_memory_mcp.server"],
      "env": {
        "LOG_LEVEL": "INFO"
      }
    }
  }
}

Requirements are Python 3.8+ and the Desktop Claude app. Redis support can be added with pip install extended-memory-mcp[redis], and Windows installs are recommended to set an explicit STORAGE_CONNECTION_STRING path rather than rely on the default. After restarting Claude Desktop, verify the connection in Developer Settings, then test it by asking Claude to save and later recall project information.

Who it's for

Desktop Claude app users who work on the same project across many separate conversations and want architectural decisions, working preferences, and project context to persist between sessions, on local storage they fully control. It is released under the MIT License.

Source README

Extended Memory MCP

PyPI version
Python 3.8+
License: MIT

Extended Memory MCP is a Model Context Protocol (MCP) tool that provides cross-session memory storage for Claude Desktop app.

This tool solves a fundamental problem: when your Claude conversation reaches token limits or you start a new chat, all context is lost. Claude forgets your project details, previous decisions, and working relationships. You have to re-explain everything from scratch.

Extended Memory MCP automatically saves and restores:

  • Your project context and current work status
  • Architectural decisions and their reasoning
  • Claude's communication style and your working preferences
  • Complete isolation between different projects

This is specifically designed for Desktop Claude app users who want persistent memory across conversation sessions. It's not a CLI tool - it runs as an MCP server that integrates directly with the Desktop Claude app through the Model Context Protocol.

🚀 Quick Start

Requirements

  • Python 3.8+
  • Desktop Claude app

Step 1: Installation

Option A: Install from PyPI (Recommended)
pip install extended-memory-mcp
Option B: Install from Source (Development)
git clone https://github.com/ssmirnovpro/extended-memory-mcp.git
cd extended-memory-mcp
pip install -e ".[dev]"

Step 2: Desktop Claude App Configuration

Edit your Desktop Claude app MCP configuration:

  1. Open Desktop Claude app
  2. Go to SettingsDeveloperEdit Config
  3. Add the Extended Memory MCP server to your configuration

Configuration:

{
  "mcpServers": {
    "extended-memory": {
      "command": "python3",
      "args": ["-m", "extended_memory_mcp.server"],
      "env": {
        "LOG_LEVEL": "INFO"
      }
    }
  }
}

Configuration for source installation (if you installed from GitHub):

{
  "mcpServers": {
    "extended-memory": {
      "command": "python3", 
      "args": ["/path/to/extended-memory-mcp/mcp-server/server.py"],
      "env": {
        "LOG_LEVEL": "INFO"
      }
    }
  }
}

If you already have other MCP servers configured, add the extended-memory entry to your existing mcpServers section.

Step 3: Additional Installation Options

Install with Redis Support
pip install extended-memory-mcp[redis]
Install Development Version
pip install extended-memory-mcp[dev]
Configuration Parameters
Parameter Purpose Default Value
STORAGE_CONNECTION_STRING Database location ~/.local/share/extended-memory-mcp/memory.db (macOS/Linux)
LOG_LEVEL Logging verbosity INFO
Platform-Specific Notes

macOS & Linux: Can use default storage location (auto-created in user data directory)

Windows: Recommended to set explicit STORAGE_CONNECTION_STRING path:

"env": {
  "STORAGE_CONNECTION_STRING": "sqlite:///C:/Users/YourName/extended-memory/memory.db"
}
Redis Storage (Experimental)

For advanced users wanting Redis instead of SQLite:

"env": {
  "STORAGE_CONNECTION_STRING": "redis://localhost:6379/0"
}

Note: Redis support is experimental. Performance characteristics are not fully tested.

Step 3: Verification

  1. Restart Claude Desktop
  2. Check MCP Connection - In Claude, the extended-memory server should appear in Developer Settings
  3. Test Memory - Ask Claude: "Save that we're working on project X with React architecture"
  4. Verify Persistence - Start a new conversation and ask Claude about your projects

🔒 Privacy & Local Storage

Extended Memory MCP is a "dumb" storage client - your data remains completely local and private:

  • No cloud sync - All data stored on your machine only
  • No analysis - Data is stored as-is without processing or analysis
  • No telemetry - Zero external communication or data collection
  • Full control - You own and control all memory data

🔧 Project Organization & Usage

Project Isolation

Memory is organized by projects with strict isolation between them. Each project maintains its own separate context, decisions, and history.

Default behavior: All conversations use the general project scope unless explicitly specified.

For proper project isolation:
Include the project identifier in your Claude custom instructions:

You have external memory; follow its instructions for effective usage. When working with external memory, always specify that this is project "<your-short-project-id-here>" as its project_id for read and write operations.

Replace <your-short-project-id-here> with your actual project identifier (e.g., mobile_app, blog_redesign, work_project).

Important: Projects are not auto-detected. Without explicit project_id specification, all conversations use the general scope.

How the Memory Tool Works

Extended Memory provides Claude with memory management tools, but Claude decides when and how to use them. The AI may choose not to load memory automatically, especially for general conversations that don't seem memory-related.

If Claude doesn't recall previous context, you can prompt:

  • "Load my project context"
  • "What do you remember about this project?"
  • "Check our previous work on this"

Claude has several memory tools available:

  • save_context - Save important information with tags
  • load_contexts - Load previous context and conversations
  • forget_context - Remove outdated information
  • list_all_projects - View all your projects
  • get_popular_tags - Find commonly used tags

🤝 Community & Support

🔒 Privacy & Security

  • Local-First: All data stored locally on your machine
  • No Telemetry: No data collection or external communication
  • Open Source: Full transparency - audit the code yourself
  • GDPR Compliant: You control your data completely

📄 License

This project is licensed under the MIT License.

For Everyone: Free to use, modify, and distribute without restrictions. Use it in commercial or personal projects - no strings attached.

See LICENSE for full details.

🌟 Star History

Star History Chart


Made with ❤️ for the AI community

Extended Memory MCP - Because your AI assistant should remember.

FAQ

Common questions

Discussion

Questions & comments · 0

Sign In Sign in to leave a comment.