Connect Codex to iCloud

1. Create your Pear account

Sign up at pearmcp.com with your email, connect iCloud during onboarding with an App-Specific Password, and copy your Pear API key (pear_sk_...).

2. Add Pear in Codex

Codex CLI supports remote MCP servers directly. Export your Pear API key into an environment variable, then add Pear once:

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

That stores Pear in your Codex MCP configuration without hardcoding the secret into the config file itself.

3. Verify it and start using it

Run codex mcp list to confirm Pear is registered, then open Codex and start asking for Apple-aware actions:

• “What meetings do I have this afternoon?”
• “Create a reminder to ship the release notes tomorrow morning.”
• “Find a free 30-minute slot next week and draft an email to confirm it.”
• “Show me unread iCloud Mail from this morning.”

What Pear unlocks inside Codex

• Read and update Apple calendar events, reminders, contacts, and Mail from the same coding assistant.
• Run daily briefing, scheduling, free-time search, and follow-up workflows from one hosted MCP server.
• Avoid custom local Apple automation by registering Pear once in Codex CLI and reusing it across sessions.
• Keep inbox, calendar, reminders, and coding tasks in one grounded agent workflow.

Why Codex + Pear?

Codex is strongest when you can stay in one flow. Pear gives it grounded Apple context without jumping to your phone or browser every few minutes, so scheduling, reminders, contact lookups, and inbox checks can happen in the same workspace where you are already coding.