Apple Notes MCP vs MCP Memory Server

A side-by-side look at pricing, capabilities, pros, cons, and our editorial scores.

	Apple Notes MCP MCP Servers	MCP Memory Server MCP Servers
Tagline	Let Claude read your local Apple Notes over the Model Context Protocol.	Persistent knowledge-graph memory for Claude and other MCP clients
Category	MCP Servers	MCP Servers
Pricing	Free· Free / open-source (MIT). No hosted service; runs locally on your Mac.	Free· Free and open source (MIT). Self-hosted; no vendor charges. Runs locally via npx or Docker.
Model	—	—
Editorial score	—	—
Use cases	Personal knowledge retrieval from Apple NotesSearching decade-old meeting notes during a Claude chatPulling travel or recipe notes into a planning conversationSummarising a specific note by titleBuilding a local MCP toolchain alongside filesystem and browser serversReference implementation for writing your own macOS SQLite-backed MCP server	Persistent Claude Desktop memory across chatsLong-lived coding-agent project memoryLightweight personal CRM of people and companiesResearch-agent scratch knowledge graphCross-session preference and style memoryTeam convention and past-bug recall for coding assistantsStructured note-taking backend for MCP clientsLocal-first alternative to hosted memory APIs
Pros	Genuinely local: reads the on-disk SQLite database directly, so notes never leave your Mac Trivial install via uv/uvx and a short claude_desktop_config.json block Exposes the three operations that matter most — list, read, search — with a clean MCP surface MIT-licensed Python, small enough to audit or fork in an afternoon Works with any MCP client, not just Claude Desktop, so it composes with other servers No API keys, no subscriptions, no accounts — zero ongoing cost	Official, Anthropic-maintained reference implementation - the canonical way to add persistent memory to an MCP client Zero-config install via npx or a one-line Docker command; works out of the box with Claude Desktop's claude_desktop_config.json Simple, inspectable JSONL storage on disk that you can grep, diff, back up and edit by hand Structured entity/relation/observation model is more queryable than a raw text scratchpad and cheaper than a vector DB Nine well-scoped tools plus a live-updating knowledge-graph Resource, so agents can both read and mutate memory Fully open source (MIT) and vendor-neutral - runs against any MCP-speaking model, not just Claude Trivial to fork or wrap for team-specific schemas since the codebase is a single small TypeScript file
Cons	Read-only: cannot create, edit, or append notes from within Claude Skips password-protected notes entirely (ZISPASSWORDPROTECTED is unhandled) No attachment content, no checklist state, no pinned-note filtering, no iCloud sync awareness macOS-only by design, and requires granting Full Disk Access to the runner Repository is archived by the maintainer — bug fixes and new features are unlikely without a fork Search is basic keyword matching against the SQLite text, not semantic retrieval	Reference-quality, not production-grade: single-file JSONL storage with no concurrency control, indexing or replication search_nodes is a plain substring match with no embeddings or semantic ranking - large graphs degrade quickly No built-in multi-user, auth or per-project isolation; a shared install mixes memories from every session The model still has to be prompted to actually call the memory tools - forgetful assistants forget to remember No web UI, visualisation or admin surface; you inspect and clean the graph by editing the JSONL yourself Only a local filesystem backend - no Postgres, SQLite or cloud sync option is shipped
Website	github.com	github.com

Pick Apple Notes MCP if

✅ Genuinely local: reads the on-disk SQLite database directly, so notes never leave your Mac
✅ Trivial install via uv/uvx and a short claude_desktop_config.json block
✅ Exposes the three operations that matter most — list, read, search — with a clean MCP surface
✅ MIT-licensed Python, small enough to audit or fork in an afternoon

Pick MCP Memory Server if

✅ Official, Anthropic-maintained reference implementation - the canonical way to add persistent memory to an MCP client
✅ Zero-config install via npx or a one-line Docker command; works out of the box with Claude Desktop's claude_desktop_config.json
✅ Simple, inspectable JSONL storage on disk that you can grep, diff, back up and edit by hand
✅ Structured entity/relation/observation model is more queryable than a raw text scratchpad and cheaper than a vector DB

Compare a different pair →