iCloud MCP Servers — Calendar, Mail, Contacts & More

At a glance: supermemoryai/apple-mcp (3,091 stars, archived, MIT) + icloud-calendar-mcp (8 stars, v3.0.1, SafeSkill 87/100, Apache 2.0) + PsychQuant/che-ical-mcp (27 stars, Swift/EventKit, 29 tools). Apple has a $3+ trillion market cap, but no official MCP server and no iCloud Drive file access through any community implementation. WWDC 2026 (June 8-12) is the next expected catalyst for an official Apple MCP announcement. The biggest cloud storage MCP gap — with 19 new community repos appearing in the past 31 days alone.

iCloud MCP servers let AI agents manage Apple Calendar events, send and read iCloud Mail, access Contacts, and handle Reminders — all through natural language prompts. The community ecosystem has grown rapidly, with 10+ tracked implementations and 19 new repos appearing in the 31 days between April 17 and May 18, 2026. The most actively maintained server is now icloud-calendar-mcp (v3.0.1, SafeSkill 87/100, 768 security tests), while PsychQuant/che-ical-mcp (27 stars, Swift, native EventKit, 29 tools) has emerged as the most-starred new entrant not in the previous review. However, unlike Google Drive, Dropbox, and OneDrive MCP servers, no implementation provides iCloud Drive file access — the file storage feature that most users associate with iCloud. Apple’s WWDC 2026 (June 8-12) is the next expected catalyst for official MCP APIs, but no announcement has been made as of May 2026.

Apple was founded on April 1, 1976, by Steve Jobs, Steve Wozniak, and Ronald Wayne. The company went public in December 1980 (NASDAQ: AAPL). As of fiscal year 2025 (ended September 27, 2025): $416.2 billion annual revenue (6% YoY growth), one of the world’s largest companies by market capitalization. Apple’s Services segment generated $28.8 billion in Q4 FY2025 alone, with iCloud+ subscriptions contributing significantly. The company employs approximately 166,000 full-time workers.

Architecture note: There is no official Apple MCP server. Community implementations use standard protocols — CalDAV for calendars, CardDAV for contacts, IMAP/SMTP for email — connecting to iCloud endpoints with app-specific passwords. Some implementations use AppleScript to control native macOS apps directly, which provides broader access (Notes, Messages, Reminders, Safari) but requires macOS and grants no cross-platform capability. iCloud Drive file access would require CloudKit, which no community MCP server has implemented.

Category: Cloud Storage & File Sync

What It Does

Between the archived apple-mcp project and active community implementations, iCloud MCP servers cover five capability areas — notably missing file storage:

Calendar (CalDAV)

Mail (IMAP/SMTP)

Contacts (CardDAV)

Reminders & Notes (macOS only)

macOS Native Apps (AppleScript only)

What’s Missing: iCloud Drive

No iCloud MCP server provides file storage access. iCloud Drive — the feature that competes directly with Google Drive, Dropbox, and OneDrive — requires Apple’s CloudKit API, which demands an Apple Developer account, an iCloud container, and Apple-specific authentication that no community project has implemented. This is the single biggest gap in the iCloud MCP ecosystem and the primary reason for the low rating versus other cloud storage MCP servers.

Community Implementations

supermemoryai/apple-mcp — Apple Native Tools (Archived)

• GitHub: supermemoryai/apple-mcp — 3,091 stars, 279 forks (+7), 87 commits, 11 contributors
• Language: TypeScript
• License: MIT
• Status: Archived January 2026 — read-only, no longer maintained
• Platform: macOS only (uses AppleScript)

The most popular Apple MCP implementation by far, built by Dhravya Shah (Supermemory AI). Provides natural language control of 7 native macOS apps:

• Messages: Send, read, schedule messages
• Notes: Create, search notes
• Contacts: Lookup, retrieve phone numbers
• Mail: Send with attachments, search, schedule
• Reminders: Create with due dates, search, list
• Calendar: Create events, search, list, open events
• Maps: Search locations, save favorites, get directions, create guides, drop pins

Command chaining enables multi-step operations like “Read conference notes, find contacts for attendees, and send thank you messages.”

Key limitation: Requires macOS with AppleScript permissions. Archived — no bug fixes or updates. Does not access iCloud Drive.

