Which integrations are available for this server?

Allows interaction with Apple Reminders on macOS, providing tools for listing reminder lists, retrieving reminders, creating new reminders with titles and due dates, marking reminders as completed, and deleting reminders. Enables access to the Apple Reminders app on macOS through AppleScript, allowing for complete reminder management including viewing lists, retrieving, creating, completing, and deleting reminders.

How do I use MCP Apple Reminders?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@MCP Apple Reminders add 'buy groceries' to my shopping list for tomorrow" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

en es ja ko zh

MCP Apple Reminders

by shadowfax92

Overview Schema Related Servers Score Discussions

TypeScript

Local

MCP Apple Reminders

A Model Context Protocol (MCP) server for interacting with Apple Reminders on macOS.

Features

List Management: View all reminder lists in your Apple Reminders app
Reminder Retrieval: Get all reminders from a specific list
Create Reminders: Create new reminders with titles, due dates, and notes
Complete Reminders: Mark reminders as completed
Delete Reminders: Remove reminders from your lists
Date Handling: Proper handling of ISO date formats for due dates

Related MCP server: Apple Reminders MCP Server

Configuration

Usage with Claude Desktop

Add this to your claude_desktop_config.json:

{
  "mcpServers": {
    "apple-reminders": {
      "command": "node",
      "args": [
        "/path/to/mcp-apple-reminders/dist/index.js"
      ]
    }
  }
}

NPX (Coming Soon)

{
  "mcpServers": {
    "apple-reminders": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-apple-reminders"
      ]
    }
  }
}

API

The server exposes the following MCP tools for interacting with Apple Reminders:

getLists

Returns all reminder lists.

getReminders

Returns reminders from a specific list.

Parameters:
- listName (required): The name of the reminder list

createReminder

Creates a new reminder.

Parameters:
- listName (required): The name of the reminder list
- title (required): The title of the reminder
- dueDate (optional): The due date for the reminder (ISO format: "YYYY-MM-DDTHH:MM:SS.sssZ")
- notes (optional): Notes for the reminder

completeReminder

Marks a reminder as completed.

Parameters:
- listName (required): The name of the reminder list
- reminderName (required): The name of the reminder to complete

deleteReminder

Deletes a reminder.

Parameters:
- listName (required): The name of the reminder list
- reminderName (required): The name of the reminder to delete

How It Works

This MCP server uses AppleScript to interact with the Apple Reminders app on macOS. It provides a standardized interface for AI assistants to manage reminders through the Model Context Protocol.

Development

This project uses TypeScript and the MCP SDK. To extend functionality, modify the tools in src/index.ts and the AppleScript functions in src/reminders.ts.

Requirements

macOS (required for Apple Reminders integration)
Node.js 16+
Apple Reminders app configured with at least one list

License

MIT

Available Tools

5 tools

completeReminderD

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. Dates show when Glama detected each change.

1 tool updatev1.0.0Jan 3, 2026
- ChangedgetLists1 field changed
  - removedInput schema / additionalProperties
```
Removed value: -false
```
5 tool updatesAug 15, 2025
- First observedcompleteReminder
- First observedcreateReminder
- First observeddeleteReminder
- First observedgetLists
- First observedgetReminders

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

C2/5.0

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

Resources

GitHub Repository

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

hithereiamaliff-mcp-nextcloudOAuth
ai.smithery
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Cloud Storage File Systems Workplace & Productivity
237
reminders-bridgeOAuth
io.github.IsaiahDupree
MCP connector for Apple Reminders — search, create, complete, and edit via your own Mac.
Calendar Management App Automation Workplace & Productivity
1
mcpOAuth
net.todoist
Official Todoist MCP server for AI assistants to manage tasks, projects, and workflows.
App Automation Workplace & Productivity Project Management
2
Telnyx A
com.telnyx.api
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.
Communication Cloud Platforms Cloud Storage
62

Related MCP Servers

MCP Apple Reminders
Note Taking Calendar Management Workplace & Productivity
rex
A
license
Not graded
quality
D
maintenance
A 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.
Updated 3 months ago (2026-06-11 22:31 UTC)
MIT
Apple Reminders MCP Server
OS Automation App Automation
shreyanshjain05
A
license
Not graded
quality
C
maintenance
MCP server enabling AI assistants to create, read, list, and delete Apple Reminders on macOS via AppleScript.
Updated 5 months ago (2026-04-02 15:28 UTC)
11
Apache 2.0
apple-reminders-mcp-server
Workplace & Productivity Project Management
mggrim
F
license
Not graded
quality
D
maintenance
A Model Context Protocol server providing comprehensive integration with Apple Reminders, enabling CRUD operations, natural language date parsing, advanced search, and list management.
Updated 2 months ago (2026-07-02 17:07 UTC)
-
Apple Reminders MCP Server
Project Management Calendar Management Workplace & Productivity
justinhaaheim
A
license
Not graded
quality
B
maintenance
A Model Context Protocol (MCP) server that integrates Apple Reminders with Claude Desktop, enabling comprehensive task management and reminders directly through conversations with Claude.
Updated 2 days ago (2026-09-04 13:57 UTC)
61
4
MIT

Appeared in Searches

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/shadowfax92/apple-reminders-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server