Memory Mcp

memory-mcp

Persistent memory + automatic git snapshots for Claude Code. Never lose context. Never lose code.

Why memory-mcp?

What makes it different

- Git Snapshots — Every memory save commits your entire project. Roll back anytime.
- Two-Tier Memory — CLAUDE.md loads instantly, deep store searchable mid-conversation.
- LLM-Powered — Haiku extracts what matters, consolidates duplicates, prunes stale info.
- Visual Dashboard — See your context: tokens, memories by type, snapshot history.
- Zero friction — No commands to run. It just works silently.

Quick Start

That's it. Start coding. Memories accumulate automatically.

How It Works

Two-tier memory architecture:

Silent capture via hooks:

Claude Code hooks fire after every response (Stop), before context compaction (PreCompact), and at session end (SessionEnd). A fast LLM (Haiku) reads the transcript and extracts:

- Architecture — how the system is structured
- Decisions — why X was chosen over Y
- Patterns — conventions and how things are done
- Gotchas — non-obvious pitfalls
- Progress — what's done, what's in flight
- Context — business context, deadlines, preferences

Smart memory management:

- Jaccard similarity deduplication (no duplicate memories)
- Confidence decay (progress fades after 7 days, context after 30)
- LLM-powered consolidation (merges overlapping memories, prunes stale ones)
- Line-budgeted CLAUDE.md (stays under ~150 lines, most important first)

Updating

To update an existing installation:

To update hooks (e.g., after a bug fix):

Requirements

- Claude Code CLI
- Node.js 18+
- Anthropic API key (for the Haiku-based extractor, ~$0.001 per extraction)

CLI Commands

Context Dashboard

Visualize your memory usage with memory-mcp context:

Use memory-mcp context --html to generate an…