Skip to main content
ClaudeWave

Shared, git-tracked memory for AI agents on the same codebase. What one Claude/Cursor/Cline learns, the next one picks up. No DB, no SaaS — just files in your repo. CLI + MCP server.

MCP ServersOfficial Registry1 stars0 forksPythonMITUpdated today
ClaudeWave Trust Score
95/100
Verified
Passed
  • Open-source license (MIT)
  • Actively maintained (<30d)
  • Clear description
  • Topics declared
  • Documented (README)
Last scanned: 8/27/2026
Install in Claude Code / Claude Desktop
Method: UVX (Python) · repo-memory-mcp
Claude Code CLI
claude mcp add repo-memory -- uvx repo-memory-mcp
claude_desktop_config.json (Claude Desktop)
{
  "mcpServers": {
    "repo-memory": {
      "command": "uvx",
      "args": ["repo-memory-mcp"]
    }
  }
}
1. Run the command above in your terminal (Claude Code), or paste the JSON config into claude_desktop_config.json (Claude Desktop).
2. Replace any <placeholder> values with your API keys or paths.
3. Restart Claude. The MCP server and its tools appear automatically.
Use cases

MCP Servers overview

<!--
mcp-name: io.github.yubinkim444/repo-memory
-->

# repo-memory

> **Shared, git-tracked working memory for AI agents that share a codebase.**
> What one Claude / Cursor / Cline learns about your repo, the next one
> picks up automatically. No database. No SaaS. Just files in your repo.

