fradser/mcp-server-apple-reminders

The operation to perform on calendars.

Optional range end for scoped calendar discovery. When used with startDate, only calendars with at least one event in the range are returned, each annotated with the in-range event count (recurring events count as one per instance). endDate must be on or after startDate.

Optional range start for scoped calendar discovery. Format: 'YYYY-MM-DD', 'YYYY-MM-DD HH:mm:ss', or ISO 8601. If only one of startDate/endDate is supplied, the other is filled in as a 14-day window from the bound that was given.

The operation to perform.

READ-ONLY filter: narrow read results by event availability. Cannot be set via create/update; configure in Calendar.app.

End date and time. RECOMMENDED format: 'YYYY-MM-DD HH:mm:ss' (local time). Use 'YYYY-MM-DD' (no time) for all-day events. Also supports 'YYYY-MM-DDTHH:mm:ss' or ISO 8601 with timezone. For action='read': if omitted and startDate is omitted, defaults to today + 14 days; if only startDate is provided, endDate defaults to startDate + 14 days.

Filter events by a specific calendar name.

The unique identifier of the event (REQUIRED for update, delete; optional for read to get single event).

Location text for the event.

Additional notes for the event.

A search term to filter events by title, notes, or location (applied in TS after fetch).

Scope for changes to recurring events: this-event or future-events.

Start date and time. RECOMMENDED format: 'YYYY-MM-DD HH:mm:ss' (local time, e.g., '2025-11-04 09:00:00'). Use 'YYYY-MM-DD' (no time) for all-day events. Also supports 'YYYY-MM-DDTHH:mm:ss' or ISO 8601 with timezone. For action='read': if omitted and endDate is omitted, defaults to today; if only endDate is provided, startDate defaults to endDate - 14 days.

The name of the calendar for the create action. Events cannot be moved across calendars via update — delete and recreate instead.

IANA timezone identifier for a timed event (e.g., 'America/New_York', 'Asia/Shanghai'). Timed events' start and end times are interpreted in this timezone. All-day events ignore this option.

The title of the event (REQUIRED for create, optional for update).

The operation to perform on a list.

The current name of the list (for update, delete) or the name of the new list (for create).

The new name for the list (for update).

The operation to perform: read (list subtasks), create (add new), update (modify), delete (remove), toggle (flip completion), reorder (change order).

The completion status of the subtask (for update).

Array of subtask IDs in desired order (REQUIRED for reorder). Must include all subtask IDs.

The unique identifier of the parent reminder (REQUIRED for all operations).

The unique identifier of the subtask (REQUIRED for update, delete, toggle).

The title of the subtask (REQUIRED for create, optional for update).

The operation to perform.

Tags to add to the reminder (for update). Merges with existing tags. Example: ["followup"]

Mark the reminder as completed/uncompleted (update only).

Due date. RECOMMENDED format: 'YYYY-MM-DD HH:mm:ss' (local time without timezone, e.g., '2025-11-04 18:00:00'). Also supports: 'YYYY-MM-DD', 'YYYY-MM-DDTHH:mm:ss', or ISO 8601 with timezone (e.g., '2025-10-30T04:00:00Z'). When no timezone is specified, the time is interpreted as local time.

Filter reminders by a due date range (applied in TS after fetch).

End of the due-date window (READ-only, action='read'). Passed to the CLI as --end; the end day is exclusive. Only the date part is used — any time/zone component is truncated to the date prefix (day granularity). If only one of startDate/endDate is supplied, the other is filled in as a 14-day window.

Filter reminders by a specific list name.

Filter to only show location-based reminders when true.

Filter reminders by priority level.

Filter to only show recurring reminders when true.

Filter reminders by tags (must have ALL specified tags). Example: ["work", "urgent"]

The unique identifier of the reminder (REQUIRED for update, delete; optional for read to get single reminder).

Additional notes for the reminder.

Priority level: 0=none, 1=high, 5=medium, 9=low (for create/update).

Tags to remove from the reminder (for update). Example: ["urgent"]

A search term to filter reminders by title or notes (applied in TS after fetch).

Include completed reminders in the results.

Start date. When action='update': sets the reminder's start date (the CLI cannot set it at create time) — format 'YYYY-MM-DD', 'YYYY-MM-DD HH:mm:ss', or ISO 8601. When action='read': start of the due-date window, passed to the CLI as --start (start day inclusive). For read, only the date part is used — any time/zone component is truncated to the date prefix, so a window is resolved at day granularity. If only one of startDate/endDate is supplied for read, the other is filled in as a 14-day window.

Initial subtasks to create with the reminder (for create action). Provide an array of subtask titles. Example: ["Buy milk", "Get eggs", "Pick up bread"]

Tags to set on the reminder (for create). Replaces any existing tags. Example: ["work", "urgent"]

The name of the list for create or update operations.

The title of the reminder (REQUIRED for create, optional for update).

A URL to associate with the reminder.