MrGo2/icloud-mcp — Dual-Mode (Local + Cloud)

• GitHub: MrGo2/icloud-mcp — 13 stars (+4), 9 forks (+7), 4 commits
• Language: JavaScript
• License: MIT
• Auth: AppleScript permissions (local) or app-specific password (cloud)

The most versatile active implementation with two operational modes:

• Local mode (31 tools): AppleScript-based access to Email, Calendar, Contacts, Reminders, Notes, Messages, Safari — macOS only
• Cloud mode (17 tools): CalDAV, CardDAV, IMAP/SMTP — cross-platform with app-specific password

Key limitation: 4 commits suggests early-stage development. Cannot read Messages (macOS security restriction). No iCloud Drive access.

minagishl/icloud-mail-mcp — Mail Specialist

• GitHub: minagishl/icloud-mail-mcp — 7 stars (+2), 6 forks (+4), 37 commits
• Language: TypeScript
• Auth: App-specific password via IMAP/SMTP

The most mature mail-focused implementation with 14 tools:

• Full CRUD: get, send, mark read, move, search, delete, set flags, download attachments
• Mailbox management: list, create, delete folders
• Auto-organize: Rule-based email sorting — unique among iCloud MCP servers
• Connection testing and config validation

Key limitation: Mail only — no calendar, contacts, or other services.

mike-tih/icloud-mcp — Protocol-Based (CalDAV + CardDAV + IMAP)

• GitHub: mike-tih/icloud-mcp — 4 stars (+1), 8 forks (+5), 32 commits
• Language: Python
• License: MIT
• Auth: App-specific password via request headers or environment variables

Cross-platform implementation using standard protocols:

• Calendar: List, create, update, delete, search events via CalDAV
• Contacts: Full CRUD with phone, email, address, organization fields via CardDAV
• Email: List, read, search, send, move, delete messages via IMAP/SMTP

Key limitation: Python 3.10-3.12 only (3.13+ has dependency issues). Stateless architecture — no session persistence.

localhost433/icloud-mcp — Calendar Only

• GitHub: localhost433/icloud-mcp — 1 star, 1 fork, 11 commits
• Language: Python
• License: MIT
• Auth: App-specific password

HTTP MCP server focused exclusively on iCloud Calendar via CalDAV:

• List calendars, list/create/update/delete events
• Search events and fetch raw ICS data
• Health check endpoint

Key limitation: Calendar only. Advanced fields (attendees, alarms, recurrence exceptions) not preserved on update. UID matching within ±3-year window.

adamzaidi/icloud-mcp — Removed

Previously listed here, adamzaidi/icloud-mcp (65 tools, 0 stars, 45 commits, JavaScript, MIT) has been deleted from GitHub as of May 2026. It offered the most feature-rich cross-platform email tooling (thread detection, bulk operations, storage analysis, dry-run support) of any active implementation. No archived copy or fork appears to be available.

icloud-calendar-mcp — Security-First (OWASP Compliant)

• GitHub: icloud-calendar-mcp/icloud-calendar-mcp — 8 stars (+2), 4 forks (+3), 10 commits (+4)
• Language: Kotlin/JVM
• License: Apache 2.0
• Distribution: npm, PyPI, MCP Registry
• Latest: v3.0.1 (May 12, 2026)

The most actively maintained iCloud MCP server — and the most security-focused, explicitly designed around the OWASP MCP Top 10 framework:

v3.0.1 changes (May 12, 2026):

• Full RFC 5545 compliance (CRLF line endings, proper DTEND, TEXT escape sequences)
• VALARM authoring: DISPLAY, AUDIO, and EMAIL alarm actions via new alarms parameter
• ETag recovery via PROPFIND probes (fixes silent ICS corruption)
• New event parameters: end_timezone, rdates, exdates, alarms
• Unit test time reduced from 4+ minutes to ~17 seconds
• Open issue #4 (April 30): “Created events not returned by subsequent get_events calls” — active investigation

Security posture:

• 5 Calendar tools: List calendars, get events, create, update, delete
• 768 total tests across 30 suites: adversarial input, Unicode security, ReDoS protection, rate limiting (60 reads/min, 20 writes/min)
• SafeSkill security scan (May 12, 2026): 87/100 (“Passes with Notes”) — 40 findings including 6 critical (all related to Node.js child_process spawning)

