Memory MCP

Name: Memory MCP
Author: yuvalsuede

作者：yuvalsuede版本 1.2.1i★ –i在你的电脑上运行

注册名称io.github.yuvalsuede/memory-mcp

安装

概览

作者提供的说明（英文原文）

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

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 搜索与 AI 记忆

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
注册中心没有列出需要填写的密钥。

你需要

npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "memory": {
      "command": "npx",
      "args": [
        "-y",
        "claude-code-memory"
      ]
    }
  }
}

在终端中运行这条命令

claude mcp add memory -- npx -y claude-code-memory

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "memory": {
      "command": "npx",
      "args": [
        "-y",
        "claude-code-memory"
      ]
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "memory": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "claude-code-memory"
      ]
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 yuvalsuede 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“搜索与 AI 记忆”中的其他服务器比较i

星标数多于此分类中其他 7256 个服务器的 0%
发布到注册中心的时间比此分类中其他 7256 个服务器的 2% 更新
基础检查结果等于或优于此分类中其他 7256 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Memory MCP 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（1.2.1）于9个月前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它？

同一分类中有：Context7, Codebase Memory, Exa

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Context7

作者：upstash

Up-to-date docs for AI agents

电脑或云端★ 64,224MIT今天更新

安装

Codebase Memory

作者：DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

在你的电脑上运行★ 48,148MIT20天前更新

安装

Exa

作者：exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

在云端运行★ 5,213MIT上个月更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

memory-mcp

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?

Problem	Solution
Re-explaining your project every session	Auto-captures decisions, patterns, architecture
Context window fills up, knowledge lost	Two-tier memory: CLAUDE.md (instant) + deep search
Broke something, can't remember what worked	Git snapshots on every save, instant rollback
No idea what Claude "knows" about your project	Visual dashboard shows all context
Worried about cloud storage	100% 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

# Install globally

npm install -g claude-code-memory

Interactive setup (API key + hooks)

memory-mcp setup

Initialize a project

memory-mcp init ~/Projects/my-app

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

How It Works

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

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:

Layer	Purpose	Size
`CLAUDE.md`	Auto-read on session start. Top ~150 lines of the most important context.	Compact
`.memory/state.json`	Full 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:

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

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

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 setup

memory-mcp init [dir] Initialize memory for a project memory-mcp status [dir] Show memory status and health memory-mcp statusline [dir] Compact one-line status (great for shell prompts) memory-mcp context [dir] Show context metrics and token usage memory-mcp context --html Generate visual HTML dashboard memory-mcp search Search memories by keyword memory-mcp ask Ask a question, get answer from memory memory-mcp consolidate [dir] Merge duplicates, prune stale memories memory-mcp key [api-key] Set or check Anthropic API key memory-mcp snapshots [dir] List git snapshot history memory-mcp snapshot-enable Enable automatic git snapshots memory-mcp snapshot-disable Disable git snapshots memory-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.

# Enable during init (you'll be prompted)

memory-mcp init ~/Projects/my-app

Or enable later

memory-mcp snapshot-enable

View snapshot history

memory-mcp snapshots

Compare two snapshots

memory-mcp snapshot-diff abc123 def456

Restore to a previous state

memory-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:

Tool	Description
`memory_search`	Keyword search across all memories
`memory_related`	Get memories by tag or area
`memory_ask`	Ask a question, get an LLM-synthesized answer from memory
`memory_save`	Manually save a memory
`memory_recall`	List all memories with filters
`memory_delete`	Remove a memory
`memory_consolidate`	Trigger memory consolidation
`memory_consciousness`	Generate the full consciousness document
`memory_stats`	Show memory statistics
`memory_init`	Set 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:

<!-- MEMORY:START -->

MyProject

A 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._

Global vs Per-Project Install

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

memory-mcp setup  # select "global" when prompted

Per-project: hooks and MCP configured per project.

memory-mcp init /path/to/project

Configuration

API key is resolved in order:

ANTHROPIC_API_KEY environment variable
~/.memory-mcp/config.json
~/.config/anthropic/api_key
~/.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