Apple 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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| listReminderListsA | Get all reminder lists from Apple Reminders |
| getRemindersB | Get reminders from a specific list in Apple Reminders |
| createReminderC | Create a new reminder in Apple Reminders |
| completeReminderB | Mark a reminder as completed in Apple Reminders |
| uncompleteReminderB | Mark a reminder as incomplete in Apple Reminders |
| deleteReminderB | Delete a reminder from Apple Reminders |
| updateReminderC | Update an existing reminder in Apple Reminders |
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 7 tools
Each tool targets a distinct operation (create, read, update, delete, complete, uncomplete, list lists) with no overlap in purpose.
Tools follow a verbNoun pattern consistently, though 'listReminderLists' uses 'list' instead of 'get' like the others, and 'uncomplete' is a bit unusual but symmetrical to 'complete'.
7 tools is well-scoped for a reminders server, covering the essential operations without bloat or missing core functionality.
Covers CRUD, complete/uncomplete, and listing lists; missing a dedicated getReminderById (getReminders returns from a list) but core workflows are solid.