icloud-mcp

Claude as a chief of staff across your iCloud account. An MCP server that bridges Claude Desktop (or any MCP client) to your Mail, Calendar, Reminders, and Contacts so Claude can triage your morning, schedule meetings, draft emails, defer tasks, and search across all four services in a single prompt.

The novelty isn't that it bridges iCloud (a handful of MCPs already do that). The novelty is the cross-service verbs that compose across iCloud silos — moving a Mail thread into a Reminder, scheduling around your calendar, drafting an email by contact name instead of email address, all in one call.

What you can do

Cross-service verbs (v3, the chief of staff)

• daily_brief — your morning view. Today's calendar + unread mail + overdue/due-today reminders, all in one tool call. Times in your timezone. Per-source errors don't block the whole brief.

• find — search across Mail / Calendar / Reminders / Contacts in parallel. Per-service results; no cross-service dedup yet (v4 work).

• schedule — create a calendar event with attendee resolution (names → contact emails) and conflict detection. Tells you what overlaps; lets you confirm.

• draft — save an email draft with contact resolution. Names get looked up in Contacts; ambiguous names surface for user clarification before the draft lands.

• defer — snooze a reminder to a later due date. ETag conditional PUT means concurrent edits surface as a clear error.

Per-service tools (v2 surface, kept for direct access)

Mail: list_folders, list_messages, read_message, search_messages, send_email, create_draft, create_reply_draft, send_draft, move_message, delete_message, mark_seen, mark_unseen, flag_message, unflag_message.

Calendar: list_calendars, list_events, get_event, create_event, update_event (v3, new), delete_event.

v4 cross-service verbs (the cornerstone, v4.2)

• triage(uid, folder?) — Read a mail message, propose a reminder + event + draft (whichever fit), return a signed TriagePlan. Identity resolution flows through M4.1's IdentityResolver so contacts collapse correctly.

• triage_commit(confirmToken, proposed) — Execute the plan after user confirmation. Each leg runs with deterministic-UID idempotency; re-calling within the 10-min token window produces zero duplicate iCloud resources. Partial failures surface with retrySafe: true on failed legs.

• triage_commit_retry(legs, payload) — Retry specific failed legs after the token window expires (or when only some legs need retrying). Same per-leg idempotency keys ensure already-succeeded legs replay without duplicates.

v4 admin tools

• identity_cache_flush — Drop the per-request Contacts cache used by the identity resolver. After editing a Contact in the iCloud Contacts app, call this so the next verb sees the change without restarting the server.

Related MCP server: imail-mcp

What v4.2 added (the triage verb)

triage is the cornerstone chief-of-staff move that v3 named and deferred. Reads a mail message, proposes the cross-service actions that fit the message, returns a signed plan. After you confirm, triage_commit executes each leg with deterministic-UID idempotency so retries dedupe at the iCloud level rather than creating duplicates. The proposer is rules-based for v4.2 (action-verb regex + chrono-node for natural-language datetime + question/request detection); LLM-generated suggestions are explicitly v5 work.

The load-bearing correctness claim of v4.2: re-calling triage_commit with the same confirmToken within its 10-min window produces zero duplicate resources. Per-leg idempotency keys derive deterministic UIDs (CalDAV) and Message-Ids (IMAP); on retry the second PUT returns 412 from If-None-Match: * and we GET-and-return the existing resource as replayed_existing.

Set CONFIRM_TOKEN_SECRET (32+ random bytes) in your environment before using triage. The HMAC signing of confirmToken is intentionally separate from AUTH_TOKEN so a leaked bearer token can't be used to forge proposals.

What v4.1 changed (the identity layer)

draft and schedule now route name resolution through a single identity layer that handles fuzzy matching, multi-email collapse, and shared-phone collapse:

• Fuzzy name matching. Drafting to Andersn resolves to Anderson (1-character typos on names ≥7 chars match at the 0.85 similarity threshold). Pure substring matches still take precedence; fuzzy is a fallback when nothing else matched.

