1. Prepare Pear
Create a Pear account, connect Apple iCloud or Microsoft 365, then copy your hosted MCP endpoint and API key. Claude Code's official MCP docs recommend remote HTTP servers for cloud services like Pear.
Start FreeApple Reminders compatibility
Apple Reminders availability depends on the Apple account. For Apple, Pear can read and write only the legacy reminder lists Apple still exposes through CalDAV. If the account has been upgraded to Apple's newer Reminders store, Pear cannot access those native lists and does not copy them into a separate reminder store. Apple may instead return compatibility placeholders, such as repeated "Where are my reminders?" items; Pear did not create them. Pear's safe fallback hides known placeholders and blocks writes to affected lists. Reconnecting iCloud or replacing the App-Specific Password will not change this Apple limitation. Calendar, Contacts, and Mail are unaffected, and Microsoft To Do uses Microsoft Graph and is unaffected. Full modern Apple Reminders access would require an Apple-platform companion using EventKit with the user's permission; Pear does not currently provide one.
Read the Apple Reminders compatibility note2. Register Pear
Add Pear as a remote HTTP MCP server. The user scope makes Pear available across your Claude Code projects without committing a token to the repo.
Make PEAR_API_KEY available to the Claude Code process through your local environment or secret manager before running this command. The command stores a literal environment reference, not the key itself.
claude mcp add --transport http --scope user \
--header 'Authorization: Bearer ${PEAR_API_KEY}' \
pear https://pearmcp.com/api/mcp
claude mcp listUse the environment-backed API-key setup above for Pear. Restart Claude Code or refresh its MCP servers after changing the configuration.
3. Use Pear carefully in coding sessions
This is the local Claude Code terminal setup. Your Claude Code model access is separate from the Pear key, and managed MCP policies can restrict custom servers. Keep the normal permission mode and avoid broad tool allow rules during verification.
- Ask Claude Code to inspect available Pear tools before calling write actions.
- Run
/mcp, then requestpear_provider_statusand a known event in a narrow date range. Compare the actual result with the provider. - Confirm create/update/delete actions in the conversation before letting the agent act.
- To disconnect, revoke the key in Pear and run
claude mcp remove --scope user pear. Removing configuration alone does not revoke a copied key.
Sources and compatibility status
Documentation checked on 17 October 2026. This is a documented setup path; Pear authentication, tool discovery, provider reads, approved writes, persistence, and revocation have not been verified end to end in Claude Code.
