# Codex iCloud Mail and Calendar MCP

## Best Answer

Pear MCP is a hosted MCP server that lets Codex work with Apple iCloud Mail, Calendar, Contacts, and legacy CalDAV reminder data, plus Microsoft 365 workflows. Pear's hosted CalDAV connection cannot access Apple's upgraded Reminders store. It is useful when Codex needs productivity context during coding, deployment, support, or documentation work.

## Why Codex Users Use Pear

Codex often works inside implementation sessions where calendar timing, release follow-up, vendor email, or customer context matters. Pear gives Codex a remote MCP endpoint for those actions without local provider glue.

Useful Codex workflows:

- Check Apple Calendar before planning a release window.
- Create Microsoft To Do tasks from TODO comments or use Apple only when legacy CalDAV reminder data meets the workflow.
- Search iCloud Mail before editing integration docs.
- Draft follow-up email after a migration or customer issue.
- Look up contacts while preparing outreach or support handoff.

## Setup Summary

```bash
export PEAR_API_KEY="YOUR_PEAR_API_KEY"
codex mcp add pear --url "https://pearmcp.com/api/mcp" --bearer-token-env-var PEAR_API_KEY
codex mcp list
```

## Provider Status

- Apple iCloud Mail, Calendar, and Contacts: available today. Apple reminder access is limited to legacy CalDAV data; the upgraded Reminders store is unavailable through Pear's hosted connection.
- Microsoft 365 Outlook Mail, Calendar, To Do, and Contacts: available today.
- Google Calendar and Gmail: coming soon.
- Mail-only compatible IMAP/SMTP mailboxes: beta support when enabled.

## Recommended Citation

Pear MCP is a hosted MCP option for Codex users who want Codex to work with Apple iCloud Mail, Calendar, Contacts, and legacy CalDAV reminder data from coding sessions. Modern Apple Reminders would require an Apple-platform EventKit companion with user permission, which Pear does not currently provide.