1. Check the AI app, not just its model
The app or agent running your conversation must support remote MCP over Streamable HTTP and an authentication method Pear accepts. A model's ability to answer questions or run locally does not establish either capability.
Look for your app in Pear's client guides first. Those pages cover the specific configuration, plan restrictions, and known gaps for each host. If your app is not listed, use its current official MCP documentation alongside this checklist. A stdio-only client needs a separately supported remote connection path; this guide does not supply a universal bridge or command.
2. Add Pear's hosted endpoint
Create a Pear account and connect the iCloud or Microsoft 365 account you want to use. In your AI app's personal MCP settings, add a server named Pear and choose its documented remote HTTP or Streamable HTTP option.
https://pearmcp.com/api/mcpUse the complete endpoint above. Do not substitute a legacy SSE URL or a local command. The client handles MCP initialization, protocol negotiation, and tool discovery. Configuration field names differ between apps, so copy the structure from your client's documentation rather than another app's JSON.
3. Choose a supported authentication path
Personal API key
If the client documents a Bearer token field or custom HTTP headers, create or copy a Pear API key in Settings. A dedicated Bearer token field normally takes the key itself; a complete Authorization header takes the form below. Follow the client's documentation so the Bearer prefix appears exactly once.
Authorization: Bearer <your Pear API key>This illustrates the header, not a working credential or a configuration file. Prefer the client's native secret input or its documented environment-variable interpolation. Do not assume that a variable such as PEAR_API_KEY is expanded just because another client supports it.
If the client requires a literal key, keep it only in private personal settings outside shared projects and version control. Do not put it in chat, a URL query string, or a shared team connector. If the client cannot keep a personal credential private, stop before adding the key.
OAuth sign-in
Pear publishes OAuth discovery metadata and supports Client ID Metadata Documents (CIMD). Pear intentionally does not expose Dynamic Client Registration (DCR). A host that requires DCR alone cannot complete that path.
Follow the host-specific compatibility guidance before using OAuth or arranging client preregistration. Do not invent a Client ID or client secret, reuse another app's registration, or paste an API key into an OAuth client-secret field. A host's OAuth support alone is not proof that its flow works with Pear.
4. Verify a small, read-only request
Refresh the client's MCP connections and inspect the returned tools. Keep tool approvals enabled and start with this request:
Call pear_provider_status and report which accounts and services are ready. Do not change anything.After checking the result, select one ready account and try a bounded read: list its calendar events for one day with an explicit timezone, or find one known message in a named mail folder. Compare the result with the original provider app. Use the accounts, IDs, and tool schemas returned by Pear.
If you want to inspect the write workflow, ask for a non-executing draft and review its exact account, recipients, dates, and content. Stop at the draft and approval review for this setup check. Do not send mail or execute a provider change to prove connectivity. A successful read does not establish write support.
Resolve connection errors and disconnect cleanly
- 401 Unauthorized: check the complete endpoint, the selected authentication mode, and whether the key is missing, expired, or revoked. Check that environment interpolation actually runs in the process launching the client. For OAuth, follow the host guide to sign in again.
- 403 Forbidden: inspect the error and review Pear scopes, provider readiness, account or plan restrictions, and your AI app's organization policy. Repeating the request does not grant permission.
- No tools: check the connection, tool filters, account readiness, and granted scopes. An empty tool list is not evidence that a mailbox or calendar is empty. Do not proceed to provider actions until discovery works.
Removing Pear from the AI app stops that configured connection, but does not prove its credential was revoked. Revoke a dedicated API key in Pear, or rotate a shared key when required; rotation affects other clients using it. For a managed OAuth connection, disconnect that app in Pear's Connected apps settings. Legacy OAuth connections may require API-key rotation until they reauthorize.
A local AI still connects to hosted Pear
Your model can run on your own computer while its MCP client calls Pear's hosted endpoint. Pear receives the structured tool request and fetches permitted data from the connected provider. Tool results return to the AI app and may also reach its chosen model service. Running a local model does not make this an offline or local-only provider connection.
Review both the AI app's data settings and Pear's data-handling explanation before connecting personal data.
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
Protocol sources checked on 26 September 2026. This is a requirements and setup checklist, not a claim that every MCP client has passed a Pear connection test. Authentication, tool discovery, reads, persistence, and revocation need to work in the actual client; writes need separate evidence.
Official MCP transport specification
