Skip to main content
📖 The AI Tool Bible

Apple Notes MCP vs Home Assistant MCP

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

 
Apple Notes MCP
MCP Servers
Home Assistant MCP
MCP Servers
TaglineLet Claude read your local Apple Notes over the Model Context Protocol.Open-source MCP server that lets any LLM control and observe a Home Assistant smart home in real time.
CategoryMCP ServersMCP Servers
PricingFree· Free / open-source (MIT). No hosted service; runs locally on your Mac.Free· Free and open source (Apache 2.0). Self-hosted; only cost is your own Home Assistant instance and the LLM client you connect to it.
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
Conversational smart-home control from Claude Desktop or CursorLLM-driven Home Assistant automationsReal-time device state monitoring via SSEVoice-agent frontends that call HA servicesBulk add-on and HACS package management through chatPrototyping custom home-lab AI assistantsNatural-language climate and lighting scenesCamera snapshot and motion event triaging
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
  • Broad domain coverage — lights, climate, covers, media, locks, vacuums, cameras, and more mapped to MCP tools out of the box
  • Real-time SSE subscriptions let an LLM react to state changes and automation triggers, not just poll
  • Docker Compose setup and clear env-var config make it easy to run alongside an existing Home Assistant install
  • Exposes system-level surfaces most HA wrappers skip: add-on management, HACS package installs, automation CRUD
  • Token auth plus rate limiting on the bridge, so it isn't a trivially open control plane
  • Apache 2.0 licensed, TypeScript, 500+ GitHub stars and active commits — reasonable community traction for an MCP project
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
  • Requires a working Home Assistant instance and long-lived access token — not useful without one
  • Self-hosted only; you own the reverse-proxy, TLS, and network exposure decisions
  • Model-agnostic by design, so quality of device control depends heavily on which LLM client you attach
  • Single-maintainer community project — issue triage and roadmap can be slower than vendor MCP servers
  • Broad tool surface can flood an LLM's context window if you don't scope subscriptions to specific domains
Websitegithub.comgithub.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 Home Assistant MCP if
  • ✅ Broad domain coverage — lights, climate, covers, media, locks, vacuums, cameras, and more mapped to MCP tools out of the box
  • ✅ Real-time SSE subscriptions let an LLM react to state changes and automation triggers, not just poll
  • ✅ Docker Compose setup and clear env-var config make it easy to run alongside an existing Home Assistant install
  • ✅ Exposes system-level surfaces most HA wrappers skip: add-on management, HACS package installs, automation CRUD
Compare a different pair →