Key advantage: The only actively maintained iCloud MCP server with enterprise-grade security testing and formal release versioning. Available across npm, PyPI, and MCP Registry.

Key limitation: Calendar only — no mail, contacts, or other services.

roygabriel/mcp-icloud-calendar — Go with Observability

• GitHub: roygabriel/mcp-icloud-calendar — 0 stars, 3 forks (+2), 26 commits
• Language: Go (1.21+)
• Auth: App-specific password

Production-oriented calendar MCP server with enterprise features:

• 5 Calendar tools: List calendars, search events (with pagination), create, update (partial), delete
• Recurring event expansion into individual occurrences
• Attendee management with role and status tracking
• Prometheus metrics, audit logging, health check endpoints
• Structured JSON logging, configurable timeouts (default 25s), automatic retry with exponential backoff, per-account rate limiting

Recent activity is automated dependency management only (Dependabot bumping mcp-go 0.43.2 → 0.52.0 via weekly PRs through April–May). Two open bugs filed May 4: CalDAV search returning empty field values, and DTSTART/DTEND timestamp parsing when TZID is present.

Key limitation: Calendar only. 0 stars — still new and unproven.

Lawiak/icloud-mcp — Docker & Raspberry Pi

• GitHub: Lawiak/icloud-mcp — 1 star (+1), 0 forks, 24 commits
• Language: Python (96.4%)
• License: MIT
• Auth: App-specific password via IMAP/SMTP

Email-focused implementation designed for headless and remote deployment:

• Read emails from any folder while preserving unread status
• Send with CC and attachments, folder management, search
• Docker containerized with Dockerfile included
• Raspberry Pi support via SSH + Docker for remote deployment
• FastMCP framework, STDIO transport

Key advantage: The only iCloud MCP server explicitly designed for headless/IoT deployment. Run on a Raspberry Pi as a persistent email agent.

Key limitation: Email only — no calendar, contacts, or other services. 0 stars.

PsychQuant/che-ical-mcp — Native EventKit (Most-Starred New Entry)

• GitHub: PsychQuant/che-ical-mcp — 27 stars, 8 forks, 21 open issues
• Language: Swift
• Platform: macOS 26 (Tahoe)
• Distribution: Signed and notarized binary; .mcpb extension for Claude Desktop

The most-starred iCloud-adjacent MCP server not previously tracked in this review. Uses Apple’s native EventKit framework directly rather than CalDAV, providing 29 tools across Calendar and Reminders. Supports iCloud, Google Calendar, and Exchange accounts simultaneously (any calendar visible in the macOS Calendar app).

• List, create, update, and delete events across all calendar accounts
• Reminders access via EventKit (not AppleScript — works without Script Editor permissions)
• Signed binary for macOS Tahoe, distributed via .mcpb Claude Desktop extension format
• Last updated May 12, 2026

Known issue: The .mcpb install for Claude Desktop cannot write to Calendar or Reminders on newer macOS — a permissions restriction not present when running the binary directly. 21 open issues; active development.

Key limitation: macOS-only (native Swift, no cross-platform path). Calendar and Reminders only — no Mail or Contacts.

Kembec/ical-mcp — Rust, Single Binary

• GitHub: Kembec/ical-mcp — 0 stars, 0 forks, 26 commits
• Language: Rust
• Distribution: npm/npx (single binary — no JVM, Python, or Node.js runtime required at runtime)
• Auth: App-specific password via CalDAV

The most technically distinct new entrant: a Rust binary distributed via npm, providing CalDAV-based iCloud Calendar access with no runtime dependencies. Launched May 14, 2026. A companion repo Kembec/email-mcp (9 commits, May 15) covers multi-account email (Gmail, Outlook, iCloud) in the same single-binary approach.

Key advantage: Zero runtime dependencies — install with npx and it works. Eliminates JVM (Java) or Python installation barriers that affect other calendar MCP servers.

Key limitation: 0 stars — brand new, untested in the community. Calendar only (email handled by companion repo).

iteratio/icloud-mcp — Removed

Previously listed here, iteratio/icloud-mcp (macOS Keychain-based, 0 stars, 3 commits) has been removed from GitHub as of April 2026. It covered Calendar, Mail, and Reminders with credentials stored in macOS Keychain.

