Memory Mcp

io.github.yuvalsuedePublished by GitHub account yuvalsuedev1.2.1Updated Oct 24, 2026

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

The publisher's own server: Memory.fit

VerifiedSTDIODesktop onlyKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Local MCP server that gives Claude Code persistent project memory and automatic git snapshots, so context and code survive across sessions.

What you can do
Search, recall and filter stored project memories by keyword, tag or area, and ask questions answered from memory by an LLM synthesis step. Save, delete and consolidate memories, and generate a full consciousness document plus memory statistics. Initialize a project's memory store with a name and description. Manage git snapshots of the whole project: list history, compare snapshots and restore a previous state. Show context metrics and token usage, optionally as an HTML dashboard.
When to use it
Useful for long-running Claude Code projects where you keep re-explaining architecture, decisions and conventions, or where you want a rollback point tied to each working session. Best suited to developers who already work in git repositories and want memory kept entirely in local files.
Requirements
Runs locally via npx from the npm package claude-code-memory. Needs Claude Code CLI and Node.js 18 or newer. Requires an Anthropic API key for the Haiku-based extractor, resolved from the ANTHROPIC_API_KEY environment variable or local config files. Setup installs Claude Code hooks and writes project files such as CLAUDE.md, .memory/state.json and .mcp.json.
Before you install
The extractor sends session transcript content to Anthropic's Haiku model, so conversation data leaves your machine. Extraction and consolidation incur small API charges, roughly a few cents per day of coding. Every memory save commits the entire project to a hidden branch, and optional remote push can publish that history. Memories and snapshots can be deleted or restored, so review before enabling snapshots on important repositories.

Installation

In SourceWeft

  1. Open Memory Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

memory-mcp

[npm version] [npm downloads] [License: MIT] [Node] [TypeScript]

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

🧠 45 memories | 📊 2.8K tokens | 📸 23 snapshots | ⏱️ 5m ago

Why memory-mcp?

ProblemSolution
Re-explaining your project every sessionAuto-captures decisions, patterns, architecture
Context window fills up, knowledge lostTwo-tier memory: CLAUDE.md (instant) + deep search
Broke something, can't remember what workedGit snapshots on every save, instant rollback
No idea what Claude "knows" about your projectVisual dashboard shows all context
Worried about cloud storage100% local files, your git repo

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

bash
# Install globallynpm install -g claude-code-memory
# Interactive setup (API key + hooks)memory-mcp setup
# Initialize a projectmemory-mcp init ~/Projects/my-app

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

How It Works

mermaid
graph TB    subgraph "Phase 1: Silent Capture"        A[Claude Code Session] -->|User sends message| B[Claude responds]        B -->|Hook fires: Stop/PreCompact/SessionEnd| C[extractor.js]        C --> D[Read transcript from cursor]        D --> E[Chunk if >6000 chars]        E --> F[Send to Haiku LLM]        F -->|Extract memories as JSON| G[Dedup via Jaccard similarity]        G --> H[Save to .memory/state.json]        H --> I[Decay confidence scores]        I --> J{Consolidation needed?}        J -->|>80 memories or every 10 extractions| K[Haiku merges/drops]        J -->|No| L[Sync CLAUDE.md]        K --> L    end
    subgraph "Phase 2: Recovery"        M[New session starts] -->|Built-in behavior| N[Claude reads CLAUDE.md]        N --> O[Claude has full project context]    end
    subgraph "Phase 3: Deep Recall"        O --> P{Need specific context?}        P -->|memory_search| Q[Keyword search across memories]        P -->|memory_ask| R[Haiku synthesizes answer from top 30 matches]        P -->|memory_related| S[Tag-based retrieval]    end
    subgraph "Data Store"        H -.-> T[(.memory/state.json<br/>Full memory store)]        L -.-> U[(CLAUDE.md<br/>~150 line summary)]        T -.->|MCP tools read| Q        T -.->|MCP tools read| R        T -.->|MCP tools read| S    end
    style A fill:#4a9eff,color:#fff    style F fill:#ff6b6b,color:#fff    style K fill:#ff6b6b,color:#fff    style R fill:#ff6b6b,color:#fff    style T fill:#ffd93d,color:#000    style U fill:#6bcb77,color:#000

Two-tier memory architecture:

LayerPurposeSize
CLAUDE.mdAuto-read on session start. Top ~150 lines of the most important context.Compact
.memory/state.jsonFull memory store. Searchable via MCP tools mid-conversation.Unlimited

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:

bash
npm install -g claude-code-memory --force

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

bash
memory-mcp setup

Requirements

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

CLI Commands

memory-mcp setup              Interactive first-time setupmemory-mcp init [dir]          Initialize memory for a projectmemory-mcp status [dir]        Show memory status and healthmemory-mcp statusline [dir]    Compact one-line status (great for shell prompts)memory-mcp context [dir]       Show context metrics and token usagememory-mcp context --html      Generate visual HTML dashboardmemory-mcp search <query>      Search memories by keywordmemory-mcp ask <question>      Ask a question, get answer from memorymemory-mcp consolidate [dir]   Merge duplicates, prune stale memoriesmemory-mcp key [api-key]       Set or check Anthropic API keymemory-mcp snapshots [dir]     List git snapshot historymemory-mcp snapshot-enable     Enable automatic git snapshotsmemory-mcp snapshot-disable    Disable git snapshotsmemory-mcp help                Show help

Context Dashboard

Visualize your memory usage with memory-mcp context:

