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_toolsandget_tool_infofor 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_readonlysafe_managefull_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'sAppleReminders-MCP/start.sh) to your MCP client - Reload or reconnect the client so the Reminders tool surface is loaded into context
- Call
reminders_healthfirst - If Reminders access is blocked, call
reminders_permission_guide - After changing macOS permissions, call
reminders_recheck_permissions
Prompting Notes
tools/listreturns the full Reminders tool surface. Context-constrained clients can usesearch_toolsfirst, thenget_tool_infofor 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_daterequires a timezone offset:yyyy-MM-ddTHH:mm:ss-HH:00
Related
Metadata
Release files for apple-mcp-reminders 1.1.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| apple_mcp_reminders-1.1.4.tar.gz | 34.6 kB | With provenance | Details for apple_mcp_reminders-1.1.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| apple_mcp_reminders-1.1.4-py3-none-any.whl | Python 3 | none | any | Details for apple_mcp_reminders-1.1.4-py3-none-any.whl |
Total release size: 66.0 kB
Release files / apple_mcp_reminders-1.1.4.tar.gz
| Download URL | apple_mcp_reminders-1.1.4.tar.gz |
|---|---|
| Size | 34.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
59d9da50ccb1f8ae1db3670fe94868305ff038b3d74dc7d782bc04fab059fab1
|
|
BLAKE2b-256 checksum How to use checksums |
c72f15c5768d8a841b7f00893f54aa77ebc7f5d35db74d2d01feeb238c3dc3b3
|
| 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 26, 2026.
Transparency logRelease files / apple_mcp_reminders-1.1.4-py3-none-any.whl
| Download URL | apple_mcp_reminders-1.1.4-py3-none-any.whl |
|---|---|
| Size | 31.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
28653988f9414cd9b1ff4149aa9eb05dc0703931cc3465e650eaae39ace4fc6d
|
|
BLAKE2b-256 checksum How to use checksums |
4219bc81595fee5b8a363e09cd60abd3ebb1c003d201e81bdd091f46dbc6bf00
|
| 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 26, 2026.
Transparency logSecurity for apple-mcp-reminders 1.1.4
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.
Attestation for apple_mcp_reminders-1.1.4.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 26, 2026.
Transparency logA 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.