1. Check Folk's current connection options
Checked on 4 October 2026: Folk's public app guide now directs users to dashboard → menu → connected apps. Its FAQ advertises MCP support, but the documented name, URL, key form and reload command from our earlier guide are no longer in that app guide. We have not confirmed a replacement Pear setup procedure.
Check connection requirements with Pear2. Confirm the required transport and authentication
A Pear API-key connection needs remote MCP over Streamable HTTP and a private credential field that sends the Authorization Bearer header. These are API-key connection requirements, not confirmed Folk form fields. Do not enter a key until Folk documents the mapping.
Name
PearRequired HTTP header
Authorization: Bearer YOUR_PEAR_API_KEYServer URL
https://pearmcp.com/api/mcpAsk Folk support for its current custom MCP setup instructions and credential-field behavior. Share field names with Pear support, never credentials. A model-provider API-key setting is not a Pear MCP connection. Do not paste a key into chat or reuse another client's OAuth registration.
Read Folk's current app instructions3. Verify only after a documented setup is available
A saved URL does not establish access. Once a supported configuration is available, check authentication and returned tools before requesting provider data. Pear has not completed these checks in Folk.
- Call pear_provider_status and confirm the intended account and ready services.
- Read a known calendar event and compare it with your calendar.
- Check reconnection and revocation before relying on the connection.
- Keep writes separate: review an exact draft before approving any change.
Read Folk's FAQ for its MCP claim, or use the Poke guide for a messaging assistant with published custom MCP instructions. This page covers folk.com, not the separate folk.app CRM.
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
