← back to brunchlabs Card No. 04 · from the pantry

Anamnesis.

ἀνάμνησις/ a‑nam‑NEE‑sis / n.

1.a calling‑to‑mind; the soul's recovery of what it once knew. 2.your Obsidian vault, served to Claude as an MCP server.

Notes, transcripts, and recall — straight from your second brain, plated for any agent at the table.

§ I

In the pantry

five jars,
always stocked.

  1. 01 notes_search(query, …)

    Full‑text SQLite FTS5 across the vault, filterable by folder, tag, and date window. Like a pantry walk with a flashlight.

    returns · ranked excerpts & scores

  2. 02 notes_list(path?)

    Browse the vault folder structure one level at a time. Open a drawer, see what's there.

    returns · folders & files at that level

  3. 03 notes_recent(limit?, folder?)

    The freshest jars — whatever you've touched lately. Yesterday's meeting, this morning's idea.

    returns · most‑recently modified files

  4. 04 notes_read(path)

    Pull a single note off the shelf and read it whole — frontmatter, body, modified timestamp.

    returns · the note, in full

  5. 05 notes_write(path, content, message?)

    Create or update a note mid‑conversation. Every write is auto‑committed to git, so your vault keeps a real history — and the agent leaves the kitchen tidier than it found it.

    returns · path & commit status · guarded · path‑traversal blocked

§ II

A recall, traced

from disk
to dinner table.

Source
▤
Obsidian Vault
your filesystem
Stove
∾
Anamnesis
MCP server · stdio
Plate
⊛
Claude
or any MCP client

no copy, no API, no upload — your notes stay yours.

§ III

The recipe

two steps,
then it's hot.

★ Install ★ serves any MCP client
i.

Build it

Clone, install, build. Anamnesis is still a kitchen recipe — not yet on npm.

# ~/somewhere
git clone git@github.com:brunchlabs/anamnesis.git
cd anamnesis/server && npm install && npm run build
ii.

Wire it up

Drop this into your MCP config (~/.claude.json). Point VAULT_PATH at the Obsidian folder you want served.

// ~/.claude.json — mcpServers entry
{
  "anamnesis": {
    "command": "node",
    "args": ["/path/to/anamnesis/server/dist/index.js"],
    "env": {
      "VAULT_PATH": "/Users/you/Obsidian/MyVault"
    }
  }
}
iii.

Wake Claude

Restart Claude Code (or any MCP client). The five pantry tools — notes_search, notes_list, notes_recent, notes_read, notes_write — will be on the menu.

↳ still kitchen‑only — write us for early access & the npm tarball.

Ask for a taste →
§ IV

House specials

small choices,
big flavor.

  1. ★

    SQLite FTS5, off‑vault

    A full‑text index lives outside your vault so iCloud doesn't fight it. First boot indexes; subsequent boots are instant.

  2. ★

    Every write commits to git

    Agents that edit your notes leave receipts. simple-git auto‑commits on every notes_write, so you can git log what the kitchen did last night.

  3. ★

    Remote variant — cloud Claude, too

    An optional Cloudflare Worker (D1 + Vectorize + GitHub OAuth) serves the same vault to web‑based Claude. A launchd git pull/push daemon keeps the two stoves in sync.