apple-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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_remindersB | List reminders from Apple Reminders. Optionally filter by list name and include completed items. |
| create_reminderB | Create a new reminder in Apple Reminders. |
| complete_reminderC | Mark a reminder as completed. |
| delete_reminderB | Permanently delete a reminder. |
| update_reminderA | Update fields on an existing reminder. Only provided fields are changed. If you update notes OR tags individually, the other is preserved automatically. |
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 5 tools
Each tool addresses a distinct action on reminders: create, list, complete, update, and delete. There is no overlap or ambiguity between them.
All tools follow a consistent verb_noun pattern (e.g., create_reminder, delete_reminder), with verbs clearly indicating the operation.
With 5 tools, the set is well-scoped for managing reminders, covering core operations without unnecessary bloat.
CRUD operations are present along with a completion action. Missing a 'get single reminder' tool is a minor gap, but the set is largely complete for its domain.