MCP Apple Notes

Created By
RafalWilinskia year ago
Talk with your notes in Claude. RAG over your Apple Notes using Model Context Protocol.
Overview

MCP Apple Notes

MCP Apple Notes is a tool that allows users to interact with their Apple Notes using an AI assistant named Claude through a Model Context Protocol (MCP) server, enabling enhanced search and retrieval functionalities.

How to Use MCP Apple Notes?

To use MCP Apple Notes, clone the repository from GitHub, install the necessary dependencies, and configure the Claude desktop application to integrate with the MCP server for your local notes.

Key Features of MCP Apple Notes?

  • 🔍 Semantic search capabilities using all-MiniLM-L6-v2 on-device embeddings.
  • 📝 Full-text search for quick access to notes.
  • 📊 Vector storage for efficient data retrieval using LanceDB.
  • 🤖 MCP server compatibility for AI interactions.
  • 🍎 Seamless integration with native Apple Notes via JXA.
  • 🏃‍♂️ Fully local operation, requiring no external API keys.

Use Cases of MCP Apple Notes?

  1. Searching through large volumes of notes on command.
  2. Engaging with AI to generate contextually relevant replies from stored notes.
  3. Indexing notes for better organization and retrieval.

FAQ from MCP Apple Notes?

  • Can I use this integration without being online?
    Yes! The entire setup is designed for local execution, ensuring your notes remain private.

  • What prerequisites are needed?
    You need Bun installed for dependency management and the Claude desktop application to facilitate AI interaction.

  • Is it possible to customize how my notes are indexed?
    Yes, future updates will include options for custom embeddings and control over the database functionalities.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
RafalWilinski
Star
213
Language
TypeScript
License
-
Tags

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago