apple-notes-mcp
Provides an MCP server that lets AI assistants interact with Apple Notes on macOS via AppleScript/CoreData—creating, searching, reading, updating, deleting (move to Recently Deleted), moving notes between folders, and performing folder/account/batch/export/diagnostic operations. Uses local-only automation; no external APIs are described.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Strengths: local-only automation is implied; no external network API or tokens are described; TLS is not directly applicable because interactions are via local process/MCP over localhost. Concerns: any note content is accessible to whoever can use the MCP server; there is no mention of fine-grained authorization or per-tool scope enforcement; permission prompting for AppleScript automation means the user effectively grants powerful access to Notes.app.
⚡ Reliability
Best When
You want an AI assistant to manage your personal Apple Notes on your own Mac and you can grant macOS automation/AppleScript permissions.
Avoid When
You cannot allow desktop automation of Notes.app, need guaranteed transactional safety for destructive operations, or require enterprise-grade audit/compliance guarantees beyond local device controls.
Use Cases
- • Save conversations as Apple Notes (create notes with titles/content)
- • Search notes by title or note body; filter by account/folder/date/limit
- • Read and summarize specific notes (HTML/Markdown export)
- • Update note titles/content reliably using note IDs (CoreData identifiers)
- • Organize notes by moving to folders; manage folders and accounts
- • Batch delete/move notes by IDs
- • Detect sync/shared state via diagnostics and warnings (per README features)
Not For
- • Server-side/cloud note management (macOS Apple Notes automation is local and user-machine bound)
- • High-concurrency multi-user workflows (Apple Notes UI automation is typically single-user desktop behavior)
- • Use as a general document database (data model is Apple Notes/CoreData driven)
- • Handling secrets in note content without considering local access/security controls
Interface
Authentication
No network authentication is described; access is effectively the local user’s ability to control Notes.app and the configured Notes accounts in Apple Notes.
Pricing
NPM package (MIT). No pricing model described for the server itself.
Agent Metadata
Known Gotchas
- ⚠ Use note IDs (CoreData identifiers) instead of titles to avoid duplicates/ambiguity.
- ⚠ Title/content rules: create-note expects title in `title` param and content without duplicating the title; plaintext/html formatting rules can lead to doubled titles if misunderstood.
- ⚠ move-note behavior: it copies to destination then deletes original; if delete fails the note may exist in both places.
- ⚠ Delete moves to Recently Deleted (recovery behavior depends on Notes app retention/UI).
- ⚠ Automation requires macOS permission to control Notes.app; the agent user must complete the prompt once.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for apple-notes-mcp.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-30.