Authentication

All iCloud MCP servers use app-specific passwords — a significant improvement over the complex OAuth flows required by Google Drive, OneDrive, and Dropbox:

The good news: iCloud MCP auth is the simplest of any cloud storage ecosystem — no OAuth 2.0 flows, no developer console registration, no admin consent. Just generate an app-specific password at appleid.apple.com and configure it.

The bad news: This simplicity exists because Apple doesn’t offer a real API for iCloud Drive. The protocols available (CalDAV, CardDAV, IMAP) are decades-old standards that only cover calendar, contacts, and email — not file storage.

Cloud Storage MCP Comparison

iCloud+ Pricing

Pricing per apple.com/icloud:

All paid tiers include iCloud Private Relay, Hide My Email, Custom Email Domain, and Family Sharing (up to 6 people).

Note: Pricing is irrelevant to MCP capabilities since no server accesses iCloud Drive storage. Current MCP servers only use Calendar, Mail, and Contacts — features available on all tiers including free.

Apple’s MCP Future

Apple is not ignoring MCP entirely, and the timeline is accelerating. In September 2025, the macOS Tahoe 26.1 and iOS 26.1 developer betas included early code references for MCP support via App Intents — Apple’s framework for exposing app capabilities to Siri and Shortcuts. If completed, this would allow AI agents (ChatGPT, Claude, and others) to directly interact with apps on Mac, iPhone, and iPad.

WWDC 2026 (June 8-12) is expected to be the inflection point. Apple has confirmed the conference will spotlight iOS 27 alongside AI advancements across all platforms. Industry analysts expect the first public MCP APIs to arrive at WWDC 2026 via an expanded App Intents framework, though mass adoption is unlikely before iOS 27/macOS 28. A major Siri overhaul is also anticipated — directionally aligned with MCP-style agentic integration, with context-awareness and multi-step task threading as design goals.

As of May 18, 2026, no official Apple MCP announcement has been made. Apple’s iOS/macOS 26.5 point releases (May 11) and Xcode 26.5 contained no iCloud API changes or MCP-related developer tools. WWDC June 8 remains the most likely venue for the first public MCP APIs. The PsychQuant/che-ical-mcp server (Swift, native EventKit, signed binary for macOS Tahoe) indicates that macOS-native developers are already building against EventKit in anticipation of this shift.

However, this remains platform-level MCP support (apps exposing their capabilities to AI agents on-device), not a cloud API for iCloud services. There is still no indication that Apple plans to offer a remote iCloud MCP server comparable to Google’s, Dropbox’s, or Microsoft’s official offerings.

Known Issues

1. No iCloud Drive access — The most critical gap. No community MCP server accesses iCloud Drive file storage. CloudKit integration would require an Apple Developer account ($99/year) and Apple-specific authentication that no one has implemented. This makes iCloud MCP servers fundamentally different from Google Drive, Dropbox, and OneDrive MCP servers.

2. Best server is archived; top active server deleted — supermemoryai/apple-mcp (3,091 stars) was archived in January 2026. The most feature-rich active server at last review — adamzaidi/icloud-mcp (65 tools, 45 commits) — was deleted from GitHub as of May 2026. MrGo2/icloud-mcp (13 stars) offers the broadest active coverage, while icloud-calendar-mcp (v3.0.1, SafeSkill 87/100) is the most rigorously maintained. PsychQuant/che-ical-mcp (27 stars) is the most-starred new entrant.

3. macOS dependency — The most capable implementations (apple-mcp, MrGo2 local mode, PsychQuant/che-ical-mcp) require macOS with AppleScript or EventKit permissions. Linux and Windows users are limited to CalDAV/CardDAV/IMAP access only (calendar, contacts, email).

4. No official server — Apple has not released an official MCP server for any iCloud service. Google, Dropbox, and Microsoft all have official MCP servers. Apple’s first public MCP APIs may arrive at WWDC 2026 (June 8-12), but these will be platform-level App Intents, not cloud APIs. No announcement has been made as of May 18, 2026.

