MCP Server - My Apple Remembers

Created By
baryhuanga year ago
A lightweight MCP server that integrates with Apple Notes to create a personal memory system for AI. Easily recall and save information from your Mac using simple AppleScript commands. Compatible with all macOS versions with minimal setup requirements.
Overview

What is My Apple Remembers?

My Apple Remembers is a lightweight MCP server that integrates with Apple Notes to create a personal memory system for AI, allowing users to easily recall and save information from their Mac using simple AppleScript commands.

How to use My Apple Remembers?

To use My Apple Remembers, enable SSH on your macOS, install Docker Desktop, and configure the MCP server with your macOS credentials. You can then use prompts to instruct how you want your memory to be saved and recalled.

Key features of My Apple Remembers?

  • Memory Recall: Access notes, calendar events, messages, files, and other information from your Mac.
  • Memory Persistence: Save important information to Apple Notes for future reference.
  • Minimal Setup: Just enable Remote Login on the target Mac.
  • Universal Compatibility: Works with all macOS versions.

Use cases of My Apple Remembers?

  1. Recalling important notes and calendar events.
  2. Saving messages and files for future reference.
  3. Integrating with AI systems to enhance memory management.

FAQ from My Apple Remembers?

  • Can I use My Apple Remembers on any macOS version?

Yes! It is compatible with all macOS versions.

  • Is there a setup guide available?

Yes! Detailed installation and configuration instructions are provided in the documentation.

  • What security measures should I take?

Always use secure, authenticated connections when accessing remote macOS machines.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
baryhuang
Star
2
Language
Python
License
MIT license

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)

4 hours ago
Gpt Scrambler

a day ago