クロードコードの永続的、検索可能なプロジェクトメモリ。 各プロジェクトには、決定、ルール、アーキテクチャのメモ、スプリントのゴール、ベクトルデータベースに保存されているすべてのもの、新しいセッションを開始するたびに自動的にロードされます。

この問題を解決する問題は? Claudeは、セッション間ですべてを忘れます。 同じことを何度も再説明し終え、コンテキストウィンドウが埋め込まれると、ルールが逃れ、過去の決定が失われ、機械の切り替えはゼロから始まります。 このMCPは、再起動、コンテキストオーバーフロー、チームハンドオフを存続する、実際のメモリをClaudeを与えます。

お問い合わせ

プレーン英語

###このプロジェクトは実際に何をしますか?

プロジェクトごとのClaudeの永久的な記憶を与えます 各プロジェクトごとに別々の脳として考える。

何かに取り組んでいるときは、決定書(「PostgreSQL」を選択)、ルール(「コミット前のテストを実行する」)を作成し、スプリントを計画します。 通常、新しいセッションが始まると、そのすべてがforgottenです、またはClaudeが毎回再読わなければならない[[.md]ファイルを渡して散布します。

このMCPを使って:

• 決定を下す場合 → クラウドは自動的に保存します

SMG Claude Memory MCP

Persistent, searchable project memory for Claude Code. Each project has its own brain — decisions, rules, architecture notes, sprint goals — all stored locally in a vector database and automatically loaded every time you start a new session.

What problem does this solve? Claude forgets everything between sessions. You end up re-explaining the same things over and over, rules get missed, past decisions get lost when your context window fills up, and switching machines means starting from scratch. This MCP gives Claude a real memory — one that survives restarts, context overflows, and team handoffs.

---

In Plain English

What does this project actually do?

It gives Claude permanent memory per project. Think of it as a separate brain for each of your projects.

When you’re working on something, you make decisions (“we chose PostgreSQL”), set rules (“always run tests before commits”), and plan sprints. Normally, all of that is forgotten when a new session starts, or gets scattered across .md files that Claude has to re-read every time.

With this MCP:

• When you make a decision → Claude stores it automatically
• When you ask about something → Claude searches memory first, then answers
• When you start a new session → All the important stuff loads automatically
• When you set a rule (“always do X”) → Claude won’t forget it again

Three things users should understand

1. Semantic search — Ask “what database did we pick?” and it finds the PostgreSQL decision, even if you never typed “PostgreSQL” in your query. It searches by meaning, not keywords.

2. Project isolation — Every project has its own separate memory database. Memories from project-A never leak into project-B.

3. Team collaboration — You can move a project’s memory into the project folder, commit it to git, and your teammates get the same memory after git pull.

The technical one-liner

“An MCP server for Claude Code that stores per-project memory in local DuckDB with vector embeddings. It remembers decisions, rules, and sprint notes, retrieves them via semantic search, and auto-loads full context at session start — so Claude never forgets anything.”

What you’ll feel day-to-day

• You won’t need to re-explain your project’s decisions every session
• Rules you’ve set stick — Claude can’t skip them (enforced by hooks)
• Context window overflows don’t lose important info (it’s in the DB)
• Switching machines? git pull + one command, and Claude picks up exactly where you left off
• Onboarding a teammate’s Claude? Same thing — they get your whole project memory instantly

---

FAQ — Common Questions, Clear Answers

Q: When I run make_portable, does it move ALL projects’ memory to git, or just the one I’m working on?

Just the one project. Other projects are never touched.

Each project has its own separate .duckdb file:

~/.memory-mcp/