Apple Notes Snapshot

web MCP Server

Apple Notes backup control room for macOS with AI diagnostics, a token-gated Local Web API, a read-only MCP surface, and clear recovery paths.

Verified
webweb
3 views1 stars0 forksMIT

Why This Matters

Discovered via github-topic:model-context-protocol and last synced 3mo ago.

Verified
Source
github-topic:model-context-protocol
Stars
1
Last synced
3mo ago
Install
Check source

Install

Install instructions not detected yet

Check the source repository for the latest setup steps.

View source instructions
13
Tools
0
Resources
0
Prompts
Standard I/O
Transport

Available Tools (13)

Need

Upstream `notes-exporter`

Yes

Yes

Limited

State files, metrics, and summaries

Manual

Wrapper-owned log handling

No

Optional, token-aware local control plane

pre-commit

every local commit attempt

pre-push

every local push attempt

hosted

pull request / push / workflow dispatch

nightly

scheduled GitHub run

manual

deliberate human/operator action

verify

doctor

branch

sha> ``` ## Who this is for - People who already rely on Apple Notes and want local, repeatable snapshots - macOS users who prefer `launchd` over cloud schedulers - Anyone who wants backup health, logs, and operational visibility around Apple Notes exports - Maintainers who want a reviewable wrapper instead of ad hoc shell snippets ## Who this is not for - Teams looking for a shared cloud notes product - Anyone expecting two-way sync back into Apple Notes - Cross-platform note automation workflows - Hosted SaaS or desktop app buyers ## Proof and verification This repository ships with repo-owned verification commands instead of asking you to trust screenshots alone. These are maintainer / contributor gates, not required for the first successful snapshot. If you want the shorter public-facing evidence page first, open the [proof page](https://xiaojiou176-open.github.io/apple-notes-snapshot/proof/). It keeps the repo-side gates, GitHub-controlled delivery facts, and the current access boundary in one place. The ladder below remains the maintainer-grade verification contract. Default local maintainer lane: ```bash ./notesctl rebuild-dev-env ./.runtime-cache/dev/venv/bin/python -m pre_commit run --all-files PYTHON_BIN=./.runtime-cache/dev/venv/bin/python scripts/checks/ci_gate.sh ``` Maintainer verification expects a local Python 3.11+ toolchain. `./notesctl rebuild-dev-env` recreates `.runtime-cache/dev/venv` from scratch so the documented verification commands stay aligned with the current checkout path and interpreter. GitHub Actions for this repo run on **GitHub-hosted runners**; the local ladder below is maintainer verification, not a self-hosted runner requirement. Five-layer CI contract:

Layer

Default trigger