Connect Cursor to Pear MCP

1. Create your Pear account

Sign up at pearmcp.com, then connect Apple iCloud or Microsoft 365. Pear OAuth does not require a Pear API key or client secret. Choose the editor or Cloud Agent instructions below because Cursor stores those connections separately.

2. Install Pear in the Cursor editor

Choose Add Pear to Cursor, approve the MCP server, then complete Pear sign-in and consent. Cursor uses Pear's public OAuth Client ID with no client secret.

{
  "mcpServers": {
    "pear": {
      "url": "https://pearmcp.com/api/mcp",
      "auth": {
        "CLIENT_ID": "pear_oauth_grok_bot"
      }
    }
  }
}

Cursor and Grok Bot use the same Pear editor client ID and grant boundary by design. xAI's Grok Bot documentation says it shares Cursor MCP authentication, but Pear's named-host Grok Bot canary is still pending.

3. Connect Cursor Cloud Agents

Open cursor.com/agents, add Pear as a custom HTTP MCP server, and complete Pear OAuth there before launching an agent. Pear's dedicated Cloud Client ID keeps that connection separate from the editor, so authorizing one surface does not replace the other surface's refresh session. The editor deep link and tokens saved by the local Cursor app do not authenticate Cursor Cloud Agents.

{
  "url": "https://pearmcp.com/api/mcp",
  "auth": {
    "CLIENT_ID": "pear_oauth_cursor_cloud"
  }
}

Team admins can distribute the same server entry, but each member must complete their own Pear OAuth connection. The known failed Cloud Agent report stopped inside Cursor atneedsAuth before any request reached Pear. Pear has not yet completed the end-to-end Cursor Cloud lifecycle canary. Do not put a personal Pear API key in a team-shared configuration.

4. API-key alternatives

For the editor, add Pear from Cursor's MCP settings or project/user MCP JSON. Keep the Bearer credential in a local environment variable so it stays out of source control.

{
  "mcpServers": {
    "pear": {
      "url": "https://pearmcp.com/api/mcp",
      "headers": {
        "Authorization": "Bearer ${env:PEAR_API_KEY}"
      }
    }
  }
}

For a headless Cloud Agent that cannot use a member's OAuth connection, set the HTTPAuthorizationheader to a Bearer value in Cursor's encrypted HTTP header configuration. Never put that key in a repository, team-shared configuration, or Cloud VM environment variable.

5. Verify the right Cursor connection

• In the editor, approve the deep-link install or restart Cursor after saving manual JSON.
• For Cloud Agents, confirm Pear is connected at cursor.com/agents before launch.
• Start with a read-only prompt such as checking today's calendar.
• Only run write actions after Cursor shows the right connected provider account.

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.