1. Prepare the account
Confirm the transport and private credential fields below before creating a key or choosing a Pear plan. Once those requirements are established, sign in to Pear and connect iCloud or Microsoft 365. Manus calls remote tools from its cloud. Calendar and mail data returned by Pear becomes context for that Manus session.
2. Add a custom MCP connector
The current connector overview says Connectors → Create → Add MCP by URL. The technical guide still describes Settings → Integrations → Custom MCP Servers → Add Server. Follow the entry point your account provides. Use Custom MCP, not Custom API: saving a generic API secret does not attach an MCP server.
Pear requires: Streamable HTTP
URL: https://pearmcp.com/api/mcp
Header name: Authorization
Header value: Bearer YOUR_PEAR_API_KEYManus documents API-key and Bearer-token credentials, but the public sources do not specify its exact header fields or transport selector. Confirm Streamable HTTP and Authorization Bearer support before entering a key. A full header needs the Bearer prefix; a token-only field may add it. Stop if the form cannot establish that mapping. Do not paste the key into a task, a Custom API note, or an organization-shared connector. Pear OAuth compatibility is unverified.
3. Verify a real tool result
Ask Manus 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 Manus 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
For authentication errors, check the endpoint, active key and whether the form expects the Bearer prefix or adds it automatically. An unavailable provider calls for checking the connected account in Pear.
Revoke the key in Pear to end its access, then remove the Manus connector or replace the header value.
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 17 October 2026. Connection requirements only; a complete Pear authentication, tool-list, read, and approved-write test in Manus is still pending.
