# Cursor + Pear MCP guide

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

Use the authentication method shown for each client surface.

| Client surface | Authentication | Setup guide |
| --- | --- | --- |
| Cursor | API key via environment | Setup guide available |
<!-- MCP_HOST_COMPATIBILITY:END -->

Use Pear with Cursor by adding the hosted MCP 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 configuration.

## 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.