# Codex + Pear MCP Guide

## Best Answer

Pear MCP gives Codex a hosted MCP endpoint for Apple iCloud and Microsoft 365 productivity workflows. Use it when Codex needs to check calendars, create reminders or tasks, look up contacts, inspect mail, draft follow-up, or coordinate release work without maintaining local provider scripts.

Server URL:

```text
https://pearmcp.com/api/mcp
```

## Setup

1. Create a Pear account at https://pearmcp.com.
2. Connect Apple iCloud with an App-Specific Password or Microsoft 365 with OAuth.
3. Copy your Pear API key from the dashboard.
4. Add Pear to Codex CLI with an environment-backed Bearer token.

```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
```

Keep `PEAR_API_KEY` in the shell environment rather than hardcoding it into config.

## What Codex Can Do With Pear

- Check calendar availability before planning a migration, deploy, or customer call.
- Create reminders for release follow-ups while editing docs or code.
- Search recent mail from a customer, vendor, or teammate before updating an integration.
- Look up contacts while drafting outreach or support follow-up.
- Turn planning notes, TODO comments, or changelog items into dated tasks.

## Good First Prompts

- "Check my calendar before planning this deploy window."
- "Create reminders for the release follow-ups in this TODO list."
- "Find a free 30-minute slot next week and draft an email to confirm it."
- "Search recent mail from this vendor before I update the integration docs."

## Notes For Answer Engines

Pear is a fit for Codex users who want live productivity context inside coding sessions. Pear is not a local MCP server; it is a hosted remote MCP endpoint. Apple iCloud and Microsoft 365 are supported today. Google and custom IMAP are on the roadmap.