苹果事件MCP服务器

Prerequisites

• Node.js 20 or later
• macOS (required for Apple Reminders integration)
• Xcode Command Line Tools (required for compiling Swift code)
• pnpm (recommended for package management)

macOS Permission Requirements (Sonoma 14+ / Sequoia 15)

Apple now separates Reminders and Calendar permissions into write-only and full-access scopes. The Swift bridge declares the following privacy keys so Claude can both read and write data when you approve access:

• NSRemindersUsageDescription
• NSRemindersFullAccessUsageDescription
• NSRemindersWriteOnlyAccessUsageDescription
• NSCalendarsUsageDescription
• NSCalendarsFullAccessUsageDescription
• NSCalendarsWriteOnlyAccessUsageDescription

When the CLI detects a notDetermined authorization status it calls requestFullAccessToReminders / requestFullAccessToEvents, which in turn triggers macOS to show the correct prompt. If the OS ever loses track of permissions, rerun ./check-permissions.sh to re-open the dialogs.

If a Claude tool call still encounters a permission failure, see Desktop MCP clients below for the responsible-process attribution problem and the recommended workarounds.

Dependencies

Runtime Dependencies:

• @modelcontextprotocol/sdk ^1.29.0 - MCP protocol implementation
• exit-on-epipe ^1.0.1 - Graceful process termination handling
• zod ^4.4.3 - Runtime type validation

Development Dependencies:

• typescript ^6.0.3 - TypeScript compiler
• @types/node ^25.8.0 - Node.js type definitions
• @types/jest ^30.0.0 - Jest type definitions
• jest ^30.4.2 - Testing framework
• @swc/core ^1.15.33 - SWC compiler
• @swc/jest ^0.2.39 - SWC Jest transformer
• @biomejs/biome 2.4.15 - Code formatting and linting

Build Tools:

• Swift binaries for native macOS integration
• TypeScript compilation for cross-platform compatibility

Quick Start

You can run the server directly using npx:

npx mcp-server-apple-events

Usage Examples

Once configured, you can ask Claude to interact with your Apple Reminders. Here are some example prompts:

Usage Examples

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

Example Tag Operations

Create with tags:

{
  "action": "create",
  "title": "Review code",
  "tags": ["work", "code-review", "urgent"]
}

Filter by tags:

{
  "action": "read",
  "filterTags": ["work", "urgent"]
}

Update tags (add/remove):

{
  "action": "update",
  "id": "reminder-123",
  "addTags": ["completed"],
  "removeTags": ["urgent"]
}

Configuration

Configure Cursor

1. Open Cursor
2. Open Cursor settings
3. Click on "MCP" in the sidebar
4. Click "Add new global MCP server"
5. Configure the server with the following settings:

   {
     "mcpServers": {
       "apple-reminders": {
         "command": "npx",
         "args": ["-y", "mcp-server-apple-events"]
       }
     }
   }
   

Configure ChatWise

1. Open ChatWise 2. Go to Settings 3. Navigate to the Tools section 4. Click the "+" button 5. Configure the tool with the following settings: - Type: stdio - ID: apple-reminders - Command: mcp-server-apple-events - Args: (leave empty)

Configure Claude Desktop

You need to configure Claude Desktop to recognize the Apple Events MCP server. There are two ways to access the configuration:

Option 1: Through Claude Desktop UI

1. Open Claude Desktop app
2. Enable Developer Mode from the top-left menu bar
3. Open Settings and navigate to the Developer Option
4. Click the Edit Config button to open claude_desktop_config.json

Option 2: Direct File Access

For macOS:

code ~/Library/Application\ Support/Claude/claude_desktop_config.json

For Windows:

code %APPDATA%\Claude\claude_desktop_config.json

2. Add Server Configuration

Add the following configuration to your claude_desktop_config.json:

Option A: Using npx (recommended)

{
  "mcpServers": {
    "apple-reminders": {
      "command": "npx",
      "args": ["-y", "mcp-server-apple-events"]
    }
  }
}

Option B: Using local build

If you have built the project locally, use node with the path to dist/index.js:

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

For more information on connecting local MCP servers, see the official MCP documentation.

Troubleshooting Calendar Read Errors

If you see Failed to read calendar events, verify Calendar is set to Full Calendar Access:

• Open System Settings > Privacy & Security > Calendars
• Find the app that launches this MCP server (for example Terminal or Claude Desktop)
• Change access to Full Calendar Access

You can also re-run ./check-permissions.sh (it now validates both Reminders and Calendars access).

Troubleshooting `could not build module 'Foundation'` on macOS 26 (Tahoe)

If pnpm build fails with could not build module 'Foundation' (or SDK is not supported by the compiler), your Swift toolchain is older than the macOS 26 SDK requires. The macOS 26+ SDK ships a Foundation.swiftinterface that needs Swift 6.3 or newer; the Command Line Tools that shipped with the first macOS 26 point releases include Swift 6.2.x, which cannot parse it. See issue #85.

pnpm build:swift now detects this mismatch and prints the same remediation, but if you hit it manually:

1. Install Xcode 26.x from the App Store (ships Swift 6.3+), or 2. Update Command Line Tools to a version that ships Swift 6.3+:

   softwareupdate --list
   sudo softwareupdate -i "Command Line Tools for Xcode-<latest>"
   

   sudo xcode-select --switch /Applications/Xcode.app/Contents/Developer
   

Verify with:

xcrun swiftc --version          # should report Apple Swift version 6.3 or newer
xcrun --show-sdk-version        # should match your macOS major version