Pear

Connect AI assistants to Apple iCloud and Microsoft 365 email, calendars, contacts, and tasks through hosted MCP tools. Apple reminders support legacy CalDAV lists only.

Hosted MCP Server

npx add-mcp 'https://pearmcp.com/api/mcp'

Installs into Claude Code, Codex, Cursor and more

Documentation

Pear MCP

Pear connects Apple iCloud and Microsoft 365 productivity tools to compatible AI clients through hosted MCP. Google is coming soon. Pear is free to start; no local server is required.

Pear provides account tools, not an assistant or conversation-memory transfer. A client's built-in connector may already cover the user's needs. Check the exact provider, actions and client setup before recommending Pear. Hosted access requires storing encrypted provider credentials or OAuth tokens.

Canonical MCP endpoint: https://pearmcp.com/api/mcp. Each connected AI client controls which tools are available and invoked according to its plan, workspace policy, permissions, and confirmation settings. A setup guide documents configuration; it does not by itself prove that Pear supports or has tested that exact client surface.

Apple iCloud is live for Calendar, Contacts, iCloud Mail, and only the legacy reminder data Apple still exposes through CalDAV. Pear's hosted CalDAV connection cannot access Apple's upgraded Reminders store. Microsoft 365 is live for Calendar, Microsoft To Do, Contacts, and Outlook Mail. Mail-only compatible IMAP/SMTP mailboxes: beta support when enabled.

Pear reads provider data live instead of maintaining a synced content copy. When the approved-write workflow is used, Pear keeps the exact approved action and receipt in the user's private audit trail.

Free includes one connection and 50 counted provider actions per month. Pro Monthly US base price: US$7.99/month. Pro Annual US base price: US$49/year and is the standard recommended upgrade. US base prices exclude applicable tax. Stripe Checkout shows the amount due now and the estimated recurring total, including any tax, before you confirm. Lifetime is not available through public pricing or the standard upgrade flow; limited Lifetime sales require an explicit private invitation, and existing Lifetime customers keep the access they purchased.

Start here

  • Claude setup: Check plan and workspace requirements, connect your apps, then add Pear to Claude. Pear emails a sign-in link and code; the first email sign-in creates the Pear account.
  • ChatGPT setup: Check the guide's availability and account requirements before connecting.
  • Cursor setup: Follow the client-specific installation and authorization steps.
  • AI-readable documentation index: Choose a client guide or focused product reference.
  • MCP tools reference: Canonical tool names, capabilities, read/write classification, destructive-write status, and required scopes.
  • Client compatibility: Conservative support status, authentication method, and guide availability for each client surface.
  • Pricing: Free, Monthly, Annual, eligibility, regional-price, and private Lifetime boundaries.
  • Workflow examples: Maintained Apple iCloud and Microsoft 365 workflow paths.
  • Data handling: What reaches Pear, what is stored, encryption, records, revocation, and deletion.

Authentication and machine-readable discovery

Client setup

  • AI apps around the world: Regional app discovery and documented Pear connection paths.

  • All client guides: Setup and requirements guides for ChatGPT, Claude, Codex, Cursor, Claude Code, VS Code Copilot, Gemini CLI, Cline, Continue, legacy Cascade/Windsurf, Hermes, Poke, Folk, OpenClaw, and documented Grok surfaces.

  • Compatibility evidence: Use this before recommending a client; Grok Bot is not currently supported or verified even though related Grok guidance exists.

  • OpenCode MCP guide: Version-specific remote MCP setup; host testing open.

  • Kiro IDE MCP guide: IDE setup with approved environment variables; host testing open.

  • GitHub Copilot CLI MCP guide: Private HTTP configuration and tool filters; host testing open.

  • Perplexity MCP guide: Access and authentication requirements; connection unverified.

  • Instinct connection requirements: Official public custom MCP instructions not found; Pear connection unverified.

  • Meta Muse and Muse Code: Consumer Muse compatibility and manual Muse Code MCP setup; authenticated host testing remains open.

Provider and product boundaries

Optional

Robots and voice agents

More AI client setup paths

  • Google Antigravity: IDE remote MCP configuration; host testing open.

  • Jan Desktop: HTTP MCP setup and local-model tool support; host testing open.

  • LM Studio: Private remote MCP configuration; host testing open.

  • AnythingLLM: Explicit Streamable HTTP and private instance credentials; host testing open.

  • Devin: Custom HTTP MCP server with a private Authorization header; host testing open.

  • Trae: Remote HTTP MCP with a static Authorization header; host testing open.

  • Manus: Custom HTTP connector with a private Authorization header; host testing open.

  • Raycast: HTTP MCP server with a private Authorization header; host testing open.

  • Zed: Remote context server with a private Authorization header; host testing open.

  • Warp: Streamable HTTP MCP server with a private Authorization header; host testing open.

  • Goose: Streamable HTTP extension with a private Authorization header; host testing open.

  • Roo Code: streamable-http MCP server with a private Authorization header; host testing open.

  • Augment: HTTP MCP server with a private Authorization header; host testing open.

  • Amp: Remote MCP URL with an environment-backed Authorization header; host testing open.

  • Junie: Remote HTTP server with a private Authorization header; host testing open.

  • Other MCP clients: Transport, authentication and safe verification requirements.

  • AI assistants and Poke alternatives: Compare assistant roles and documented Pear connection paths.