Apple Notes MCP vs Chroma MCP

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

	Apple Notes MCP MCP Servers	Chroma MCP MCP Servers
Tagline	Let Claude read your local Apple Notes over the Model Context Protocol.	Official MCP server that gives LLM clients direct access to the Chroma vector database.
Category	MCP Servers	MCP Servers
Pricing	Free· Free / open-source (MIT). No hosted service; runs locally on your Mac.	Free· Open source (Apache 2.0). Free to run locally or self-hosted; embedding-function API keys (OpenAI, Cohere, Jina, VoyageAI, Roboflow) billed by those providers. Chroma Cloud pricing set separately by Chroma.
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	Long-term memory for Claude DesktopTeam knowledge base shared across agentsRAG over local documentsSemantic code search in Cursor or ContinueVector store for custom MCP agentsPersonal notes and journal recallMetadata-filtered document retrievalChroma Cloud access from LLM clients
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 server from the Chroma team, tracks the database's features closely Four deployment modes (ephemeral, persistent, HTTP, Chroma Cloud) from one binary Twelve well-scoped MCP tools cover the full collection and document lifecycle Supports six embedding functions including OpenAI, Cohere, Jina, and VoyageAI with per-collection persistence Zero-config install via uvx - drops into Claude Desktop or Cursor in a couple of JSON lines Apache 2.0 licensed and readable Python source; easy to fork or extend Query tools expose HNSW tuning and metadata/full-text filters, not just naive semantic search
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	You still have to run and back up the Chroma store yourself unless you pay for Chroma Cloud Command-line API key arguments are convenient but leak into process lists; env/.env path is safer but extra setup No built-in access control or multi-tenant isolation - anything the MCP client sees, it can delete Embedding-function persistence only works for collections created on Chroma v1.0.0+; older stores need migration Python-only server; teams on pure Node stacks add a runtime dependency MCP tool surface is CRUD-shaped - no higher-level RAG primitives like chunking, re-ranking, or hybrid fusion
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 Chroma MCP if

✅ Official server from the Chroma team, tracks the database's features closely
✅ Four deployment modes (ephemeral, persistent, HTTP, Chroma Cloud) from one binary
✅ Twelve well-scoped MCP tools cover the full collection and document lifecycle
✅ Supports six embedding functions including OpenAI, Cohere, Jina, and VoyageAI with per-collection persistence

Compare a different pair →