A
licenseNot graded
qualityB
maintenanceA 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.
2
MIT
MCP Apple Reminders
by shadowfax92
Recordatorios de Apple de MCP
Un servidor de Protocolo de contexto de modelo (MCP) para interactuar con Recordatorios de Apple en macOS.
Características
Gestión de listas : vea todas las listas de recordatorios en su aplicación Recordatorios de Apple
Recuperación de recordatorios : obtenga todos los recordatorios de una lista específica
Crear recordatorios : crea nuevos recordatorios con títulos, fechas de vencimiento y notas.
Recordatorios completos : marcar recordatorios como completados
Eliminar recordatorios : elimina recordatorios de tus listas
Manejo de fechas : manejo adecuado de los formatos de fecha ISO para fechas de vencimiento
Related MCP server: Apple Reminders MCP Server
Configuración
Uso con Claude Desktop
Agregue esto a su claude_desktop_config.json :
{
"mcpServers": {
"apple-reminders": {
"command": "node",
"args": [
"/path/to/mcp-apple-reminders/dist/index.js"
]
}
}
}NPX (próximamente)
{
"mcpServers": {
"apple-reminders": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-apple-reminders"
]
}
}
}API
El servidor expone las siguientes herramientas MCP para interactuar con Apple Reminders:
obtenerListas
Devuelve todas las listas de recordatorios.
obtener recordatorios
Devuelve recordatorios de una lista específica.
Parámetros:
listName(obligatorio): el nombre de la lista de recordatorios
crearRecordatorio
Crea un nuevo recordatorio.
Parámetros:
listName(obligatorio): el nombre de la lista de recordatoriostitle(obligatorio): El título del recordatoriodueDate(opcional): La fecha de vencimiento del recordatorio (formato ISO: "AAAA-MM-DDTHH:MM:SS.sssZ")notes(opcional): Notas para el recordatorio
recordatorio completo
Marca un recordatorio como completado.
Parámetros:
listName(obligatorio): el nombre de la lista de recordatoriosreminderName(obligatorio): El nombre del recordatorio a completar
eliminarRecordatorio
Elimina un recordatorio.
Parámetros:
listName(obligatorio): el nombre de la lista de recordatoriosreminderName(obligatorio): El nombre del recordatorio a eliminar
Cómo funciona
Este servidor MCP utiliza AppleScript para interactuar con la app Recordatorios de Apple en macOS. Proporciona una interfaz estandarizada para que los asistentes de IA gestionen recordatorios mediante el Protocolo de Contexto de Modelo.
Desarrollo
Este proyecto utiliza TypeScript y el SDK de MCP. Para ampliar la funcionalidad, modifique las herramientas en src/index.ts y las funciones de AppleScript en src/reminders.ts .
Requisitos
macOS (necesario para la integración de Recordatorios de Apple)
Node.js 16+
La aplicación Recordatorios de Apple está configurada con al menos una lista
Licencia
Instituto Tecnológico de Massachusetts (MIT)
Available Tools
5 toolscompleteReminderD
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| listName | Yes | ||
| reminderName | Yes |
TDQS
D1/5.0
Behavior1/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness1/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness1/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose1/5
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines1/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
createReminderD
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| listName | Yes | ||
| title | Yes | ||
| dueDate | No | ||
| notes | No |
TDQS
D1/5.0
Behavior1/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness1/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness1/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose1/5
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines1/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
deleteReminderD
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| listName | Yes | ||
| reminderName | Yes |
TDQS
D1/5.0
Behavior1/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness1/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness1/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose1/5
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines1/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
getListsD
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
TDQS
D1/5.0
Behavior1/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness1/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness1/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose1/5
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines1/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
getRemindersD
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| listName | Yes |
TDQS
D1/5.0
Behavior1/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness1/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Tool has no description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness1/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Tool has no description.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has no description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose1/5
Does the description clearly state what the tool does and how it differs from similar tools?
Tool has no description.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines1/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
v1.0.0- Changed
getLists1 field changed- removed
Input schema / additionalPropertiesRemoved value: -false
5 tool updates
- First observed
completeReminder - First observed
createReminder - First observed
deleteReminder - First observed
getLists - First observed
getReminders
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
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
MCP connector for Apple Reminders — search, create, complete, and edit via your own Mac.
- mcpOAuthnet.todoist
Official Todoist MCP server for AI assistants to manage tasks, projects, and workflows.
The Telnyx MCP server is an official implementation of the Model Context Protocol that enables AI clients (like Claude Desktop, Cursor, and OpenAI Agents) to interact with Telnyx's telephony, messaging, and AI assistant APIs. It provides comprehensive capabilities including making and managing phone calls, sending SMS/MMS messages, purchasing and configuring phone numbers, creating AI assistants with custom instructions, managing cloud storage buckets, scraping and embedding website content, and handling integration secrets. The server exists as both a local implementation and a remotely hosted version, allowing developers to integrate real-world communication infrastructure directly into AI applications.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceMCP server enabling AI assistants to create, read, list, and delete Apple Reminders on macOS via AppleScript.11Apache 2.0
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server providing comprehensive integration with Apple Reminders, enabling CRUD operations, natural language date parsing, advanced search, and list management.-
- 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