• Multi-email collapse. A Contact with both jane.work@… and jane.home@… resolves to one identity with the preferred email as canonical. No more "ambiguous" prompt for the same person.

• Shared-phone collapse. Two Contact records that share a phone number collapse to one identity (the user usually didn't mean to create both).

• Per-request cache lifecycle. Contacts are fetched once at the start of a request and reused for every identity lookup within that request. On Vercel the cache lives for one HTTP call; on stdio it lives for the long-running process.

The current threshold (0.85) and the per-request cache are both first-shot guesses pending dogfooding measurement. See CHANGELOG.md for the M4.1 ship-gate items still owed.

Setup

Install dependencies:

bun install

Configure credentials. iCloud uses an app-specific password (generate at account.apple.com → Sign-In and Security → App-Specific Passwords):

cp .env.example .env
# edit .env: set ICLOUD_EMAIL and ICLOUD_APP_PASSWORD

Run the MCP server (stdio transport, for Claude Desktop):

bun run start

Or via Vercel for remote access. Once deployed, your MCP endpoint lives at https://<your-deployment>.vercel.app/api/mcp (StreamableHTTP transport). It accepts two credentials:

• a static AUTH_TOKEN bearer (for stdio callers and the Claude API's mcp_servers.authorization_token), and

• an OAuth 2.1 access token, which is what the Claude app connector requires. See Connecting to the Claude app (OAuth) below.

Connecting to the Claude app (OAuth)

The Claude app (web + desktop "Custom Connectors") only speaks OAuth or no-auth — it can't paste a static token. This server ships an OAuth 2.1 provider (via Better Auth) so the app can connect. The OAuth layer only proves the caller is you (GitHub sign-in restricted to your email); your iCloud credentials stay server-side and never pass through it.

Architecture. The bearer check in api/mcp.ts now also accepts Better Auth OAuth tokens. src/auth.ts exposes the provider under /api/auth/*; public/sign-in.html + public/consent.html handle login and approval. The flow:

Claude app → /api/mcp (no token)
          → 401 + WWW-Authenticate → discovery (/.well-known/*)
          → /api/auth/mcp/authorize → /sign-in → GitHub OAuth
          → consent (/consent) → auth code → token → /api/mcp (Bearer) ✓

One-time setup:

1. Database (free). Create a Neon Postgres project (or add Vercel Postgres, which is Neon). Copy the pooled connection string into DATABASE_URL.

2. GitHub OAuth app. GitHub → Settings → Developer settings → OAuth Apps → New. Set Authorization callback URL to https://<your-deployment>.vercel.app/api/auth/callback/github. Copy the client id/secret into GITHUB_CLIENT_ID / GITHUB_CLIENT_SECRET.

3. Env vars. Set BETTER_AUTH_URL (your full deployment origin), BETTER_AUTH_SECRET (openssl rand -hex 32), and ALLOWED_EMAILS (your GitHub account email — this is the single-user gate) in Vercel. See .env.example.

4. Run migrations. With the same env in your local .env, create the Better Auth tables:

   bun run auth:migrate      # or: bunx @better-auth/cli migrate

5. Add the connector. In the Claude app, add a custom connector pointing at https://<your-deployment>.vercel.app/api/mcp. Claude discovers OAuth, sends you through GitHub sign-in + consent, and connects.

If your GitHub email is private, GitHub returns a …@users.noreply.github.com address — put that in ALLOWED_EMAILS (the first sign-in attempt will show the exact address in the Vercel function logs).

Connecting to Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "icloud": {
      "command": "bun",
      "args": ["run", "/absolute/path/to/icloud-mcp/src/server.ts"],
      "env": {
        "ICLOUD_EMAIL": "your@icloud.com",
        "ICLOUD_APP_PASSWORD": "xxxx-xxxx-xxxx-xxxx"
      }
    }
  }
}

Restart Claude Desktop. Try: "What's on my plate today?" (calls daily_brief).

Verifying the install

bun test               # 188 unit tests, no creds required
bun run smoke-test     # read-only round-trip against your real iCloud

The smoke test exercises every provider (IMAP, SMTP, CalDAV calendars + VTODO, CardDAV) without writing anything. It's the live-credential backstop for the recorded-fixture unit tests — fixtures rot when iCloud changes its protocol semantics, and the smoke run catches that drift.

Architecture

api/
  mcp.ts             Vercel entry — MCP over StreamableHTTP; accepts AUTH_TOKEN or OAuth
  auth/[...all].ts   Better Auth catch-all (/api/auth/*)
  well-known/        Root OAuth discovery routes (rewritten from /.well-known/*)
public/
  sign-in.html       GitHub sign-in page (loginPage)
  consent.html       One-click OAuth consent page
src/
  auth.ts            Better Auth OAuth provider (mcp plugin, GitHub, single-user gate)
  server.ts          MCP server, instantiates providers, registers tools+verbs
  utils/vercel-web.ts  Vercel (req,res) ↔ Web Request/Response bridge for Better Auth
  providers/
    caldav-transport.ts    Shared CalDAV/CardDAV connection base class
    icloud-quirks.ts       requireOkAndEtag + ETagConflictError + iCalErrorExcerpt
    discovery-cache.ts     TTL'd cache for PROPFIND discovery
    imap.ts                Mail read
    smtp.ts                Mail send
    caldav.ts              Calendar (VEVENT)
    reminders.ts           Reminders (VTODO via CalDAV)
    contacts.ts            Contacts (CardDAV with hand-rolled vCard parser)
    identity-cache.ts      v4 IdentityResolver — request-scoped Contacts index
  tools/             v2 per-service MCP tool registrations
  verbs/             v3 cross-service verb registrations + shared envelope
  utils/
    timezone.ts            Resolve / register / convert iCloud-friendly timezones
    rrule.ts               Recurrence rule construction
    identity.ts            Email/phone canonicalization + fuzzy name helpers
docs/
  ICLOUD-QUIRKS.md         Canonical record of iCloud's CalDAV/CardDAV deviations
eventkit-cli/spike/        TCC feasibility test that proved EventKit needs a paid
                           Apple Developer cert (v3 stayed cloud-only as a result)

The verb response envelope is consistent across all v3 verbs:

{
  items: <verb-specific shape>,
  degraded: boolean,                    // true if any source failed
  errors: { source, message }[],        // per-source failures
  userMessage?: string,                 // what the LLM should tell the user
}

What's NOT here

Reminders smart lists, nested subtasks, location triggers, and attachments — Apple removed those from CalDAV in iOS 13+ and they're EventKit-only on Mac. The TCC spike at eventkit-cli/spike/ proved ad-hoc-signed CLI binaries can't get Reminders TCC permission on macOS 26.4; v4 will revisit if a paid Apple Developer cert becomes available. See TODOS.md.

Notes, Photos, Health, Find My, Wallet, Maps — Apple closed APIs, no remote access at all. Notes via AppleScript is a v4+ TODO.

Cross-service identity dedup beyond email canonicalization (multi-email contacts, fuzzy name matching, phone-number fallback) — v4 TODO.

Contributing

Push straight to main; no branches/PRs for this project. Solo developer workflow.

iCloud's CalDAV/CardDAV servers deviate from the spec in ways that took multiple commits to figure out. Before adding a new write path, read docs/ICLOUD-QUIRKS.md and use the shared requireOkAndEtag validator from icloud-quirks.ts. New iCloud quirks discovered in the wild should land in that doc.

Tests follow a pure-function-extraction pattern — test/caldav.test.ts:13-40 is the model. Network-dependent integration tests live in smoke-test.ts and run against a real account.

License

MIT (or whatever you prefer — currently unspecified).