Connect Continue to Pear MCP

1. Prepare Pear

Create your Pear account, connect iCloud or Microsoft 365, then copy a Pear API key. Put the key in a local Continue-resolved .env file and reference it through Continue's secret interpolation so it does not live inside the MCP definition.

Apple Reminders compatibility

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.

2. Add a streamable HTTP server

Continue's MCP docs support standalone files in.continue/mcpServerswithstreamable-http, SSE, and stdio entries. Use the HTTP transport for Pear's hosted endpoint.

name: Pear MCP
version: 0.0.1
schema: v1
mcpServers:
  - name: Pear
    type: streamable-http
    url: https://pearmcp.com/api/mcp
    requestOptions:
      headers:
        Authorization: Bearer ${{ secrets.PEAR_API_KEY }}

Set PEAR_API_KEY=pear_sk_... in the workspace's local .env,.continue/.env, or ~/.continue/.env. If you manage Continue through Hub configs, use Continue's hosted secrets flow instead of sharing the key.

3. Validate in Continue

• Reload Continue after changing config so the MCP server list refreshes.
• Confirm Pear tools appear before using provider write actions.
• Use a read prompt like checking tomorrow's schedule as the first test.
• Rotate the Pear API key if it is pasted into a shared config by mistake.