NoteStore Lab MCP

io.github.xiaojiou176-openPublished by GitHub account xiaojiou176-openv0.1.0.post1Updated Oct 25, 2026

Local copy-first Apple Notes recovery and review MCP server for NoteStore Lab case roots.

VerifiedSTDIODesktop onlyFiles & StorageKnowledge & Memory

Overview

AI-generated overview

A local, copy-first MCP server for reading Apple Notes NoteStore data, recovering deleted notes, and producing audit-ready evidence bundles.

What you can do
Walk the Apple Notes NoteStore SQLite database and browse raw note data locally. Recover trashed and orphaned notes. Answer bounded questions over a single case root with source-traceable results. Produce proof bundles where each claim carries a path, hash and snippet.
When to use it
Useful on macOS when you need to inspect or recover Apple Notes content, or to assemble traceable evidence from a notes case without sending data to a cloud service.
Requirements
Runs as a local process on macOS (desktop only) from the apple-notes-forensics PyPI package. The README describes cloning the repository and following a per-stack quickstart; no login or API keys are declared.
Before you install
It reads local Apple Notes data, which is personal and sensitive; recovered notes and proof bundles may contain private content. The README states data stays on the machine until explicitly shipped elsewhere, so review where any exported bundle is sent. Installation instructions in the README involve cloning and running repository code.

Installation

In SourceWeft

  1. Open NoteStore Lab MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

[memo]

notes-recover

your Apple Notes never really die

[Stars] [Last Commit] [License]

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

SurfaceWhat
notes-recovery cliWalk NoteStore.sqlite. Recover trashed and orphan notes.
case review skillBounded Q&A over a single case root, no hallucinations.
agent pluginsDrop-in for Claude, Codex, OpenClaw — case in, summary out.
proof bundleEvery 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

bash
git clone https://github.com/xiaojiou176-open/notes-recover.gitcd 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.

LayerWhat
chore: scaffoldLicense, 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.

RepoWhat
switchyardmodel & agent runtime switch board
browserclickyardyour AI clicks, your browser obeys
notes-recover (you here)your Apple Notes never really die
dealyardlet prices fight, you sit and watch
docyarddocs site in, markdown out, no scraping by hand
fileyardmessy folders in, organized library out
proofyardevery 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. ⭐

[Star History Chart]

Also by Yifeng[Terry] Yu

License

MIT — small print, big freedom.

Source: README.md at commit e7ce24c

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0.post1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts