F
licenseNot graded
qualityD
maintenanceA Model Context Protocol server providing comprehensive integration with Apple Reminders, enabling CRUD operations, natural language date parsing, advanced search, and list management.
-
MCP Apple Reminders
by shadowfax92
Related Servers
Alternatives to MCP Apple Reminders
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceA macOS-only MCP server that exposes Apple Reminders to AI clients, enabling create, read, update, delete, search, and organization of reminders and lists through natural language.2MIT
- AlicenseNot gradedqualityBmaintenanceA Model Context Protocol (MCP) server that integrates Apple Reminders with Claude Desktop, enabling comprehensive task management and reminders directly through conversations with Claude.99 npm4MIT
- AlicenseNot gradedqualityCmaintenanceMCP server enabling AI assistants to create, read, list, and delete Apple Reminders on macOS via AppleScript.11Apache 2.0
- AlicenseNot gradedqualityDmaintenanceMCP server for Apple Reminders via remindctl. Enables MCP-compatible AI assistants to read and write Apple Reminders through the standard Model Context Protocol.1MIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that provides integration with Things 3 and Calendar app on macOS, allowing AI assistants to manage tasks, projects, and areas.-
TDQS
C2/5.0
Scored across 5 tools
Disambiguation5/5
Each tool has a clearly distinct purpose with no overlap: completeReminder, createReminder, and deleteReminder handle different lifecycle actions on reminders, while getLists and getReminders are distinct read operations for lists and reminders respectively. The naming makes it immediately clear what each tool does without ambiguity.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern with camelCase styling: completeReminder, createReminder, deleteReminder, getLists, getReminders. The naming is perfectly predictable and follows the same convention throughout the entire set.
Tool Count4/5
Five tools is a reasonable number for a reminders server, covering core CRUD operations and list management. It's slightly lean but appropriate for the domain, though an updateReminder tool would make it more complete. The count is well-scoped without being excessive.
Completeness3/5
The tool set covers create, read (getReminders), and delete operations for reminders, plus list management (getLists) and completion (completeReminder). However, there's a notable gap: no updateReminder tool to modify existing reminders, which is a common operation in reminder systems. This missing functionality could cause agent workarounds.
Maintenance
ActivityInactive
ResponsivenessNo issues