Apple Notes MCP vs MCP Everything Server

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

	Apple Notes MCP MCP Servers	MCP Everything Server MCP Servers
Tagline	Let Claude read your local Apple Notes over the Model Context Protocol.	The kitchen-sink reference MCP server that exercises every corner of the Model Context Protocol
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 License). No cloud service or paid tier — you run it locally via npx, Docker, or your MCP client of choice.
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	MCP client conformance testingRegression testing of stdio and Streamable HTTP transportsVerifying sampling round-trip behavior in a new agent hostDebugging elicitation UI in an IDE integrationReference reading for authoring a new MCP serverDemoing MCP primitives in workshops and talksSmoke-testing cancellation and progress-notification handlingValidating resource-subscription update delivery
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	Only server that exercises the full MCP feature matrix in one place — tools, resources, prompts, sampling, elicitation, roots, logging, subscriptions, and Tasks Maintained by the Model Context Protocol project itself, so behavior tracks the spec as it evolves (SEP-1686 Tasks, Streamable HTTP, etc.) Runs anywhere an MCP client runs — npx, Docker, Claude Desktop, VS Code, Cursor, Windsurf — with stdio or HTTP transports TypeScript source is short and readable, making it a de-facto reference for how each handler should be shaped MIT-licensed, no telemetry, no signup, no cloud dependency Includes progress notifications and cancellation flows that most tutorial servers skip, so client cancel/timeout logic can be exercised properly
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	Explicitly not useful for end users — it does not do anything a human would actually want done Feature drift means some primitives (SEP-1686 Tasks, elicitation) may not yet be implemented in every client, producing red herrings during testing Documentation is a single features.md; there is no guided tour that maps each tool to the spec section it exercises TypeScript-only reference — Python or Rust client authors have to translate patterns themselves Sampling and elicitation flows depend on the client honoring them, so a silent client makes it hard to tell whether the server or the client is at fault
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 Everything Server if

✅ Only server that exercises the full MCP feature matrix in one place — tools, resources, prompts, sampling, elicitation, roots, logging, subscriptions, and Tasks
✅ Maintained by the Model Context Protocol project itself, so behavior tracks the spec as it evolves (SEP-1686 Tasks, Streamable HTTP, etc.)
✅ Runs anywhere an MCP client runs — npx, Docker, Claude Desktop, VS Code, Cursor, Windsurf — with stdio or HTTP transports
✅ TypeScript source is short and readable, making it a de-facto reference for how each handler should be shaped

Compare a different pair →