1. Create your Pear account
Sign up at pearmcp.com, connect Apple iCloud or Microsoft 365, and create your Pear API key. Store it in your local environment or password manager, not inside a project file. Cursor documents both automatic OAuth and static-client configuration, but Pear has not classified the automatic registration method or certified either OAuth path. This environment-backed API-key path remains canonical and still needs a current host smoke.
Sign Up Free2. Add Pear to Cursor MCP config
Add Pear from Cursor's MCP settings or project/user MCP JSON. Use an environment variable for the bearer token so the key stays out of source control.
{
"mcpServers": {
"pear": {
"url": "https://pearmcp.com/api/mcp",
"headers": {
"Authorization": "Bearer ${env:PEAR_API_KEY}"
}
}
}
}3. Verify inside Cursor
- Restart Cursor or refresh MCP servers after saving the config.
- Confirm Pear appears in Cursor's MCP server list.
- Start with a read-only prompt such as checking today's calendar.
- Only run write actions after Cursor shows the right connected provider account.
Apple 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 note