Anamnesis MCP server

Anamnesis

Cross-machine memory for Claude Code

Website · Docs · Benchmark · Dashboard

uv tool install anamnesis-memory && anamnesis init

ἀνάμνησις (anamnesis): Greek for recollection, the act of calling knowledge back to mind.

Anamnesis is a local-first, file-based memory layer for Claude Code that syncs across your own machines. What Claude learns about your projects (conventions, architecture decisions, fixes that worked, what you did yesterday) is stored as plain markdown, indexed locally for search, and kept in sync over your private network.

Claude Code's own memory stays on the machine where it was written. Copying a SQLite index through a cloud folder such as Dropbox or iCloud corrupts it. Anamnesis syncs the markdown with git instead and rebuilds the index on each machine, so a note written on your desktop is searchable from your laptop.

No cloud account is required. The memory stays on your machines, version-controlled and human-readable.

How it works

┌─────────────┐        git over your private mesh        ┌─────────────┐
  │  desktop    │  ◄────────────  (Tailscale)  ────────►   │  laptop     │
  │             │                                          │             │
  │  Claude Code│                                          │  Claude Code│
  │     ▼       │                                          │     ▼       │
  │  MCP server │   markdown (source of truth)             │  MCP server │
  │     ▼       │   + SQLite FTS index (rebuilt locally)   │     ▼       │
  │ ~/.anamnesis│                                          │ ~/.anamnesis│
  └─────────────┘                                          └─────────────┘

The markdown is the source of truth; everything else is derived from it.

• Files first. Each note is a markdown file under ~/.anamnesis/memory/, readable and git diff-able.

synced. On the project's eval set, keyword search reaches about 94% recall, so there is no vector store until measurements call for one.

• A local index. A SQLite FTS5 index gives keyword (BM25) recall. It is rebuilt locally and is not

mesh, or any git remote you control. Only the markdown travels; each machine rebuilds its own index, so the database file is not copied between machines. If two machines edit the same note, sync reports a git conflict instead of dropping either side.

• Sync over git. The markdown is a git repo synced over your private Tailscale

SessionStart injects the relevant notes, and SessionEnd captures a summary of the session and syncs it.

• Claude Code integration. An MCP server exposes read-only query tools, and session hooks do the rest:

distills session notes into durable notes, and anamnesis merge consolidates near-duplicates. Generated notes carry provenance and confidence in their front-matter. merge --apply is gated on your eval set so it does not lower recall, and anamnesis eval measures reflection before and after on a sandbox copy.

• Reflection and merge. An optional reflection pass (any OpenAI-compatible model, set in config)

machine.

• A dashboard. A web GUI to browse, search, edit, and read the history of your memory across every

Quickstart

Shortened. The full README is on GitHub.