** Claude Code의 검색 가능한 프로젝트 메모리.** 각 프로젝트에는 자체 두뇌가 있습니다. 결정, 규칙, 건축 노트, 스프린트 목표 - 벡터 데이터베이스에 저장된 모든 로컬로 새로운 세션을 시작할 때마다 자동으로로드됩니다.

**이 문제를 해결합니까? ** Claude는 세션 간의 모든 것을 잊습니다. 당신은 위에 동일한 것들을 다시 설명하고, 규칙은 놓쳤다, 과거 결정은 당신의 컨텍스트 창이 위로 채우고, 전환 기계는 처음부터 시작을 의미합니다. 이 MCP는 실제 메모리를 부여합니다. 재시작, 컨텍스트 오버플로우 및 팀 핸드오프를 살아가는 것.

---

일반 영어

이 프로젝트는 실제로 무엇을 합니까?

** 프로젝트 당 Claude 영구 메모리를 제공합니다. ** 각 프로젝트에 대해 별도의 두뇌로 생각하십시오.

뭔가 작업 할 때, 당신은 결정 ( “우리는 PostgreSQL을 선택했습니다”), 설정 규칙 (“직원 전에 테스트 실행”), 및 계획 스프린트. 일반적으로, 그 중 모든 forgotten 때 새로운 세션 시작, or get scattered throughout .md] Claude have to re-read every time.

이 MCP로:

• **결정을 할 때 ** → Claude는 자동으로 저장

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/