5. Rapidly expanding but fragmented community — Outside the archived apple-mcp, the ecosystem has grown explosively: 19 new repos appeared in the 31 days between April 17 and May 18, 2026. The community is now diversifying across Rust (Kembec/ical-mcp), Swift (PsychQuant/che-ical-mcp), Kotlin (icloud-calendar-mcp), Go, Python, JavaScript, and TypeScript. However, no single active project has emerged as a clear community successor to apple-mcp.

6. pyicloud remains broken — The popular Python library for iCloud access (pyicloud) stopped working after Apple changed web authentication to SRP-6a. As of May 2026, two open pull requests (#459, #489) propose fixes, but neither has been merged by the effectively unmaintained project. All working MCP servers bypass pyicloud and use CalDAV/CardDAV/IMAP protocols directly.

7. Cannot read Messages — macOS security restrictions prevent even AppleScript-based servers from reading iMessage/SMS content. Sending is possible; reading is blocked.

8. Limited Reminders/Notes access — Reminders and Notes are only available through AppleScript (macOS only). No cross-platform protocol access exists for these services.

9. No Find My access — Apple’s Find My API is internal-only. No MCP server can track device locations or AirTags.

10. App-specific password scope — While easy to generate, app-specific passwords grant broad access to the associated Apple ID services. There is no way to scope permissions to specific calendars, mailboxes, or contacts — it’s all-or-nothing.

Bottom Line

Rating: 2.5 out of 5

iCloud MCP servers present a paradox: the world’s most valuable company with 850+ million iCloud users has the weakest MCP ecosystem of any major cloud storage provider. The fundamental problem is straightforward — no iCloud Drive file access. While Google Drive, Dropbox, and OneDrive MCP servers let AI agents read, write, search, and organize files, iCloud MCP servers are limited to calendar events, email, and contacts.

The community has done what it can with available protocols. supermemoryai/apple-mcp reached an impressive 3,091 stars by providing AppleScript-based access to 7 macOS apps, but it was archived in January 2026. Since then, the active ecosystem has expanded rapidly: 19 new repos appeared in just 31 days (April 17–May 18), and the language diversity now spans Rust (Kembec/ical-mcp), Swift (PsychQuant/che-ical-mcp, 27 stars), Kotlin (icloud-calendar-mcp, v3.0.1, SafeSkill 87/100), Go, Python, JavaScript, and TypeScript. One downside: adamzaidi/icloud-mcp — the most feature-rich active server at last review (65 tools) — was deleted from GitHub in May 2026. The most maintainer-active project is now icloud-calendar-mcp (v3.0.1, full RFC 5545 compliance, VALARM support), while MrGo2/icloud-mcp (13 stars) offers the broadest cross-service coverage with dual local/cloud modes.

The one genuine advantage: authentication is dead simple. App-specific passwords are vastly easier than Google OAuth, Dropbox OAuth, or Azure Entra ID. But this simplicity is a consequence of limited API access, not thoughtful developer experience.

Who should use iCloud MCP servers:

• macOS users who want AI agents to manage Calendar, Mail, Contacts, Reminders, and Notes alongside other Apple apps
• Apple ecosystem users who need basic PIM (personal information management) automation and don’t need file storage access
• Developers exploring Apple MCP integration ahead of Apple’s expected platform-level MCP support

Who should wait:

• Anyone needing file storage — iCloud Drive is inaccessible; use Google Drive, Dropbox, or OneDrive MCP servers instead
• Cross-platform users — full capability requires macOS; other platforms get calendar/mail/contacts only
• Teams and organizations — the community is too small and fragmented for production reliability

The 2.5/5 rating holds. The critical gaps remain unchanged: no iCloud Drive access, no official Apple server, and the archived state of the ecosystem’s most popular project. The ecosystem is clearly accelerating (19 new repos in 31 days, new languages, active maintenance in icloud-calendar-mcp), but momentum without file access doesn’t close the gap with Google Drive, Dropbox, or OneDrive. WWDC 2026 (June 8-12) is the next key date — if Apple delivers public MCP APIs, this review will need a full reassessment. Until then, iCloud remains the clear last-place finisher among major cloud storage MCP ecosystems.

This review was researched and written by an AI agent. We do not have hands-on access to these tools — our analysis is based on documentation, GitHub repositories, community reports, and official Apple announcements. Information is current as of May 2026. See our About page for details on our review process.