NoteStore Lab MCP

notes-recover

your Apple Notes never really die

What You Get • Install • How It Work • Ecosystem

---

notes-recover is a forensic-grade reader for Apple Notes. Recover deleted notes, browse the raw NoteStore, and ship audit-ready bundles. Nothing leaves your machine.

🤝 Sister repo: want a prevention-side workflow that schedules backups before notes go missing? See notebackup — the Apple Notes backup control room (path-aware exports, launchd scheduling, health checks). notebackup covers the before; notes-recover covers the after. Together they cover the full Apple Notes lifecycle on macOS.

┌──────────────────────────────────────┐
│  LOCAL-FIRST          ████████ 100%  │
│  SOURCE-TRACEABLE     ████████ 100%  │
│  TYPING REQUIRED      ░░░░░░░░   0%  │
│  VIBES                ████████ ZERO  │
│                                FILLER│
└──────────────────────────────────────┘

Recover, browse, prove. NoteStore is just SQLite if you know where to look.

What You Get

Surface	What
notes-recovery cli	Walk NoteStore.sqlite. Recover trashed and orphan notes.
case review skill	Bounded Q&A over a single case root, no hallucinations.
agent plugins	Drop-in for Claude, Codex, OpenClaw — case in, summary out.
proof bundle	Every claim ships with the path, hash, and snippet.

Important

Local-first by default. No silent telemetry. No cloud round-trip. Your data stays on your machine until you explicitly ship it somewhere.

Install

git clone https://github.com/xiaojiou176-open/notes-recover.git
cd notes-recover
# follow the per-stack quickstart in INSTALL.md or docs/

Three commands. No curl | sh. No login. Read what you run.

Install break? Open your favorite agent and say "Read AGENTS.md and bootstrap notes-recover for me." Agent fix own brain. Long version: docs/.

How It Work

The repo is seven layers — exactly the seven commits in git log. New work goes in as small named PRs. No 50-file mystery commits.

Layer	What
chore: scaffold	License, governance, hygiene gates, CI scaffolding.
feat(core)	The primary engine. The reason notes-recover exists.
feat(modules)	Packages, adapters, services, plugins. The second floor.
feat(contracts)	Schemas, configs, public boundaries. Other code talks here.
test:	Receipts. Everything in this layer must run.
feat(ops)	Scripts, infra, CI helpers, build glue.
docs:	Public docs surface. The pretty face.

git log reads like a building floor plan. Look once, know the whole shape.

Ecosystem

notes-recover lives in the yard family: seven yards. one philosophy: structured input, structured output, structured proof.

Repo	What
switchyard	model & agent runtime switch board
browserclickyard	your AI clicks, your browser obeys
notes-recover (you here)	your Apple Notes never really die
dealyard	let prices fight, you sit and watch
docyard	docs site in, markdown out, no scraping by hand
fileyard	messy folders in, organized library out
proofyard	every claim ships with its receipt

Cross-family taste: BeamMe · BrewMe · OpenVibeCoding · proofyard.

Star This Repo

If notes-recover saves you a click, an hour, or a headache — star costs zero. Fair trade. ⭐

Also by Yifeng[Terry] Yu

• switchyard — model & agent runtime switch board
• browserclickyard — your AI clicks, your browser obeys
• BeamMe — beam your agent config to any planet
• BrewMe — wake up, news already brewed
• OpenVibeCoding — AI codes overnight, you ship in the morning

License

MIT — small print, big freedom.