How is Repo Memory different from `CLAUDE.md` or `.cursorrules`?
`CLAUDE.md` is for rules that a human writes; Repo Memory is for facts that an agent verifies – locations, behaviors, and decisions discovered during work.
@yubinkim444
Basic information
A different approach from typical persistent-memory MCPs. Instead of a local
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"repo-memory": {
"command": "uvx",
"args": [
"repo-memory-mcp",
"--repo",
"/path/to/your/repo"
]
}
}
}Tool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
Fetch the live tool list by running this server in a temporary sandbox using the button above.
Repo Memory is a shared, git-tracked working memory for AI agents that share a codebase. It stores structured facts, decisions, and gotchas in plain files under a .ai-memory/ directory, synchronized via git. It is designed for developers using AI coding assistants such as Claude, Cursor, or Cline.
Install with pip install repo-memory or run via uvx. Initialize memory in your repo with repo-memory init, then use commands such as repo-memory add-fact, add-decision, or add-gotcha. For AI agent integration, add an MCP server entry in your client config pointing to repo-memory-mcp with the repo path.
CLAUDE.md or AGENTS.md`CLAUDE.md` is for rules that a human writes; Repo Memory is for facts that an agent verifies – locations, behaviors, and decisions discovered during work.
Python 3.10 or later. The only dependency is the official MCP SDK.
In a `.ai-memory/` directory inside the repository. The data is plain files (facts.jsonl, decisions/, gotchas.md) and is synchronized via normal git commits and pushes.
It uses stdio transport. The server is launched via `repo-memory-mcp` with a `--repo` argument or the `REPO_MEMORY_ROOT` environment variable.
Facts are append-only; stale entries remain. Readers check `verified_at` to re-verify if needed. Suspicious facts are filtered through normal code review via git.

Exact, shared memory for AI agents: a hierarchical database where totals always add up, every write is attributed to the agent and person behind it, and any figure traces back to its source file. Agents create databases,

Search published GPU deployment, rack integration and structured cabling resources; read canonical documents and Leviathan Systems company service scope. Anonymous, read-only Streamable HTTP MCP. No credentials required.

Serve your docs to AI agents over SSH and MCP. Agents use ls, cat, grep, find, and pipes against a virtual filesystem backed by your documentation. Identity-scoped access, governed writing with human approval, and portab

Search saved employee handbooks from your AI assistant. Four read-only tools list authorized handbooks, browse policies, search content, and read source pages with citation links. Uses scoped bearer tokens and Streamable

Ask your Takibi Base collections anything; get answers with cited passages and a support score.
Comments