MemPalace: The Open-Source AI Memory System That Scores 96.6% — Complete Guide (2026)

The Problem MemPalace Solves

After six months of daily AI use, you've generated approximately 19.5 million tokens of conversations. That's every decision, every solution, every trade-off analysis. The question is: where did it all go?

The difference is dramatic: $10/year for 96.6% recall vs. $507/year for lossy summaries that throw away context.

The Palace Architecture

MemPalace is inspired by the ancient Greek Method of Loci — a memorization technique where you place ideas in rooms of an imaginary building and walk through it to recall them. MemPalace applies the same principle to AI memory:

The Building Blocks

Why Structure Matters

This isn't cosmetic organization. The palace structure directly improves retrieval accuracy:

The architecture gives AI a navigable map instead of a flat search index. When you ask "what did we decide about auth?", MemPalace knows which wing to search, which rooms to check, and which halls to follow, instead of scanning every piece of data.

The Memory Stack

MemPalace uses a 4-layer system that loads only what's needed:

Your AI wakes up with L0 + L1 (~170 tokens) and immediately knows your world — your team members, your projects, your preferences. Searches only fire when needed, keeping costs near zero.

Getting Started

Installation

pip install mempalace

Requirements: Python 3.9+, no API key, no internet after install.

Setup

# Initialize — guided onboarding, sets up wings for your people and projects
mempalace init ~/projects/myapp

# Mine your project files (code, docs, notes)
mempalace mine ~/projects/myapp

# Mine your AI conversations (Claude, ChatGPT, Slack exports)
mempalace mine ~/chats/ --mode convos

# General mode — auto-classifies into decisions, milestones, problems
mempalace mine ~/chats/ --mode convos --extract general

Search

# Search everything
mempalace search "why did we switch to GraphQL"

# Search within a specific project
mempalace search "database decision" --wing myapp

# Search a specific topic
mempalace search "auth approach" --room auth-migration

Connect to Your AI

For Claude, ChatGPT, Cursor, Gemini (MCP-compatible tools):

claude mcp add mempalace -- python -m mempalace.mcp_server

Now your AI has 19 tools available through MCP. Ask it anything:

"What did we decide about auth last month?"

Claude calls mempalace_search automatically, gets verbatim results, and answers. You never type a search command — the AI handles it.

For local models (Llama, Mistral):

mempalace wake-up > context.txt
# Paste context.txt into your model's system prompt

MemPalace vs. The Competition

The Fundamental Difference

Most memory systems use an AI to extract what it thinks is important from your conversations — "user prefers Postgres," "team decided to use Clerk." Then they throw away the original conversation.

MemPalace stores everything verbatim and uses semantic search to find what's relevant. The 96.6% recall proves this works better than extraction-based approaches. You never lose the reasoning, the context, or the nuance behind a decision.

The 19 MCP Tools

When connected via MCP, your AI gets access to a comprehensive toolkit:

Palace (Read)

Palace (Write)

Knowledge Graph

Navigation & Agents

Specialist Agents

MemPalace lets you create agents with their own memory:

~/.mempalace/agents/
  ├── reviewer.json       # code quality, patterns, bugs
  ├── architect.json      # design decisions, tradeoffs
  └── ops.json            # deploys, incidents, infra

Each agent has a focus, keeps a diary (in AAAK), and builds expertise by reading its own history. The reviewer remembers every bug pattern it's seen. The architect remembers every design decision. They're specialist lenses on your data.

Your CLAUDE.md only needs one line:

You have MemPalace agents. Run mempalace_list_agents to see them.

Honest Limitations

MemPalace launched with impressive numbers but also with acknowledged issues. To their credit, the creators published a detailed correction on April 7:

What Was Overstated

• →AAAK compression — Originally claimed "30×" compression. Actually lossy, and small-scale examples showed no token savings
• →"+34% palace boost" — Compares unfiltered to filtered search. Real but not a novel technique — standard ChromaDB metadata filtering
• →"100% with Haiku rerank" — Real result, but the rerank pipeline wasn't in the public benchmark scripts
• →Contradiction detection — Exists as fact_checker.py but not yet wired into knowledge graph operations

What's Real

• →96.6% LongMemEval — Raw mode, 500 questions, independently reproduced
• →Local, free, no cloud — Actually runs entirely on your machine
• →Palace architecture — Real and useful for retrieval, even if the boost is standard filtering
• →19 MCP tools — Functional and well-documented

Who Should Use MemPalace?

Ideal Users

• →Solo developers managing multiple projects who lose context between sessions
• →Team leads who need to recall what decisions were made and by whom
• →Heavy AI users (Claude, ChatGPT, Cursor) who generate thousands of conversations
• →Privacy-conscious organizations that can't send data to cloud memory services

Not Ideal For

• →Casual AI users who have a few conversations per week — the setup overhead isn't justified
• →Teams needing real-time collaboration — MemPalace is local to each machine
• →Windows users — Some issues reported with macOS ARM64; Windows support is less tested (early days)

Conclusion

MemPalace proves that AI memory doesn't need to be expensive, cloud-dependent, or lossy. By storing everything raw and making it navigable through the palace architecture, it achieves the highest recall scores ever published — for free.

The project is three days old. It has rough edges, overstated initial claims, and open issues. But the core approach — verbatim storage, structured navigation, local-first — is sound, the benchmark results are independently verified, and the team is fixing problems in real-time.

If you use AI daily and have ever wished it could remember what you discussed last month, MemPalace is worth 5 minutes of setup. Your future self — the one looking for "why did we choose Postgres?" six months from now — will thank you.

GitHub: github.com/milla-jovovich/mempalace