Context Dashboard
  Project: my-app
  Total Context  2.8K estimated tokens
  Tier 1 CLAUDE.md (auto-loaded)  █████████████████░░░░░░░░░░░░░ 1.0K  45 lines, 44 in memory block
  Tier 2 .memory/state.json (searchable)  ██████████████████████████████ 1.8K  29 active, 5 archived, 24 superseded
  Memories by Type  architecture ███░░░░░░░░░░░░░░░░░   8 memories (291 tokens)  decision     ██████░░░░░░░░░░░░░░  18 memories (540 tokens)  gotcha       ████░░░░░░░░░░░░░░░░  10 memories (332 tokens)  progress     ██████░░░░░░░░░░░░░░  19 memories (538 tokens)
  Git Snapshots  ● Enabled on __memory-snapshots  42 commits → origin

Use memory-mcp context --html to generate an interactive browser dashboard.

Git Snapshots

Automatic project versioning tied to your working sessions. Every memory extraction commits your entire project to a hidden branch.

bash
# Enable during init (you'll be prompted)memory-mcp init ~/Projects/my-app
# Or enable latermemory-mcp snapshot-enable
# View snapshot historymemory-mcp snapshots
# Compare two snapshotsmemory-mcp snapshot-diff abc123 def456
# Restore to a previous statememory-mcp snapshot-restore abc123
# Disable (preserves existing snapshots)memory-mcp snapshot-disable

How it works:

  • Commits go to __memory-snapshots branch (invisible in normal workflow)
  • Optional push to remote (e.g., origin)
  • Commit messages include what memories were extracted
  • Full project state captured, not just memory files

Use cases:

  • Roll back after breaking changes
  • See what your project looked like during a specific session
  • Track project evolution alongside context evolution

MCP Tools (used by Claude mid-conversation)

When configured as an MCP server, Claude can access these tools during a session:

ToolDescription
memory_searchKeyword search across all memories
memory_relatedGet memories by tag or area
memory_askAsk a question, get an LLM-synthesized answer from memory
memory_saveManually save a memory
memory_recallList all memories with filters
memory_deleteRemove a memory
memory_consolidateTrigger memory consolidation
memory_consciousnessGenerate the full consciousness document
memory_statsShow memory statistics
memory_initSet project name and description

What Gets Stored

Memories are categorized into six types:

architecture   "Next.js 14 app router with Supabase backend, Stripe for billing"decision       "Chose server components for public pages because of SEO requirements"pattern        "All API routes validate input with zod and return NextResponse"gotcha         "Supabase RLS policy on word_lists requires user_id OR org_id, not both"progress       "Auth complete, billing webhook handling in progress"context        "Client wants launch by March, focus on core features only"

File Structure

After initialization, your project gets:

your-project/├── CLAUDE.md              ← auto-updated memory summary (read on session start)├── .memory/│   ├── state.json         ← full memory store│   └── cursor.json        ← tracks what's been processed├── .mcp.json              ← MCP server configuration└── .claude/    └── settings.json      ← hook configuration

CLAUDE.md Format

The memory block is inserted between markers, preserving any existing CLAUDE.md content:

markdown
<!-- MEMORY:START --># MyProjectA brief description
_Last updated: 2026-01-27 | 45 active memories, 62 total_
## Architecture- Next.js 14 app router with Supabase backend- Auth via NextAuth with Google and email providers
## Key Decisions- Chose server components for SEO pages- Using Supabase RLS instead of API-level auth
## Patterns & Conventions- All API routes use zod validation- Tailwind only, no CSS modules
## Gotchas & Pitfalls- RLS policy requires user_id OR org_id, not both
## Current Progress- Auth: complete- Billing: in progress
## Context- Launch target: March
_For deeper context, use memory_search, memory_related, or memory_ask tools._<!-- MEMORY:END -->

Global vs Per-Project Install

Global (recommended): hooks work for all projects automatically.

bash
memory-mcp setup  # select "global" when prompted

Per-project: hooks and MCP configured per project.

bash
memory-mcp init /path/to/project

Configuration

API key is resolved in order:

  1. ANTHROPIC_API_KEY environment variable
  2. ~/.memory-mcp/config.json
  3. ~/.config/anthropic/api_key
  4. ~/.anthropic/api_key

Cost

The extractor uses Claude Haiku for memory extraction and consolidation. Typical cost:

  • ~$0.001 per extraction (after each Claude response)
  • ~$0.005 per consolidation (every ~10 extractions)
  • A full day of coding: ~$0.05–0.10

License

MIT

Source: README.md at commit c434710

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.2.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Memory integrations

Memory.fit

fit.memoryOfficial publisher

Hosted Memory.fit server that lets an AI read your training, sleep, recovery and nutrition data and write back weekly plans, targets and meal plans.

Streamable HTTPWeb executableAuth
Location & LifestyleCredential requiredOct 29, 2026

pg.ddx.io: the PostgreSQL community's memory

io.ddx.pgOfficial publisher

pg.ddx.io: the PostgreSQL community's memory's hosted MCP server, published by pg.ddx.io; no sign-in required; Streamable HTTP; 29 tools.

Streamable HTTPWeb executable
Databases29 toolsOct 24, 2026

var.gg Naming Memory

gg.varOfficial publisher

Remote MCP server that suggests and searches code identifier names from domain concepts in Korean, Japanese, Chinese, Vietnamese and English, and exposes ERD…

Streamable HTTPWeb executable
Databases7 toolsOct 27, 2026

Counterparts

ai.counterparts

Local-first long-term memory for Claude Code and Claude Desktop: the assistant writes notes about you and your projects and recalls them in later sessions.

STDIODesktop only
AI & MLNot validated yetNov 7, 2026

LAHZE - Persian AI Memory Platform

Published by GitHub account pedramgholizadeh

LAHZE - Persian AI Memory Platform's hosted MCP server; no sign-in required; Streamable HTTP; 13 tools.

Streamable HTTPWeb executable
Location & Lifestyle13 toolsNov 3, 2026