Reminders MCP Server
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_reminder_listsA | Get all reminder lists from macOS Reminders app. Returns list names, IDs, and reminder counts. |
| create_reminder_listC | Create a new reminder list in macOS Reminders app. |
| delete_reminder_listA | Delete a reminder list and all its reminders. This action cannot be undone. |
| rename_reminder_listC | Rename an existing reminder list. |
| get_remindersB | Get reminders with optional filtering by list, completion status, priority, date range, or search text. |
| get_reminderC | Get a single reminder by its ID. |
| create_reminderC | Create a new reminder in the specified list. |
| update_reminderC | Update an existing reminder's properties. Only specified fields will be changed. |
| delete_reminderA | Delete a reminder. This action cannot be undone. |
| complete_reminderC | Mark a reminder as completed or incomplete. |
| batch_create_remindersB | Create multiple reminders at once. More efficient than creating one at a time. |
| batch_update_remindersB | Update multiple reminders at once. More efficient than updating one at a time. |
| batch_complete_remindersC | Mark multiple reminders as completed or incomplete at once. |
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 13 tools
Every tool has a clearly distinct purpose with no ambiguity. The tools are organized around specific resources (reminders, reminder lists) and actions (create, get, update, delete, complete, list, rename), with clear boundaries between individual and batch operations. An agent can easily distinguish between tools like 'create_reminder' and 'batch_create_reminders' based on their descriptions.
All tools follow a consistent verb_noun pattern with snake_case throughout. The naming is predictable and readable, with clear conventions like 'create_reminder', 'get_reminders', 'update_reminder', 'delete_reminder_list', and 'batch_complete_reminders'. There are no deviations in style or structure.
With 13 tools, the count is well-scoped for a reminders management server. Each tool earns its place by covering essential CRUD operations for both reminders and reminder lists, including individual and batch variants, without feeling excessive or thin. This aligns with typical server scopes of 3-15 tools.
The tool surface provides complete CRUD/lifecycle coverage for the reminders domain. It includes creation, retrieval, updating, deletion, and completion for reminders, plus list management operations (create, list, rename, delete). There are no obvious gaps, and agents can handle all core workflows without dead ends.