[![PyPI](https://img.shields.io/pypi/v/repo-memory-mcp)](https://pypi.org/project/repo-memory-mcp/)
[![Python](https://img.shields.io/badge/python-3.10%2B-blue)]()
[![MCP](https://img.shields.io/badge/MCP-server-7c3aed)]()
[![License: MIT](https://img.shields.io/badge/license-MIT-green)]()

---

## The problem

Every AI session that touches your repo starts from zero. It re-greps the
same files. It re-discovers the same conventions. It re-asks the same
questions you already answered three sessions ago. Multi-user / multi-tool
makes it worse: your teammate's Cursor and your Claude Code learn the same
codebase independently.

There is `CLAUDE.md` / `.cursorrules` for **rules** the human writes. But
there is nothing for **facts** an agent verified — "the auth middleware
lives at `src/auth/middleware.py:42`", "PR #387 chose httpx over requests
because of HTTP/2", "don't run migrations during peak hours".

`repo-memory` is that nothing. A `.ai-memory/` directory you commit to
your repo. Every AI tool reads from it, writes to it. Git is the database.

---

## Layout

```
your-repo/
├── .ai-memory/
│   ├── README.md           # explains the convention
│   ├── facts.jsonl         # append-only structured facts with evidence
│   ├── decisions/          # one markdown per non-trivial decision
│   │   └── 2026-05-19-pick-httpx.md
│   └── gotchas.md          # one-line "watch out for X" notes
├── src/
└── README.md
```

Pure files. Sync over git. No daemon, no DB, no auth. Works offline.

---

## Install

```bash
pip install repo-memory-mcp
# or
uvx repo-memory-mcp --help
```

Python ≥3.10. Depends only on the official `mcp` SDK (for the MCP server).

---

## Quick start

```bash
cd your-repo
repo-memory init                              # creates .ai-memory/ + adds CLAUDE.md hint
repo-memory add-fact "Auth middleware lives in src/auth/middleware.py" \
                     --file src/auth/middleware.py --lines 42-180 --tool grep
repo-memory add-decision "Use httpx not requests" \
                         --body "HTTP/2 + async support; we already use anyio."
repo-memory add-gotcha "Don't run migrations during 9-11am UTC peak"

repo-memory show                              # render everything as Markdown
repo-memory list-facts --tag auth
```

Then commit `.ai-memory/` like any other file:

```bash
git add .ai-memory/
git commit -m "memory: record auth middleware location + httpx decision"
git push
```

Anyone else (human or AI) who pulls the repo now sees those facts/decisions
immediately.

---

## LLM & AI Agent Readable Specification

> **For agents discovering this repo through search or MCP indexing.**

### Identity
- **name**: `repo-memory`
- **purpose**: read/write a structured, git-tracked memory store about the
  current codebase so multiple AI agents (and humans) don't re-learn it.
- **transport**: CLI (`repo-memory`) and MCP stdio (`repo-memory-mcp`).
- **storage**: plain files under `.ai-memory/` in the repo. Sync = git.

### When to call which tool

| Tool | When |
|------|------|
| `get_repo_memory` | At the **start** of any task on this repo. |
| `add_fact` | After you verify a non-obvious fact (location, behavior, convention). Include `evidence` so the next agent can re-verify cheaply. |
| `add_decision` | After a non-trivial choice (architecture, library, trade-off). Body should explain *why*, not just *what*. |
| `add_gotcha` | After a surprise that wasted your time. |
| `list_facts` | When you want only facts in a specific area (`tag`, `source_file`). |

### Recommended agent workflow

```
1. agent.call("get_repo_memory")            -> absorb prior context
2. ...do task, run tools, verify things...
3. agent.call("add_fact", claim, evidence)  -> for each new fact
4. agent.call("add_decision", title, body)  -> if a choice was made
5. session ends, human commits .ai-memory/   -> shared via git
```

### MCP server install

Add to your client config (Claude Desktop / Cursor / Cline):

```json
{
  "mcpServers": {
    "repo-memory": {
      "command": "uvx",
      "args": ["repo-memory-mcp", "--repo", "/abs/path/to/the/repo"]
    }
  }
}
```

Or set `REPO_MEMORY_ROOT` env var instead of `--repo`.

Exposes 5 tools: `get_repo_memory`, `add_fact`, `list_facts`,
`add_decision`, `add_gotcha`.

---

## Why git, not a database

- **Zero infra.** No service to host, no account to create, no API key
  to rotate.
- **Already authoritative.** Git history is the single source of truth.
  `git blame` tells you which agent added which fact and when.
- **Works offline.** Plane, train, conference WiFi — all fine.
- **PR review.** Suspicious or wrong facts get filtered through normal
  code review.
- **Per-repo scope.** A fact about repo A doesn't leak into repo B; the
  store is local to the repo.

---

## Schema (for tooling authors)

`facts.jsonl` — one JSON object per line:

```json
{
  "id": "abc123def456",
  "ts": "2026-05-19T18:00:00Z",
  "claim": "Auth middleware lives in src/auth/middleware.py",
  "evidence": {
    "file": "src/auth/middleware.py",
    "lines": "42-180",
    "tool": "grep",
    "command": "rg 'def authenticate' src/",
    "verified_at": "2026-05-19T18:00:00Z"
  },
  "tags": ["auth"],
  "added_by": "claude-opus-4.7"
}
```

Append-only. Stale entries stay. Readers consult `verified_at` and
re-verify if they want.

---

## Automatic discovery hint

`repo-memory init` also appends a short discoverability section to your
repo's `CLAUDE.md` (or `AGENTS.md` if you already have one) telling any
AI agent that enters the repo to check `.ai-memory/` first and to record
new findings back into it. Idempotent — re-running won't duplicate.

Opt out with `--no-claude-md`.

The appended block is delimited by `<!-- BEGIN: repo-memory -->` and
`<!-- END: repo-memory -->`, so you can hand-edit other parts of your
`CLAUDE.md` freely.

---

## CLI reference

| Command | Effect |
|---------|--------|
| `repo-memory init [--no-claude-md]` | Create `.ai-memory/` skeleton + (default) update CLAUDE.md/AGENTS.md. |
| `repo-memory show [--limit N]` | Print everything as one Markdown doc. |
| `repo-memory add-fact "<claim>" [--file F --lines L --tool T --command C --tag T --by AGENT]` | Append a fact. |
| `repo-memory list-facts [--tag T] [--source-file F] [--since ISO] [--limit N] [--json]` | List/filter facts. |
| `repo-memory add-decision "<title>" [--body MD]` | Write a decision file. |
| `repo-memory list-decisions` | List decision file paths. |
| `repo-memory add-gotcha "<note>"` | Append a one-line gotcha. |

All commands take `--root PATH` if your CWD isn't the repo root.

---

## About the author

Built by [yubinkim444](https://github.com/yubinkim444), who also makes
**[Kay's Records](https://kay-s-record.web.app/get.html)** — an app for iOS
and Android.

If this project saved you time, giving the app a try is the nicest way to say
thanks.

## License

MIT © yubinkim444
ai-agentsclaudeclinecursordeveloper-toolsknowledge-basellmmcpmemory

What people ask about repo-memory

What is yubinkim444/repo-memory?

+

yubinkim444/repo-memory is mcp servers for the Claude AI ecosystem. Shared, git-tracked memory for AI agents on the same codebase. What one Claude/Cursor/Cline learns, the next one picks up. No DB, no SaaS — just files in your repo. CLI + MCP server. It has 1 GitHub stars and its last recorded update is dated 2026-08-26.

How do I install repo-memory?

+

You can install repo-memory by cloning the repository (https://github.com/yubinkim444/repo-memory) or following the README instructions on GitHub. ClaudeWave also provides quick install blocks on this page.

Is yubinkim444/repo-memory safe to use?

+

Our security agent has analyzed yubinkim444/repo-memory and assigned a Trust Score of 95/100 (tier: Verified). See the full breakdown of passed checks and flags on this page.

Who maintains yubinkim444/repo-memory?

+

yubinkim444/repo-memory is maintained by yubinkim444. The last recorded GitHub activity is dated 2026-08-26, with 0 open issues.

Are there alternatives to repo-memory?

+

Yes. On ClaudeWave you can browse similar mcp servers at /categories/mcp, sorted by popularity or recent activity.

Deploy repo-memory to your cloud

Ship this repo to production in minutes. Each platform spins up its own environment with editable env vars.

Maintain this repo? Add a badge to your README

Drop the badge into your GitHub README to show it's tracked on ClaudeWave. Each badge links back to this page and reflects the live Trust Score.

Featured on ClaudeWave: yubinkim444/repo-memory
[![Featured on ClaudeWave](https://claudewave.com/api/badge/yubinkim444-repo-memory)](https://claudewave.com/repo/yubinkim444-repo-memory)
<a href="https://claudewave.com/repo/yubinkim444-repo-memory"><img src="https://claudewave.com/api/badge/yubinkim444-repo-memory" alt="Featured on ClaudeWave: yubinkim444/repo-memory" width="320" height="64" /></a>

More MCP Servers

repo-memory alternatives