Skip to content

Connect Cursor to Pear MCP

Set up Pear separately in the Cursor editor or Cursor Cloud Agents. The editor and Cloud use separate Pear authorizations and client IDs. Pear shares the editor client ID with Grok Bot by design.

Connection details

The values Cursor asks for first.

Pear hosted endpointhttps://pearmcp.com/api/mcp
Authentication
OAuth + PKCE
Setup surface
Cursor editor or Cloud Agents dashboard
One-click installCloud Agent setupOAuth + PKCEAPI-key alternativeRemote MCP

Cursor documents static OAuth, editor install links, and per-user OAuth for Cloud Agents. Pear uses public Client IDs with no client secrets.

Setup guide availableOfficial setup reference
Get ready

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.

Sign Up Free
Make the connection

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.

Add Pear to Cursor
{
  "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 describes Cursor’s connector backend and team MCP policy. Grok Bot has a native OAuth custom-connector preview. Follow the Grok guide for its manual setup and preview limits.

Make the connection

3. Connect Cursor Cloud Agents

Cursor Cloud Agents require a paid Cursor plan, repository access, and a connected source-control account. Cloud model usage is billed by Cursor separately from Pear.

Open cursor.com/agents, use the MCP dropdown to add Pear as a custom HTTP 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.

Open 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, manage Pear from Customize in the sidebar or user MCP JSON at ~/.cursor/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.

Check it works

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.
  • Call pear_provider_status to check the account, then inspect a draft before approving a write.

Client permissions and verification status

Enterprise MCP policies can restrict servers and tools. Team distribution does not grant permission to use a server. Cursor normally requests tool approval, but the chosen Run Mode can change this behavior. Check that policy before allowing changes to your connected account.

Documentation checked on 17 October 2026. The editor and Cloud configurations follow documented Cursor capabilities and Pear's registered clients. Complete authenticated Pear lifecycle tests remain pending for both surfaces; a setup example is not proof of live interoperability.

Cursor MCP configuration and policies · Cloud Agent MCP setup · Cloud access and billing

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.

Read the Apple Reminders compatibility note
All guides

Connect Cursor

Free includes 50 counted provider actions/month. Most provider reads or writes count as one action. Batch writes count once per item. Setup and discovery do not count. Failed actions Pear can confirm had no provider effect also do not count; actions with an unknown outcome may count. Pro removes the cap.