Where Pear fits in Poke
Cognition acquired Poke's maker on 23 July 2026. Poke remains available, and this setup is unchanged. Poke's own integrations cover Gmail and Outlook. Its FAQ currently excludes native iCloud Mail support. Pear supplies a separate MCP path to your connected iCloud Mail, Calendar and Contacts, plus Microsoft 365. If Poke's existing Outlook connection already covers your workflow, you may not need Pear for that account.
This guide documents configuration. Pear has not completed authenticated Poke testing. Compare AI assistants for email and calendar, or check Pear compatibility before choosing a setup.
1. Start from the Pear recipe
Connect your provider in Pear first: Apple iCloud or Microsoft 365. Create a Pear API key in Settings. Open the Pear recipe, or use the manual setup below.
2. Add Pear manually if needed
Open Poke's new integration form. Name it Pear, enter the server URL and paste your Pear API key into the API Key field. Choose Create Integration. Poke adds the Bearer prefix itself.
Server URL
https://pearmcp.com/api/mcpAuthentication
API Key field → Bearer headerToken value
Pear API key from SettingsPoke documents this request-header mapping:
Authorization: Bearer YOUR_PEAR_API_KEYEnter only the key in Poke's API Key field. Keep it in your private connection; never put it in a recipe, shared link, chat message or screenshot. Your Apple app-specific password and Microsoft sign-in belong in Pear's provider setup, not this field.
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. Check a read before preparing a write
- Ask Poke to use Pear to check connected providers with
pear_provider_status. Confirm it finds the intended account. - Read a known iCloud Calendar event or search for a known iCloud Mail message. Specify the account, folder and date range; compare the result with your own app.
- Ask for a reply through
pear_draft_write. Review the sender, recipient, subject and body in Pear before approving it. - Only after that approval, use
pear_execute_approved_writefor the unchanged draft. Check the receipt; preparing a draft does not send the email.
If tools are missing, re-sync the integration in Poke. For an authentication error, check the endpoint and private API-key field. A successful save alone does not verify reads, writes or every provider combination.
Useful Poke workflows to try
- “Use Pear to find the delivery email in my iCloud Mail inbox, then prepare a reply asking to change the date. Do not send it yet.”
- “Read tomorrow's iCloud Calendar in my timezone and find a free hour. Prepare an event for that time for me to review.”
- “Find the follow-up in my Outlook Mail and prepare a Microsoft To Do task. Show me the due date before creating it.”
Explore iCloud Mail, Outlook Mail and Microsoft To Do workflows. Tools depend on your connected provider, scopes, plan and Poke's controls. Google Workspace through Pear remains coming soon.
Sources and connection status
Checked 26 September 2026: Poke MCP documentation and Poke FAQ. Poke documents the transport and Bearer mapping; a complete authenticated Pear connection in Poke is still unverified.
Read how Pear handles your data and Pear plans before expanding access.
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