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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_reminder_listsA | List all reminder lists available in the macOS Reminders app. |
| list_remindersA | List reminders from the macOS Reminders app. Args: list_name: Optional name of a specific list to filter by. Leave empty for all lists. include_completed: Whether to include completed reminders (default: False). |
| create_reminderA | Create a new reminder in the macOS Reminders app. Args: name: The title of the reminder. list_name: The list to add the reminder to. Uses the default list if empty. due_date: Optional due date, e.g. "February 28, 2026 at 9:00 AM". notes: Optional notes/body for the reminder. Returns: The name of the created reminder. |
| update_reminderA | Update properties of an existing reminder. Args: name: The exact current name of the reminder to update. list_name: Optional list name to narrow the search. new_name: New title for the reminder. Leave empty to keep unchanged. notes: New notes/description. Leave empty to keep unchanged. due_date: New due date, e.g. "February 28, 2026 at 9:00 AM". Leave empty to keep unchanged. Returns: True if the reminder was found and updated, False otherwise. |
| complete_reminderA | Mark a reminder as completed. Args: name: The exact name of the reminder to complete. list_name: Optional list name to narrow the search. Returns: True if the reminder was found and completed, False otherwise. |
| delete_reminderA | Delete a reminder permanently. Args: name: The exact name of the reminder to delete. list_name: Optional list name to narrow the search. Returns: True if the reminder was found and deleted, False otherwise. |
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 6 tools
Each tool maps to a distinct action and resource: lists vs reminders, and create/update/complete/delete are clearly separated. No overlap in purpose.
All six tools follow a consistent verb_noun pattern (list_, create_, update_, complete_, delete_), making the API predictable and easy to navigate.
With 6 tools, the server is well-scoped for a reminders app—covering listing, creation, update, completion, and deletion without bloat or missing essentials.
The lifecycle is well-covered, but there is no way to uncomplete a reminder or fetch a single reminder by ID. List with filtering mitigates this, but a status-reversal would round out the surface.