MCP server for Apple Notes — search, read, create, append, and sync notes via the Model Context Protocol.
Solid foundation with 11 well-named tools covering read/write/sync operations on Apple Notes. All tools have descriptions (avg 120 chars) and input schemas with typed parameters. However, output schemas are not documented in the source code provided, parameter descriptions lack detail on constraints/formats, and error handling guidance is minimal. No tool annotations (readOnlyHint/destructiveHint) despite clear risk classifications. Naming follows verb_noun convention well (search_notes, read_note, create_note, append_note). Parameter naming is mostly consistent but lacks type suffixes (e.g., 'folder' vs 'folder_name'). Missing: enum constraints for folder/account params, format specs for note IDs, and recovery guidance in error messages.
Append content to an Apple Note or preview the mutation with dryRun.
Create a new Apple Note or preview the mutation with dryRun.
Check Apple Notes reachability, permissions, and platform diagnostics.
Retrieve a single cached note entry by its Apple Notes note ID (x-coredata:// URI). Returns the full entry including all checklists and attachments.
List cached note entries from a previously synced folder, optionally filtered by year. Returns each entry's title, year, bodyPreview, checklists, and attachment paths.
Sync Apple Notes folders into a local JSON cache. Pass any folder names you want indexed (e.g. "Journal", "2025", "Projects"). Checklists and attachments are extracted automatically. Unchanged notes are skipped.
Output schemas not documented. LLMs cannot plan downstream calls or extract required fields (e.g., note IDs for chaining). Affects all 11 tools.
Parameter descriptions lack constraint details. 'folder' and 'account' accept free-form strings with no enum or validation guidance. 'limit' has no min/max bounds. 'id' format (x-coredata:// URI) not explained in read_note or note_get descriptions.
No tool annotations despite clear risk classifications. create_note and append_note are WRITE operations; note_sync is WRITE. Missing destructiveHint/idempotentHint annotations prevent agents from reasoning about retry safety and side effects.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 67 | 2025-06-18+ | v2 |
Return the status of the most recent note sync: last sync time, entry count, error count, and any error messages.
Read the full plain-text body of every note in an Apple Notes folder in a single call. Returns an array of notes sorted by the order Apple Notes stores them. When Full Disk Access is granted, each note includes a `structured` field with `checklists` (items with `text` and `done`) and `tags` (hashtags). Suitable for bulk analysis without per-note round-trips.
Read a single Apple Note by its opaque identifier. When Full Disk Access is granted, the response includes a `structured` field with `checklists` (each item has `text` and `done` boolean) and `tags` (hashtags attached to the note).
Search Apple Notes by query, folder, account, and limit.
Search hashtags used in Apple Notes. When Full Disk Access is granted, uses a fast direct SQLite query returning all tags with occurrence counts. Falls back to a JXA body-text scan when Full Disk Access is unavailable.
No dry-run or confirmation pattern for destructive operations. create_note and append_note accept dryRun param, but no guidance on what happens if dryRun is omitted or how to confirm before executing. Agents may accidentally create/modify notes.
Error handling lacks recovery guidance. No documented error codes, retryable vs fatal classifications, or actionable next steps. E.g., if read_note fails with 'note not found', should the agent call search_notes? Not stated.