Model Context Protocol server for Apple Reminders. Provides tools to list, create, update, and manage reminders across reminder lists on macOS via the EventKit framework.
The Apple Events MCP server provides 10 tools for managing reminders with consistent naming conventions (verb_noun pattern: list_, create_, mark_, delete_) and reasonable descriptions. All tools have basic input schemas with type definitions. However, there are significant gaps: (1) Output schemas are completely undocumented, no descriptions of what fields tools return, (2) Parameter descriptions lack constraint details (e.g., priority '0-9' is stated in description but not as JSON Schema min/max), (3) No error guidance or recovery paths documented, (4) Several parameters could be optional but are listed as required without justification. The server follows the basic tool structure pattern but lacks the depth expected of production-grade tools. Average tool score: 62/100.
Create a new reminder with optional title, notes, due date, and priority in a specified list
Create a new reminder list with the specified name
Delete a reminder permanently
Delete a reminder list and all its reminders permanently
List all reminder lists (calendars) available on the system
List reminders from a specific list or all lists, optionally filtering by completion status
Output schemas completely undocumented. No tool describes what fields are returned, their types, or structure. LLMs cannot plan downstream calls or extract data reliably.
Numeric constraints (priority 0-9) and enum values documented only in parameter descriptions, not in JSON Schema. LLMs cannot parse text-only constraints reliably; should use JSON Schema min/max/enum.
No error recovery guidance. Destructive operations (delete_reminder, delete_reminder_list) have no confirmation step, dry-run capability, or actionable error messages documented.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | D | 58 | <=2025-11-25 | v2 |
Get all incomplete reminders that are due today or past due
Mark a reminder as complete
Mark a reminder as incomplete
Update an existing reminder's title, notes, due date, or priority
Parameter identifier design: list_name is human-readable (good), but reminder_id lacks guidance on format or how to obtain it. No mention of whether IDs are opaque strings, UUIDs, or numeric.
No pagination documented for list operations (list_reminders, list_today_reminders). If hundreds of reminders exist, responses could exceed context limits. Should include limit/offset and total_count.
Idempotency not documented. Operations like mark_reminder_complete should be idempotent (safe to retry), but this is not stated. Agents retry on ambiguous failures, non-idempotent tools risk duplicate side effects.
Missing parameter type specification in JSON Schema. 'priority' is documented as '0-9' in text but should be JSON Schema integer with minimum/maximum. 'due_date' format 'ISO8601' should be JSON Schema string with format:'date-time'.