Can Perplexity connect to Pear?
Perplexity documents custom remote MCP connectors with Streamable HTTP and API-key authentication. Pear exposes a hosted Streamable HTTP endpoint for Apple iCloud and Microsoft 365. Pear has not verified Perplexity's API-key header mapping or a complete authenticated connection, so this is a requirements guide.
Do not subscribe or move a workflow on the assumption that the Pear connection is already verified. Check Pear's current compatibility record first.
1. Check whether custom connectors are enabled
For an individual connection, look in Account settings, then Connectors, for + Custom connector. Choose Remote. In an organization, admins control whether members can add connectors. The presence of a built-in connector does not prove custom remote access is enabled.
2. Check the transport and authentication fields
The endpoint is below. Select Streamable HTTP, not legacy SSE. Pear requires authentication.
https://pearmcp.com/api/mcpPerplexity lists an API Key option, but its public guide does not specify the HTTP header format it sends. Pear requires Authorization: Bearer followed by your Pear API key. Confirm the form supports that mapping before entering a credential. If it does not, stop and contact Pear support with the client version and field names, without the key.
Pear has no Perplexity-specific OAuth Client ID published in this guide and does not expose dynamic client registration. Do not reuse a Client ID from another AI client's guide or select None to bypass authentication.
3. Keep the connection individual
A Pear API key belongs to one Pear account. Do not use a personal key in an organization-wide connector. Perplexity distinguishes individual and shared connectors; choose an individual connection while assessing compatibility.
What a successful check needs to show
Saving the connector alone is insufficient. It needs to authenticate, list Pear tools, and complete a read such as pear_provider_status. A full compatibility record also needs permission, persistence, and revocation checks. Write operations need their own evidence.
Until those checks pass, use one of Pear's other documented setup paths from the guide directory.
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 9 September 2026. This page documents configuration and requirements. It does not certify a completed Pear connection in Perplexity.
