Skip to main content

Apple Reminders MCP

MCP server for Apple Reminders on macOS.

Provides access to reminder lists and tasks through EventKit. Keep Reminders as the system of record while enabling agents to read, create, update, complete, and delete reminders.

When to use

  • Task and reminder workflows
  • Reminders isolated from the rest of the Apple stack
  • EventKit-backed reminder management

What It Does

  • Discover, create, and delete reminder lists
  • List, create, update, and delete reminders
  • Complete and uncomplete tasks
  • Tool discovery helpers search_tools and get_tool_info for context-constrained clients
  • Today and list resources
  • Planning and inbox-triage prompts
  • Health and permission checks: reminders_health, reminders_permission_guide, reminders_recheck_permissions

Install On This Mac

Quick start (uvx, from PyPI)

With uv installed:

uvx apple-mcp-reminders

No clone, no venv management.

From a clone
git clone https://github.com/JonathanRReed/Apple-MCPs.git
cd Apple-MCPs
uv sync --all-packages

This builds one workspace environment with every server's entry point in .venv/bin (for example .venv/bin/apple-reminders-mcp). You can also point an MCP client at AppleReminders-MCP/start.sh, which prefers uv run and falls back to a plain venv bootstrap (Python 3.11+ required).

Install In AI Agents

Generic MCP client config
{
  "mcpServers": {
    "apple-reminders": {
      "command": "uvx",
      "args": ["apple-mcp-reminders"],
      "env": {
        "APPLE_REMINDERS_MCP_SAFETY_MODE": "safe_manage"
      }
    }
  }
}

Running from a clone instead? Use /path/to/Apple-MCPs/AppleReminders-MCP/start.sh as the command with empty args.

Claude Code example
claude mcp add --transport stdio --scope user apple-reminders -- uvx apple-mcp-reminders

--scope user makes the server available in every project. To share it with one repository through its .mcp.json instead, use --scope project.

Safety Modes

  • safe_readonly
  • safe_manage
  • full_access

Transport

stdio is the default and recommended transport. Set APPLE_REMINDERS_MCP_TRANSPORT=streamable-http (with optional APPLE_REMINDERS_MCP_HOST and APPLE_REMINDERS_MCP_PORT) to serve Streamable HTTP instead.

macOS Permissions

  • Reminders access is required

Launch Checklist

  • Add uvx apple-mcp-reminders (or a clone's AppleReminders-MCP/start.sh) to your MCP client
  • Reload or reconnect the client so the Reminders tool surface is loaded into context
  • Call reminders_health first
  • If Reminders access is blocked, call reminders_permission_guide
  • After changing macOS permissions, call reminders_recheck_permissions

Prompting Notes

  • tools/list returns the full Reminders tool surface. Context-constrained clients can use search_tools first, then get_tool_info for the Reminders tool they need.
  • Reminders are organized into lists. Identify available lists on first use and set a default.
  • Use Reminders for due items, tasks, and follow-ups.
  • due_date requires a timezone offset: yyyy-MM-ddTHH:mm:ss-HH:00

Metadata

Release files for apple-mcp-reminders 1.1.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for apple-mcp-reminders 1.1.3
File Size Uploaded Provenance Actions
apple_mcp_reminders-1.1.3.tar.gz 32.4 kB With provenance Details for apple_mcp_reminders-1.1.3.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for apple-mcp-reminders 1.1.3
File Interpreter ABI Platform Actions
apple_mcp_reminders-1.1.3-py3-none-any.whl Python 3 none any Details for apple_mcp_reminders-1.1.3-py3-none-any.whl

Total release size: 61.5 kB

Release files / apple_mcp_reminders-1.1.3.tar.gz

Download URL apple_mcp_reminders-1.1.3.tar.gz
Size 32.4 kB
Tags Source
SHA-256 checksum
How to use checksums
f693b61f008cb2bfe2e206bb9806ae97e45cbe4b25de176082859db26aed3771
BLAKE2b-256 checksum
How to use checksums
c58e72e6493b20de8aa55ae2bc2d708c1403eb40cb0c5871ae171e4884c7557d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 22, 2026.

Transparency log

Release files / apple_mcp_reminders-1.1.3-py3-none-any.whl

Download URL apple_mcp_reminders-1.1.3-py3-none-any.whl
Size 29.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
6e670552487406fd8bcabba22bb9da58223e3d442dc9f7618d0910bf7de3bc24
BLAKE2b-256 checksum
How to use checksums
81fd8c16ae30af32bef6ee93cd57ee87b1e617bc0d382e3854bd9aa102a256be
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 22, 2026.

Transparency log

Security for apple-mcp-reminders 1.1.3

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for apple_mcp_reminders-1.1.3.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 22, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page