Connect Poke to Pear MCP

1. Start from the Pear recipe

The fastest path is the Pear Poke recipe. Open it, then connect your Pear account or keep the same server details for a custom MCP integration.

2. Add Pear manually if needed

If you are configuring Poke manually, create a custom MCP integration with the Pear server URL and your Pear API key as the bearer/API key value.

Poke also documents automatic DCR and a hosted static recipe that requires a client ID and client secret. Pear intentionally exposes neither open DCR nor a confidential client secret; do not paste an API key into either OAuth field. Keep Pear on the API-key path.

3. Verify a complete workflow

• Ask Poke what is on tomorrow's calendar.
• Create a Microsoft To Do task, or first confirm that Apple exposes a usable legacy CalDAV reminder list.
• Look up a contact and combine it with a scheduling request.
• Search unread mail and draft a reply you can review before sending.

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.