Icloud MCP Server

Most planning and project tracking work still happens through a UI a human drives. Icloud MCP server moves it into the conversation instead. stdio MCP for iCloud Calendar (CalDAV), with optional Contacts and Mail.

The short version

Unified Apple/iCloud MCP server for Calendar, Contacts, and Mail: one static Go binary, Model Context Protocol JSON-RPC on stdio.

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

The tools it exposes

The server publishes 4 tools. What each one is for:

• Count — When
• Group — Tools
• Global — icloud_capabilities
• Dates — The Dates tool exposed by this server

What it needs from you

Configuration is passed through the environment: ICLOUD_EMAIL, ICLOUD_PASSWORD, ICLOUD_MCP_READ_ONLY, ICLOUD_MCP_DEFAULT_TZ, ICLOUD_MCP_ENABLE_CONTACTS, ICLOUD_MCP_ENABLE_MAIL, ICLOUD_MAIL_ADDRESS, ICLOUD_MAIL_PASSWORD. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Plenty of planning and project tracking servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Icloud's toolset — Count, Group, Global and 1 more — is a fair guide to whether it matches your workflow. It is maintained by ThomasCrouzet; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.