icloud-mcp
Related Servers
Alternatives to icloud-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables read-only iCloud Drive access over MCP, allowing users to browse folders, search filenames, download files, and extract document text.52MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for iCloud Drive on macOS, enabling Claude to browse, read, search, tag, write, and trash files with safe defaults and automatic handling of iCloud placeholder files.3 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to access iCloud Calendar, Reminders, and Mail with configurable scope and read-only modes.1MIT
- AlicenseAqualityCmaintenanceEnables agents to read, create, update, and delete iCloud Calendar events, including recurring events, via CalDAV.6MIT
- AlicenseNot gradedqualityCmaintenanceEnables access to iCloud mail, calendars, and contacts over MCP through IMAP/SMTP, CalDAV, and CardDAV, with configurable read/write and deletion permissions.2MIT
- AlicenseNot gradedqualityBmaintenanceEnables an AI assistant to read and search iCloud mail, draft messages (never sent), manage calendar events with a preview/commit gate, and look up contacts via IMAP, CalDAV, and CardDAV.76 npm2MIT
TDQS
Scored across 14 tools
Most tools target distinct operations, but a few pairs overlap: icloud_read_file vs icloud_download (inline text vs save-to-disk) and icloud_upload vs icloud_write_file (local file vs string content). Descriptions clarify these boundaries, so misselection risk is low but nonzero.
All tools share a uniform icloud_ prefix and lowercase snake_case, which is predictable. The only minor deviation is mixing bare nouns (status, list, info) with verb_noun forms (read_file, write_file, list_trash), but it remains readable.
14 tools is well within the ideal range and each one covers a distinct file/folder lifecycle operation. Nothing feels padded or redundant.
The surface covers create (mkdir, write_file, upload), read (list, info, search, read_file, download), update (rename, move, overwrite), and delete/restore (trash, list_trash, restore) — strong lifecycle coverage. Minor gaps like copy or share/permission operations exist but are workaroundable.