English | 简体中文
A Model Context Protocol (MCP) server that provides native integration with Apple Reminders on macOS. This server allows you to interact with Apple Reminders through a standardized interface with comprehensive management capabilities.
- List Management: View all reminders and reminder lists with advanced filtering
- Reminder Operations: Create, update, delete, and move reminders across lists
- Rich Content: Support for titles, notes, due dates, URLs, and completion status
- Native Integration: Seamless integration with macOS Apple Reminders app
- Smart Organization: Automatic categorization by priority, due date, category, or completion status
- Powerful Search: Filter reminders by completion status, due dates, and search terms
- Batch Operations: Organize multiple reminders with intelligent strategies
- Permission Management: Proactive validation of system permissions
- Flexible Date Handling: Support for both date-only and date-time formats with locale awareness
- Unicode Support: Full international character support with validation
- Unified API: Streamlined tool architecture with action-based operations
- Type Safety: Comprehensive TypeScript coverage with Zod validation
- Performance: Swift binaries for performance-critical operations
- Error Handling: Consistent error responses with detailed feedback
- Node.js 18 or later
- macOS (required for Apple Reminders integration)
- Xcode Command Line Tools (required for compiling Swift code)
- pnpm (recommended for package management)
Install globally via npm:
npm install -g mcp-server-apple-reminders
- Open Cursor
- Open Cursor settings
- Click on "MCP" in the sidebar
- Click "Add new global MCP server"
- Configure the server with the following settings:
{ "mcpServers": { "apple-reminders": { "command": "mcp-server-apple-reminders", "args": [] } } }
- Open ChatWise
- Go to Settings
- Navigate to the Tools section
- Click the "+" button
- Configure the tool with the following settings:
- Type:
stdio
- ID:
apple-reminders
- Command:
mcp-server-apple-reminders
- Args: (leave empty)
- Type:
You need to configure Claude Desktop to recognize the Apple Reminders MCP server. There are two ways to access the configuration:
- Open Claude Desktop app
- Enable Developer Mode from the top-left menu bar
- Open Settings and navigate to the Developer Option
- Click the Edit Config button to open
claude_desktop_config.json
For macOS:
code ~/Library/Application\ Support/Claude/claude_desktop_config.json
For Windows:
code %APPDATA%\Claude\claude_desktop_config.json
Add the following configuration to your claude_desktop_config.json
:
{
"mcpServers": {
"apple-reminders": {
"command": "mcp-server-apple-reminders",
"args": []
}
}
}
For the changes to take effect:
- Completely quit Claude Desktop (not just close the window)
- Start Claude Desktop again
- Look for the tool icon to verify the Apple Reminders server is connected
Once configured, you can ask Claude to interact with your Apple Reminders. Here are some example prompts:
Create a reminder to "Buy groceries" for tomorrow at 5 PM.
Add a reminder to "Call mom" with a note "Ask about weekend plans".
Create a reminder in my "Work" list to "Submit report" due next Friday.
Create a reminder with URL "Check this website: https://google.com".
Update the reminder "Buy groceries" with a new title "Buy organic groceries".
Update "Call mom" reminder to be due today at 6 PM.
Update the reminder "Submit report" and mark it as completed.
Change the notes on "Buy groceries" to "Don't forget milk and eggs".
Show me all my reminders.
List all reminders in my "Shopping" list.
Show my completed reminders.
Show all my reminder lists.
Show reminders from my "Work" list.
The server will:
- Process your natural language requests
- Interact with Apple's native Reminders app
- Return formatted results to Claude
- Maintain native integration with macOS
This server provides two unified MCP tools for comprehensive Apple Reminders management:
Tool Name: reminders
A comprehensive tool for managing Apple Reminders with action-based operations. Supports all reminder operations through a single unified interface.
Actions: list
, create
, update
, delete
, bulk_create
, bulk_update
, bulk_delete
, organize
List Action (action: "list"
):
list
(optional): Name of the reminder list to showshowCompleted
(optional): Include completed reminders (default: false)search
(optional): Search term to filter reminders by title or contentdueWithin
(optional): Filter by due date range ("today", "tomorrow", "this-week", "overdue", "no-date")
Create Action (action: "create"
):
title
(required): Title of the reminderdueDate
(optional): Due date in format 'YYYY-MM-DD' or 'YYYY-MM-DD HH:mm:ss'list
(optional): Name of the reminders list to add tonote
(optional): Note text to attach to the reminderurl
(optional): URL to associate with the reminder
Update Action (action: "update"
):
title
(required): Current title of the reminder to updatenewTitle
(optional): New title for the reminderdueDate
(optional): New due date in format 'YYYY-MM-DD' or 'YYYY-MM-DD HH:mm:ss'note
(optional): New note textcompleted
(optional): Mark reminder as completed/uncompletedlist
(optional): Name of the list containing the reminderurl
(optional): New URL to attach to the reminder
Delete Action (action: "delete"
):
title
(required): Title of the reminder to deletelist
(optional): Name of the list containing the reminder
Bulk Create Action (action: "bulk_create"
):
items
(required): Array of reminder objects to create
Bulk Update Action (action: "bulk_update"
):
criteria
(required): Search criteria to find remindersupdates
(required): Properties to update
Bulk Delete Action (action: "bulk_delete"
):
criteria
(required): Search criteria to find reminders to delete
Organize Action (action: "organize"
):
strategy
(required): Organization strategy ("priority", "due_date", "category", "completion_status")sourceList
(optional): Source list to organize fromcreateLists
(optional): Create new lists automatically (default: true)
{
"action": "create",
"title": "Buy groceries",
"dueDate": "2024-03-25 18:00:00",
"list": "Shopping",
"note": "Don't forget milk and eggs",
"url": "https://example.com/shopping-list"
}
{
"action": "list",
"list": "Work",
"showCompleted": false,
"dueWithin": "today"
}
{
"action": "organize",
"strategy": "category",
"sourceList": "Inbox",
"createLists": true
}
Tool Name: lists
Manage reminder lists - view existing lists or create new ones for organizing reminders.
Actions: list
, create
, update
, delete
List Action (action: "list"
):
- No additional parameters required
Create Action (action: "create"
):
name
(required): Name for new reminder list
Update Action (action: "update"
):
name
(required): Current name of the list to updatenewName
(required): New name for the reminder list
Delete Action (action: "delete"
):
name
(required): Name of the list to delete
{
"action": "create",
"name": "Project Alpha"
}
Success Response:
{
"content": [
{
"type": "text",
"text": "Successfully created reminder: Buy groceries"
}
],
"isError": false
}
Note about URL fields: The url
field is currently limited by Apple's EventKit API restrictions and will typically be null
. This is a limitation of Apple's EventKit framework, not our implementation. URLs stored in the native URL field of reminders cannot be accessed programmatically.
Structured URL Format: This server now uses a structured format for URLs in reminder notes to ensure consistent parsing and extraction:
Reminder note content here...
URLs:
- https://example.com
- https://another-url.com
URL Extraction: You can extract URLs from reminder notes using the structured format or regex fallback:
// Using the structured format (recommended)
import { extractUrlsFromNotes, parseReminderNote } from './urlHelpers';
// Extract just URLs
const urls = extractUrlsFromNotes(reminder.notes);
// Parse into separate note content and URLs
const { note, urls } = parseReminderNote(reminder.notes);
// Legacy regex method (fallback for unstructured content)
const urlsRegex = reminder.notes?.match(/https?:\/\/[^\s]+/g) || [];
Benefits of Structured Format:
- Consistent parsing: URLs are always in a predictable location
- Multiple URL support: Handle multiple URLs per reminder reliably
- Clean separation: Note content and URLs are clearly separated
- Backward compatible: Unstructured URLs still detected as fallback
List Response:
{
"reminders": [
{
"title": "Buy groceries",
"list": "Shopping",
"isCompleted": false,
"dueDate": "2024-03-25 18:00:00",
"notes": "Don't forget milk\n\nURLs:\n- https://grocery-store.com\n- https://shopping-list.com",
"url": null
}
],
"total": 1,
"filter": {
"list": "Shopping",
"showCompleted": false
}
}
The server includes built-in URL utilities for working with the structured URL format. These utilities are exported from src/utils/urlHelpers.js
:
extractUrlsFromNotes(notes)
- Extract URLs from structured or unstructured notesparseReminderNote(notes)
- Parse notes into separate content and URL arrayformatNoteWithUrls(note, urls)
- Format note content with structured URLsremoveUrlSections(notes)
- Remove URL sections to get clean note contentcombineNoteWithUrl(note, url)
- Combine note with single URL in structured format
import {
extractUrlsFromNotes,
parseReminderNote,
formatNoteWithUrls
} from 'mcp-server-apple-reminders/src/utils/urlHelpers.js';
// Extract URLs from any reminder note
const urls = extractUrlsFromNotes(reminder.notes);
console.log(urls); // ['https://example.com', 'https://test.com']
// Parse note into content and URLs
const { note, urls } = parseReminderNote(reminder.notes);
console.log(note); // "Task description"
console.log(urls); // ['https://example.com']
// Create structured note content
const structured = formatNoteWithUrls("New task", ['https://link1.com', 'https://link2.com']);
// Result: "New task\n\nURLs:\n- https://link1.com\n- https://link2.com"
The server provides intelligent reminder organization capabilities through four built-in strategies:
Automatically categorizes reminders based on priority keywords:
- High Priority: Contains words like "urgent", "important", "critical", "asap"
- Medium Priority: Default category for standard reminders
- Low Priority: Contains words like "later", "someday", "eventually", "maybe"
Organizes reminders based on their due dates:
- Overdue: Past due dates
- Today: Due today
- Tomorrow: Due tomorrow
- This Week: Due within the current week
- Next Week: Due next week
- Future: Due beyond next week
- No Date: Reminders without due dates
Intelligently categorizes reminders by content analysis:
- Work: Business, meetings, projects, office, client related
- Personal: Home, family, friends, self-care related
- Shopping: Buy, store, purchase, groceries related
- Health: Doctor, exercise, medical, fitness, workout related
- Finance: Bills, payments, bank, budget related
- Travel: Trips, flights, hotels, vacation related
- Education: Study, learn, courses, books, research related
- Uncategorized: Doesn't match any specific category
Simple binary organization:
- Active: Incomplete reminders
- Completed: Finished reminders
Organize all reminders by priority:
Organize my reminders by priority
Categorize work-related reminders:
Organize reminders from Work list by category
Sort overdue items:
Organize overdue reminders by due date
MIT
Contributions welcome! Please read the contributing guidelines first.
- Install dependencies:
npm install
- Build the project (TypeScript and Swift binary):
npm run build
.
├── src/ # Source code directory
│ ├── index.ts # Main entry point
│ ├── server/ # MCP server implementation
│ │ ├── server.ts # Server configuration and lifecycle
│ │ ├── handlers.ts # Request handlers and routing
│ │ └── *.test.ts # Server tests
│ ├── swift/ # Native Swift integration code
│ │ ├── bin/ # Compiled Swift binaries
│ │ ├── GetReminders.swift # Swift source file
│ │ └── build.sh # Swift build script
│ ├── tools/ # MCP tool definitions and handlers
│ │ ├── definitions.ts # Tool schemas and validation
│ │ ├── handlers.ts # Tool implementation logic
│ │ ├── index.ts # Tool registration
│ │ └── *.test.ts # Tool tests
│ ├── types/ # TypeScript type definitions
│ │ └── index.ts # Core type definitions
│ ├── utils/ # Helper functions and utilities
│ │ ├── __mocks__/ # Test mocks
│ │ ├── *.ts # Utility modules
│ │ └── *.test.ts # Utility tests
│ ├── validation/ # Schema validation utilities
│ │ └── schemas.ts # Zod validation schemas
│ └── test-setup.ts # Test environment setup
├── dist/ # Compiled JavaScript output
│ ├── index.js # Main compiled entry point
│ ├── swift/bin/ # Compiled Swift binaries
│ ├── server/ # Server compiled files
│ ├── tools/ # Tools compiled files
│ ├── types/ # Types compiled files
│ ├── utils/ # Utils compiled files
│ └── validation/ # Validation compiled files
├── node_modules/ # Node.js dependencies
├── package.json # Package configuration
├── tsconfig.json # TypeScript configuration
├── jest.config.mjs # Jest test configuration
├── pnpm-lock.yaml # pnpm lock file
└── *.md # Documentation files
npm run build
- Build both TypeScript and Swift components (REQUIRED before starting server)npm run build:ts
- Build TypeScript code onlynpm run build:swift
- Build Swift binary onlynpm run dev
- TypeScript development mode with file watchingnpm run start
- Start the MCP servernpm run test
- Run comprehensive test suitenpm run clean
- Clean build artifacts
Runtime Dependencies:
@modelcontextprotocol/sdk ^1.5.0
- MCP protocol implementationmoment ^2.30.1
- Date/time handling utilitieszod ^3.24.2
- Runtime type validation
Development Dependencies:
typescript ^5.8.2
- TypeScript compiler@types/node ^20.0.0
- Node.js type definitions@types/jest ^29.5.12
- Jest type definitionsjest ^29.7.0
- Testing frameworkts-jest ^29.1.2
- Jest TypeScript support
Build Tools:
- Swift binaries for native macOS integration
- TypeScript compilation for cross-platform compatibility