1. Prepare the account
Sign in to Pear, connect iCloud or Microsoft 365, and create an API key in Settings. In Devin, an organization admin with permission to manage MCP servers adds the custom server.
This guide does not connect you to https://mcp.devin.ai/mcp. That address is Devin's own MCP server, for other clients that want Devin's tools. It also does not use the Cascade mcp_config.json file on the Windsurf guide. Current Devin and legacy Cascade are different surfaces.
2. Add a custom HTTP server
Open Customize → MCPs → Add MCP → Add custom MCP. Choose HTTP (Streamable HTTP). SSE is the older transport. Use an auth header, not OAuth. Pear has not certified a Devin OAuth client.
Transport: HTTP
URL: https://pearmcp.com/api/mcp
Header name: Authorization
Header value: Bearer YOUR_PEAR_API_KEYReplace the placeholder only in Devin's private server settings. Keep the Bearer prefix and the space. Do not paste the key into a Devin chat or a shared screenshot.
The Devin CLI uses the same URL and header in its private MCP config. Devin's OAuth login is a different flow and is not the path on this page.
3. Verify a real tool result
Ask Devin to call pear_provider_status and name the ready services for your account. Then ask it to find a calendar event you already know, with a narrow date range and the correct timezone.
Inspect the actual tool response. If Devin only describes how it would check your calendar, the read has not happened.
From a read to a reviewed draft
Try: “Find tomorrow's planning meeting and summarize its time and attendees. Then preview a follow-up email for me to review; do not send it.” Review the draft, recipient list, and sending account before approving any write through Pear.
Troubleshoot the connection or remove access
An authentication error calls for checking the endpoint, the header name, and that the value starts with Bearer . An unavailable provider calls for checking the connected account in Pear.
Revoke the key in Pear to end its access, then remove the custom server in Devin or replace the header value with a new key.
Choose a useful first workflow
Start with a read. Ask which calendars are connected, find an event in a specific date range, or search a mail folder for a message you already know. Specify the account and timezone when they matter.
For Apple accounts, see iCloud setup and services and iCloud Mail workflows. For Microsoft accounts, see Microsoft 365 setup, Outlook Mail, and Microsoft To Do.
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. Google Workspace remains coming soon.
Pear exposes tools allowed by your account and permissions. Your AI client decides when to call them. Review recipients, dates, and content before approving writes. Read how Pear handles your data and the current plans before expanding the workflow.
Sources and compatibility status
Documentation checked on 26 September 2026. Setup guide available; a complete Pear authentication, tool-list, read, and approved-write test in Devin is still pending.
