reminders-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| statusA | Check Apple Reminders authorization status. Returns whether remindctl has permission to access Reminders. |
| show-remindersA | View reminders filtered by time range or status. Supports today, tomorrow, week, overdue, upcoming, completed, all, or a specific YYYY-MM-DD date. Optionally filter by list name. |
| list-listsA | List all reminder lists. Returns each list's ID, title, reminder count, and overdue count. |
| create-listB | Create a new reminder list with the given name. |
| rename-listA | Rename an existing reminder list. |
| delete-listA | Delete a reminder list and all its reminders. This action cannot be undone. |
| add-reminderA | Create a new reminder in Apple Reminders. Supports setting list, due date, notes, and priority. |
| edit-reminderA | Modify an existing reminder. Reference by index number (from show output) or ID/UUID prefix. Can change title, list, due date, notes, priority, or completion status. |
| complete-remindersA | Mark one or more reminders as completed. Reference by index numbers (from show output) or ID/UUID prefixes. |
| delete-remindersA | Delete one or more reminders. Reference by index numbers (from show output) or ID/UUID prefixes. This action cannot be undone. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Each tool targets a distinct resource+action: list management, reminder management, status check, and viewing. No two tools have overlapping purposes, as show-reminders is for reminders while list-lists is for lists, and edit-reminder vs complete-reminders serves singular vs bulk completion.
Most tools follow a consistent verb-noun hyphenated pattern (show-reminders, create-list, add-reminder, etc.), but 'status' is a single noun that does not fit the verb-noun convention. This is a minor deviation in an otherwise predictable naming scheme.
With 10 tools, the server is well-scoped for a reminders domain, covering both list and reminder operations without bloat. Each tool earns its place, and the count is within the ideal range for maintainability.
The tool set provides full lifecycle coverage: lists can be created, renamed, listed, and deleted; reminders can be added, shown, edited, completed, and deleted. The addition of a status check for authorization fills a practical need, leaving no obvious gaps.