# Perplexity MCP and Pear: connection requirements ## Connection and authentication Use the authentication method shown for each client surface. | Client surface | Authentication | Setup guide | | --- | --- | --- | | Perplexity | API key | Setup guide available | Check Perplexity remote MCP access, admin permissions, and Pear authentication requirements. The Pear connection is not yet verified. ## 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](https://pearmcp.com/mcp-compatibility) 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. ```text https://pearmcp.com/api/mcp ``` Perplexity 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](https://pearmcp.com/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](https://pearmcp.com/docs). ## Provider limits and next steps Start with a read such as provider status, a known event, or a known message. Specify the account and timezone. Available tools depend on the connected provider, account, and client permissions. - [iCloud setup](https://pearmcp.com/icloud-mcp-server) - [iCloud Mail](https://pearmcp.com/ai-icloud-mail) - [Microsoft 365](https://pearmcp.com/microsoft-365-mcp-server) - [Outlook Mail](https://pearmcp.com/outlook-mail-mcp) - [Microsoft To Do](https://pearmcp.com/microsoft-to-do-mcp) - [Data handling](https://pearmcp.com/data-handling) - [Plans](https://pearmcp.com/pricing) Pear's hosted CalDAV connection cannot access Apple's upgraded Reminders store. It can use only the legacy reminder data Apple still exposes through CalDAV. Reconnecting cannot change this limit. Microsoft To Do is unaffected. Google Workspace is coming soon. Review recipients, dates, and content before approving writes. Pear exposes permitted tools; the AI client controls when it calls them. ## Sources and status Documentation checked on 9 September 2026. Setup guidance is not proof of a completed Pear connection in Perplexity. - [Official Perplexity documentation](https://www.perplexity.ai/help-center/en/articles/13915507-adding-custom-remote-connectors)