1. Create your Pear account
Sign up at pearmcp.com and connect iCloud or Microsoft 365. Pear's documented Cline path uses a Bearer header with a Pear API key. Pear does not publish a Cline OAuth setup, and the API-key path remains pending a current named-host lifecycle smoke.
Sign Up Free2. Add Pear from Remote Servers
Cline's official remote-server flow recommends Streamable HTTP for new remote MCP servers. In VS Code, open Cline's MCP Servers view, choose Remote Servers, then add:
Server name
PearTransport
Streamable HTTPServer URL
https://pearmcp.com/api/mcp3. Authenticate and test
- Add an
AuthorizationBearer header using the Pear API key stored in local Cline settings. - Confirm the server is connected before asking for write actions.
- Start with calendar or contact lookup, then test Microsoft To Do or a usable legacy Apple CalDAV list before mail drafting.
- Keep the token in local Cline settings or a supported secret store, not a repository file.
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
