# Cursor editor and Cloud Agents + Pear MCP guide

<!-- MCP_HOST_IDS: cursor, cursor-cloud -->
<!-- MCP_HOST_COMPATIBILITY:START -->
## Connection and authentication

Use the authentication method shown for each client surface.

| Client surface | Authentication | Setup guide |
| --- | --- | --- |
| Cursor | OAuth with a registered Client ID | Setup guide available |
| Cursor Cloud Agents | OAuth with a registered Client ID | Setup guide available |
<!-- MCP_HOST_COMPATIBILITY:END -->

The Cursor editor and Cursor Cloud Agents store MCP connections separately. Pear
uses a separate public OAuth Client ID for each surface, with no client secret. You
must connect each Cursor surface where you want to use Pear; authorizing one does
not replace the other surface's refresh session.

## Cursor editor OAuth setup

Choose [Add Pear to Cursor](cursor://anysphere.cursor-deeplink/mcp/install?name=pear&config=eyJ1cmwiOiJodHRwczovL3BlYXJtY3AuY29tL2FwaS9tY3AiLCJhdXRoIjp7IkNMSUVOVF9JRCI6InBlYXJfb2F1dGhfZ3Jva19ib3QifX0=),
approve the MCP server, then complete Pear sign-in and consent. No Pear API key or
client secret is required.

The installed server entry is:

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

This install is for Cursor. Grok Bot is not supported yet, and Pear has not completed
Grok Bot testing. Do not treat Cursor availability as Grok Bot support.

## Cursor Cloud Agents OAuth setup

Open [cursor.com/agents](https://cursor.com/agents), add Pear as a custom HTTP MCP
server, and complete Pear OAuth there before launching a Cloud Agent. Use this server
entry:

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

The hosted flow returns to
`https://www.cursor.com/agents/mcp/oauth/callback`. A Cursor editor deep link and
tokens saved by the local Cursor app do not authenticate Cursor Cloud Agents.

Team admins can distribute the same server entry, but each member must complete
their own Pear OAuth connection. Never add a personal Pear API key to a team-shared
MCP configuration. Pear has not yet completed the end-to-end Cursor Cloud lifecycle
canary.

### Headless Cloud Agent alternative

If a headless Cloud Agent cannot use a member's OAuth connection, configure the
`Authorization` Bearer value in Cursor's encrypted HTTP header configuration. Keep
the key in a personal or run-specific Cursor configuration. Do not put it in a
repository, team-shared configuration, or Cloud VM environment variable.

## Cursor editor API-key alternative

For local editor use, add the hosted endpoint to `.cursor/mcp.json`:

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

Set `PEAR_API_KEY` in the local environment available to Cursor. Do not replace the
interpolation with a real key inside a project or checked-in `mcp.json` file. Restart
Cursor or refresh its MCP servers after saving the API-key alternative.

## Apple Reminders compatibility

Pear's hosted CalDAV connection cannot access Apple's upgraded Reminders store. It can
use only the legacy reminder data Apple still exposes through CalDAV. Reconnecting
iCloud or replacing the App-Specific Password cannot change that protocol limit.
Microsoft To Do uses Microsoft Graph and is unaffected. See the
[Apple Reminders compatibility note](./apple-reminders-compatibility.md).

Use cases:

- Check your calendar before scheduling project work.
- Create Microsoft To Do tasks from TODO comments, or first confirm Apple exposes a
  usable legacy CalDAV reminder list.
- Search mail or contacts while working in the editor.